GNOME Stakeholders Discussing RFC Process For Solving Major Technical Changes

GNOME has been working to establish a formal request for comments (RFC) process for solving major technical questions and changes moving forward. A drafted RFC is now under discussion by GNOME stakeholders for moving this process forward. Sophie Herold published the draft RFC process this week for discussion. This is to ultimately succeed the long-used, ad-hoc and informal process by GNOME developers in making major changes. The proposed RFCC comes down to: ## Summary * RFCs will be used as the process for proposing major changes which have broad repercussions * Each RFC will be a written proposal which is added to the RFC project as a merge request * Stakeholders will be identified and notified of each RFC; teams can also identify themselves as stakeholders * The discussion of an RFC happens on Discourse * Anyone can raise concerns about an RFC, work to resolve these is made after the concern has been accepted by the RFC editors * Anyone can propose changes to an RFC * Once discussion has died down, the final comment period will be announced, with a proposal to either accept or reject the RFC. After this point, there are 14 days to raise new concerns before the RFC is accepted/rejected. Those curious about this proposal can find it in full via this merge request. The RFC is being discussed on GNOME Discourse. In addition to the RFC discussion kicking off this week, This Week in GNOME also highlighted a number of other recent GNOME changes. Some of the other activities include enhancements made to the Nautilus file manager this cycle and even a new GNOME Shell extension for The Matrix-inspired falling digital rain on your desktop.