Skip to content

Commit 1ea0726

Browse files
maxulysseewels
andauthored
Apply suggestions from code review
Co-authored-by: Phil Ewels <[email protected]>
1 parent 708b427 commit 1ea0726

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

README.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -51,9 +51,7 @@ The curator workflow is as follows:
5151

5252
- [ ] Once a issue is made, update the 'Project' status to 'proposed' (right hand side bar, under 'new-<TYPE>-proposals')
5353
- [ ] Facilitate discussion on the the Issue thread, following the guidance [here](https://nf-co.re/docs/contributing/project_proposals).
54-
- [ ] Acceptance requires a minimum of OKs from:
55-
- Two members of the core team.
56-
- One member of the core team and one member of the maintainers team.
57-
- [ ] If a proposal is accepted, update both the label AND status to 'accepted', and when closing select 'Close as completed'
58-
- [ ] If a proposal is turned down, update both the label AND status to 'turned-down', and when closing select 'Close as not planned'
54+
- [ ] Acceptance requires quorum from the nf-core core team, done via voting in comments with `/accept` or `/reject`
55+
- [ ] If a proposal is accepted, update both the issue label AND project status to 'accepted', and when closing select 'Close as completed'
56+
- [ ] If a proposal is turned down, update both the issue label AND project status to 'turned-down', and when closing select 'Close as not planned'
5957
- [ ] If a proposal is not completed or abandoned after a year, update both the label AND status to 'timed-out', and when closing select 'Close as not planned'

0 commit comments

Comments
 (0)