Skip to content

Commit 9fd8097

Browse files
authored
Merge pull request #38 from nf-core/update_README
update RFC curator workflow docs
2 parents 9cca86c + 34a99c7 commit 9fd8097

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

README.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,3 +44,17 @@ The curator workflow is as follows:
4444
- [ ] If a proposal is accepted, update both the label AND status to 'accepted', and when closing select 'Close as completed'
4545
- [ ] If a proposal is turned down, update both the label AND status to 'turned-down', and when closing select 'Close as not planned'
4646
- [ ] 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'
47+
48+
### Request for Comment (RFC)
49+
50+
The curator workflow is as follows:
51+
52+
- [ ] Once a issue is made, update the 'Project' status to 'proposed' (right hand side bar, under 'new-<TYPE>-proposals')
53+
- [ ] Facilitate discussion on the the Issue thread, following the guidance [here](https://nf-co.re/docs/contributing/project_proposals).
54+
- [ ] Acceptance requires quorum from the nf-core core team, done via voting in comments with `/accept` or `/reject`
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)