[RFC-0000] Introduce the Flux RFC template

[stefanprodan]

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.

[darkowlzz]

Thanks for putting this together.
LGTM!

[hiddeco]

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. 🙇

[stefanprodan]

@hiddeco once this is merged, next step is to update https:/fluxcd/community/blob/main/GOVERNANCE.md#proposal-process and link to this readme, as now we only link to fluxcd/flux2/discussions

[yebyen]

I like the structure! I found a few RCFs which I assume should read RFC. 👍 LGTM with fixes

[makkes]

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.

[stefanprodan]

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 rfc-0000 with the template makrdown in the README.md. People will copy the dir, fill the RFC number and the template.

[squaremo]

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)?

[squaremo]

I'm happy that the process and template are sensible 👍
Thanks for setting our RFC system in motion Stefan 🍇

[hiddeco]

Thanks a lot for putting work into this @stefanprodan, and an additional 🎩-tip for following up on all comments (and nitpicks) to reach consensus. 🍍