-
Notifications
You must be signed in to change notification settings - Fork 618
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
[RFC-0000] Introduce the Flux RFC template #2085
Conversation
d6e08ab
to
ab10aa0
Compare
ab10aa0
to
543b9da
Compare
543b9da
to
ff8de03
Compare
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.
Thanks for putting this together.
LGTM!
ff8de03
to
6539c82
Compare
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.
The PR is filled against fluxcd/flux2
(and not e.g. fluxcd/community
), making the scope of this template limited to fluxcd/flux2
and fluxcd/*-controller
(I assume). Can we documented this scope?
Other than that (and the tiny nitpick comment), I think this is a good step forward. 🙇
@hiddeco once this is merged, next step is to update https://github.com/fluxcd/community/blob/main/GOVERNANCE.md#proposal-process and link to this readme, as now we only link to fluxcd/flux2/discussions |
1458684
to
30555b7
Compare
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.
I like the structure! I found a few RCFs which I assume should read RFC. 👍 LGTM with fixes
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.
I love seeing the process being streamlined a bit more! Maybe the template should be in a file of its own so people can just copy that and start writing their proposal.
Yes, once this gets approved I'll create a dir |
daf2d1e
to
6d94ffa
Compare
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.
The RFC process is mentioned twice, but not described here. Is it yet to be explained (in which case I suggest putting it after the examples of substantial changes), or elsewhere (in which case, a link would be good)?
The RFC template is heavily inspired by Rust RFCs and Kubernetes KEPs. Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
507c787
to
6dcd9bc
Compare
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.
I'm happy that the process and template are sensible 👍
Thanks for setting our RFC system in motion Stefan 🍇
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
d40a116
to
f4ebf31
Compare
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
f4ebf31
to
2c3cb1a
Compare
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.
Thanks a lot for putting work into this @stefanprodan, and an additional 🎩-tip for following up on all comments (and nitpicks) to reach consensus. 🍍
In many cases, new features and enhancements are proposed on flux2/discussions.
A proposal is discussed in public by maintainers, contributors, users and other interested parties.
After some form of consensus is reached between participants, the proposed changes go through the
pull request process where the implementation details are reviewed, approved or rejected by maintainers.
Some proposals may be substantial, and for these we ask for a design process to be followed
so that all stakeholders can be confident about the direction Flux is evolving in.
The "RFC" (request for comments) process is intended to provide a consistent and
controlled path for substantial changes to enter Flux.
The RFC template is heavily inspired by Rust RFCs and Kubernetes KEPs.