GNOME Overhauls Major Change Approval Process

GNOME developers are currently discussing the implementation of a new decision-making process based on the publication of proposals in the form of an RFC (Request for Comments) and their subsequent joint approval. The discussion is open to GNOME Foundation members, who are invited to provide comments on the proposal by October 4th. This RFC-based model is intended to be used in special cases to resolve deadlock situations, approve global changes in the project affecting working methods, code of applications, subsystems, architectural changes, and major interface reworks.

The informal decision-making model currently in practice has been leading to participant burnout, prolonged disputes, and challenges in finding consensus. The new model aims to introduce strict regulations to increase transparency, structure the process, and shift towards collective responsibility for decisions rather than individual ones. However, some developers may find the RFC-based management model complex and there is a need to establish a mechanism for conflict resolution to avoid the freezing of important RFCs.

The stages of promoting an RFC include sending the RFC-XXXX-name.md file to the GNOME/rfcs repository with a structured proposal and a link to the discussion, followed by discussion on the Discourse platform with refinement and amendments. Participants can publish objections marked with “**Concern**” to highlight possible problems or propose alternative solutions. Objections must be considered, resolved, and incorporated into the RFC. A 14-day Final Comment Period (FCP) is then announced for additional objections before the final decision to accept or reject the RFC.

/Reports, release notes, official announcements.