A place to submit, discuss and host Request for Comments (RFCs)
An RFC (Request for Comments) is a document, in our case a markdown file, that seeks to suggest a change to a software, in our case the Australian Government Design System, by outlining:
- The problem it seeks to fix
- An overview of the proposed change
- Technical description
If you have identified a change you'd like to see in the Australian Government Design System then please submit an RFC to this repository.
- Duplicate
RFCs/RFC-by-stage/1-approved/_RFC-template.md
toRFCs/RFC-by-stage/1-approved/[YOUR RFC NAME].md
- Fill out all the sections
- Do not change the status at the top of the file
- Do not remove the
_RFC-template.md
file
- Submit your PR
(đź’ˇ The template comes with hints and sections to help you navigate it.)
An RFC can be merged when it receives an absolute majority of approvals from Maintainers.
- The first stage a new RFC will be in is
draft
while it is being discussed in the PR stage. - The second stage is
approved
after it is merged into theRFCs/1-approved/
folder. - The third stage is
ready-for-implementation
which means the RFC is looking for people to implement it. Come here if you're looking to contribute. - The forth stage is
being-implemented
and this is where all RFCs land when they have not been finished but have dedicated people working on it already. The people implementing will be noted at the top of the RFC. - The fifth stage is
implemented
and that's where all RFCs land when they have been finished and are live.
Maintainers will look at your RFC and discuss it in your PR.
You can also ask for help with the RFC process on Slack at #ref-help.
An RFC can be merged once it has an absolute majority of PR approvals of all maintainers.
Make sure you check the list of maintainers, since the number of maintainers may vary.
Anyone may pick up an RFC and ask to implement it.
To raise your hands to implement an RFC submit a PR to the RFC document and add your name to the Implementer:
section at the top.
RFCs by processing stage are tracked on this Board.
RFCs that are "In Progress" should be tracked at a new GitHub Projects board here. It should be clear how work will be broken down and assigned. Groups should also create a Slack channel with prefix "feature-", ie "feature-my-rfc-idea" and invite relevant people.