{"id":183253,"date":"2026-09-05T16:53:29","date_gmt":"2026-09-05T14:53:29","guid":{"rendered":"https:\/\/prohoster.info\/blog\/news\/reformirovanie-proczessa-utverzhdeniya-znachitelnyh-izmenenij-v-gnome"},"modified":"2026-09-05T16:53:33","modified_gmt":"2026-09-05T14:53:33","slug":"reforming-the-approval-process-for-major-changes-in-gnome","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/reforming-the-approval-process-for-major-changes-in-gnome","title":{"rendered":"Reforming the process of approving significant changes in GNOME","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
GNOME developers are discussing the implementation of a new decision-making process based on publishing proposals in the form of RFC (Request for Comments) and their subsequent collective approval. Participants of the GNOME Foundation are invited to join the discussion and provide their feedback by October 4. The RFC-based model is planned to be used only in special cases for resolving deadlocks, approving global changes in the project affecting the way participants work or different applications and subsystems, as well as architectural changes and major redesigns of the interface. <\/p>\n
It is noted that the currently practiced informal model based on individual decision-making leads to burnout among participants, prolonged disputes, and exhausting searches for consensus in chats. The new model offers a strict regulation to enhance transparency, structure the process, and shift to collective responsibility for decisions instead of personal responsibility. The drawbacks of the RFC-based governance model include the complexity of the process for some developers and the lack of a conflict resolution mechanism that leads to important RFCs stalling. <\/p>\n
Stages of promoting an RFC: <\/p>\n
\n
Submission to the GNOME\/rfcs repository of the RFC-XXXX-title.md file with a structured proposal and a link to the discussion.\n
Discussion of the proposal on the Discourse platform with concurrent refinement and amendments to the RFC.\n
Publication of objections by participants marked as «**Concern**», describing potential issues or suggesting alternative solutions. If the objection is supported by the editor or one of the interested participants, it is elevated to mandatory consideration.\n
Reviewing the raised objections, developing measures to address them, and making changes to the RFC.\n
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.\n
After the final comment period and resolution of all objections, the RFC is either accepted or rejected. <\/ul>\n