(RFC) Draft initial RFC guidance #868
Conversation
This change adds the `.rfc` folder to the project with draft documentation for the RFC process, an RFC template, and scaffolded folders for accepted RFCs (`.rfc/draft`) implemented RFCs (`.rfc/final`).
|
|
||
| - **Author**: All members of the community are allowed to author new RFCs and can provide feedback | ||
| to any RFC. | ||
| - **DSC Committee**: The design committe that votes to accept or reject an RFC. Currently, the DSC |
There was a problem hiding this comment.
Since DSC team members are also members of the DSC WG, I wonder if we need to have a Committee above it
There was a problem hiding this comment.
I'm in favor of streamlining this to only including the working group for the time being - if we need to add a higher layer later, we can always amend the process for that.
|
|
||
| When submitting an RFC, the Author shall: | ||
|
|
||
| - Create a file named `RFCNNNN-<Title>.md` in the `.rfc/drafts` folder. |
There was a problem hiding this comment.
Is there a reason to use .rfc instead of just RFC? I don't see a need for it to be hidden?
There was a problem hiding this comment.
Habitual on my part - rfc/ works just as well.
| becomes harder to change at the risk of compatibility. | ||
|
|
||
| This process was adapted from the PowerShell RFC process, which itself was adapted from the Chef | ||
| RFC process and the DMTF.org process. |
There was a problem hiding this comment.
Since we don't want/need to have all the docs from the PowerShell repo, we can probably just link to relavent docs in the PS repo as applicable here. For example, I would still prefer community members to start with an issue/discussion instead of spending time on an RFC. This is somewhat covered below in the roles, but I'd rather put it up front so we don't suddenly get a bunch of RFC PRs.
| After the author marks their PR as ready for review, the RFC moves into the formal review state. | ||
| The RFC remains in this state until one of the following conditions is met: | ||
|
|
||
| - The Committee decides to reject the RFC, changing the state to [Rrejected](#rejected). |
There was a problem hiding this comment.
| - The Committee decides to reject the RFC, changing the state to [Rrejected](#rejected). | |
| - The Committee decides to reject the RFC, changing the state to [Rejected](#rejected). |
PR Summary
This change adds the
.rfcfolder to the project with draft documentation for the RFC process, an RFC template, and scaffolded folders for accepted RFCs (.rfc/draft) implemented RFCs (.rfc/final).PR Context
Drafting an RFC process to address growing need for more in-depth design documents/discussion than we can review in issues or discussions alone.