Skip to content

Commit 58bf41e

Browse files
committed
More details
1 parent 1ea0726 commit 58bf41e

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

README.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,9 @@ The curator workflow is as follows:
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).
5454
- [ ] 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'
57-
- [ ] 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'
55+
- [ ] If a proposal is turned down, update both the label AND status to 'turned-down', and when closing select 'Close as not planned'
56+
- [ ] If a proposal is accepted, update both the label AND status to 'accepted', and ask the champion to write a formal RFC and begin initial development.
57+
- [ ] When the PR is opened the corresponding issue can be closed.
58+
- [ ] Verify that feedback has been provided to the champion.
59+
- [ ] Propose an optional Bytesize talk about the proposal.
60+
- [ ] Finally merge the PR when the development is complete.

0 commit comments

Comments
 (0)