GNOME developers approved a new decision-making process based on publishing proposals in the form of RFC (Request for Comments) and their subsequent joint approval. The RFC model introduces strict regulations to increase transparency, structure the process, and transition to collective responsibility for the decision instead of personal responsibility. The RFC-based model will be used to resolve impasses in which consensus cannot be achieved, to approve architectural changes and major interface reworks, as well as to approve global changes in the project that affect the working methods of participants or the code of different applications and subsystems.
RFC promotion stages:
- Submitting the file RFC-XXXX-name.md with a structured proposal and link to the GNOME/rfcs repository for discussion.
- Discussion of the proposal on the Discourse platform with accompanying refinement and amendments to the RFC.
- Publication by participants of objections marked “**Concern**”, describing possible problems or proposing a different solution. If the objection is supported by the editor or one of the interested participants, it is transferred to the category of mandatory consideration.
- Consideration of the objections raised, development of measures to resolve them and amendments to the RFC.
- After completion of the discussion and consideration of objections, a 14-day final comment period (FCP, Final Comment Period) is announced, during which only new objections can be submitted. If the new objection is accepted, the discussion is restarted and the final comment period is shifted.
- After the final comment period has ended and all objections have been resolved, the RFC is either accepted or rejected.
/Reports, release notes, official announcements.