Using RFCs

RFC: Using RFCs

This is a first RFC to explain and bootstrap an RFC process.

Details about the RFC itself can be found in the file below the rfcs/ directory.

A more detailed description about the process can be found in the README document.

Additionally, there is an RFC template in the rfcs/ directory (as template for upcoming merge requests - i.e. a new RFC) and an issue template in the .gitlab/issue_templates/ directory (as issue template to discuss RFC ideas).

Please review all files and make note of any unclear wording or process steps.

NOTE: For a better reading experience, it is easiest to browse the branch, this merge request is created from.

TODO

The following steps are necessary to allow the new process to potentially be established. They are specific to this RFC only and are here as a reminder/note.

• Announce and start final discussion round for approval on arch-dev-public

added 2 commits

• 3b7b9c20 - Add RFC about using the RFC process
• 5305fe30 - Add issue template for RFC ideas

Compare with previous version

Perhaps we should add an "Alternatives Considered" section. This would be helpful to document the alternative approaches that were considered, and how they fall short in face of the current proposal.

I think another drawback of this RFC format is that rather than discussion coming to each person (like with a mailing list), each person must remember come here to see the discussion.

I know GitLab allows for email notifications on discussions, but it breaks the logical converstion flow and threading.

changed the description

added 3 commits

• 21ba553a - Add an RFC template
• 4cc96473 - Add RFC about using the RFC process
• c93410c0 - Add issue template for RFC ideas

Compare with previous version

resolved all threads

I think this RFC should not be discussed here. You are enforcing the process to discuss the adoption of the process... Almost as if using this process was already decided.

changed the description

resolved all threads

added 1 commit

• fd7b3027 - Add issue template for RFC ideas

Compare with previous version

added 4 commits

• d6636a31 - Add description of RFC process
• 1f47668b - Add an RFC template
• 5944b402 - Add RFC about using the RFC process
• e061efe5 - Add issue template for RFC ideas

Compare with previous version

added 4 commits

• 5217492e - Add description of RFC process
• 3aaa8a23 - Add an RFC template
• ce44b13f - Add RFC about using the RFC process
• b458581e - Add issue template for RFC ideas

Compare with previous version

resolved all threads

I was wondering if we could leverage the approvals feature on Gitlab? Although it would require adjusting some permissions, I can see approvals section but I cannot leave an approval myself.

added 1 commit

• 72df2f61 - README: Section about who can file an RFC

Compare with previous version

added 1 commit

• 25ab6ac1 - RFC: Expand on who can create an RFC

Compare with previous version

marked the checklist item Announce and start final discussion round for approval on arch-dev-public as completed

added 2 commits

• 20e53340 - README: Mention GitLab approval feature
• f2bac9a1 - RFC: Mention GitLab's approval feature

Compare with previous version

added 1 commit

• e0daf5c6 - Add gitlab-ci integration and Makefile

Compare with previous version

resolved all threads

added 5 commits

• 9a823092 - Add description of RFC process
• 9201828a - Add an RFC template
• 771cc4c2 - Add RFC about using the RFC process
• 6b99ac8d - Add issue template for RFC ideas
• 143f9232 - Add gitlab-ci integration and Makefile

Compare with previous version

merged

mentioned in merge request pacman/pacman!140