-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
Conversation
Co-authored-by: Phil Ewels <phil.ewels@seqera.io>
| - [ ] 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. |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea
|
can this be merged, @maxulysse ? |
To be merged after nf-core/website#3367