The GNOME project has implemented a new decision-making process based on RFC.

GNOME developers have approved a new decision-making process based on publishing proposals in the form of RFC (Request for Comments) and their subsequent collective approval. The RFC model introduces a strict framework to enhance transparency, structure the process, and shift towards collective responsibility for decisions rather than individual ones. The RFC-based model will be used to resolve stalemates where consensus cannot be achieved, to approve architectural changes and major interface overhauls, as well as to endorse global changes in the project affecting participants' work methods or the code of various applications and subsystems.

Stages of promoting an RFC:

• Submission to the GNOME/rfcs repository of the RFC-XXXX-title.md file with a structured proposal and a link to the discussion.
• Discussion of the proposal on the Discourse platform with concurrent refinement and amendments to the RFC.
• Publication by participants of objections marked as '**Concern**', describing possible problems or suggesting alternative solutions. If the objection is supported by the editor or one of the interested participants, it is elevated to mandatory consideration.
• Reviewing the raised objections, developing measures to address them, and making changes to the RFC.
• After the discussion and review of objections are completed, a 14-day final comment period (FCP, Final Comment Period) is announced, during which only new objections can be raised. If a new objection is accepted, the discussion restarts, and the final objection acceptance period is postponed.
• After the final comment period and resolution of all objections, the RFC is either accepted or rejected.

Source: opennet.ru