-
Notifications
You must be signed in to change notification settings - Fork 134
Update RFC process #2716
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
Update RFC process #2716
Conversation
Try to reduce the scope of the RFC
Suggest breaking the RFC review.
replace `--enable-unstable`
JustusAdam
left a comment
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.
A suggestion we had discussed before is adding who the intended audience for the RFC or each individual section is (if they differ). That should help the submitter understand what level of detail is expected and help them empathize with their audience. The UX section kinda has that already, but it's something that I think is worth emphasizing and putting either globally or in every section.
Co-authored-by: Felipe R. Monteiro <[email protected]> Co-authored-by: Zyad Hassan <[email protected]>
Co-authored-by: Adrian Palacios <[email protected]>
Description of changes:
I would like to incorporate a few suggestions to the RFC process and template:
--enable-unstableby-Zflag.The main goal is to try to speed up the process by reducing the scope of the RFC document, breaking it down into multiple steps, and even reduce the need for an RFC entirely.
Resolved issues:
N/A
Related RFC:
Optional #ISSUE-NUMBER.
Call-outs:
Testing:
How is this change tested?
Is this a refactor change?
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.