Skip to content

update RFC curator workflow docs #38

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jun 3, 2025
Merged

update RFC curator workflow docs #38

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
708b427
update RFC curator workflow docs
maxulysse May 26, 2025
1ea0726
Apply suggestions from code review
maxulysse May 27, 2025
58bf41e
More details
maxulysse May 27, 2025
34a99c7
Merge branch 'main' into update_README
maxulysse May 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,3 +44,17 @@ The curator workflow is as follows:
- [ ] If a proposal is accepted, update both the label AND status to 'accepted', and when closing select 'Close as completed'
- [ ] If a proposal is turned down, update both the label AND status to 'turned-down', and when closing select 'Close as not planned'
- [ ] 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'

### Request for Comment (RFC)

The curator workflow is as follows:

- [ ] Once a issue is made, update the 'Project' status to 'proposed' (right hand side bar, under 'new-<TYPE>-proposals')
- [ ] Facilitate discussion on the the Issue thread, following the guidance [here](https://nf-co.re/docs/contributing/project_proposals).
- [ ] Acceptance requires quorum from the nf-core core team, done via voting in comments with `/accept` or `/reject`
- [ ] If a proposal is turned down, update both the label AND status to 'turned-down', and when closing select 'Close as not planned'
- [ ] 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.
- [ ] When the PR is opened the corresponding issue can be closed.
- [ ] Verify that feedback has been provided to the champion.
- [ ] Propose an optional Bytesize talk about the proposal.
Copy link
Member

@jfy133 jfy133 May 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Give a link to the channel for bytesize proposals

Copy link
Member Author

@maxulysse maxulysse May 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should the bytesize proposal to this repo...
I'll propose that during the next outreach meeting

Copy link
Member

@jfy133 jfy133 May 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea

- [ ] Finally merge the PR when the development is complete.