RFC Process#
RFCs are proposals for changes to the GNOME project that have a broad impact or require conflict resolution. Proposals with the following characteristics will often be appropriate for an RFC:
the change has a large community impact
a process is stuck
the change is hard to undo
the change creates work for other people
disagreement is present or expected
The formal definition of the RFC process can be found in RFC 0001.
General Procedure#
It can often be helpful to have discussions with the relevant stakeholders before creating an RFC. The RFC itself is created as a merge request against the RFC repository. Additionally, an accompanying thread on Discourse must be created to discuss the RFC. Once the discussion has died down, a 14-day final comment period will be announced. After the final comment period has passed without any formal concerns being raised, the RFC is accepted.
Commenting on an RFC#
Everyone can comment on an RFC in the corresponding Discourse thread. Comments in the merge request are only allowed for pointing out typos and similarly trivial issues.
If a Foundation member has an objection to an RFC that they think must be addressed before the RFC can be accepted, they can raise a formal concern. This is done by writing a reply in the RFC’s Discourse thread beginning with **Concern:**. Another Foundation member can second the concern, which makes it an accepted concern.
Editing an RFC#
Only people listed as “Editors” in the RFC’s merge request description may edit an RFC.
The main responsibility of an editor is to incorporate relevant feedback into the RFC’s text. To this end, the editor adds new commits to the existing merge request. Existing commits are never changed or removed.
The other responsibilities of editors are:
Managing the accepted formal concerns by listing them in the description of the merge request, as well as aborting the final comment period if a concern is accepted.
Starting the final comment period.
Merging or closing the RFC, depending on its outcome.
Creating an RFC#
Every Foundation member can create an RFC by following these steps:
Fork the RFC repository and create a new branch via
git checkout -b wip/<your-gitlab-handle>/<rfc-title>.Copy the
0000-template.mdfile to thecontentfolder.Write your proposal in the new file. You can remove or add sections in the file as needed. There is no required structure.
Create a thread on Discourse under the rfc tag to discuss the RFC.
Create a merge request for your branch. The merge request title must be the
<rfc-title>. The merge request description should look like this:Stakeholders: People or teams that are affected by this RFC Editors: People or teams that can edit the RFC Discussion: <https://discourse.gnome.org/t/your-thread> ## Summary Short summary in one to three sentences ## Concerns *no concerns have been accepted yet*
Add all stakeholders as GitLab labels to the merge request if a label exists for them.
Rename your file via
git mv content/0000-template.md content/XXXX-your-title.mdto include the GitLab merge request number and your RFC’s title. The merge request number can be found in the merge request’s URL.Amend your commit, for example, via
git commit --amendand overwrite the merge request’s content withgit push --force-with-lease.Add the GitLab merge request URL to the Discourse thread.