About a year ago, Emmanuele posted RFC: Governance here. While some parts of his proposal are already taking shape, there hasn’t been any public progress on a Request for Comments (RFC) process for the GNOME project.
I am proposing an RFC framework which will also help us build future governance structures transparently and by consensus.
First of all, I am glad to see that this is going forward.
To (virtually) benchmark this, what would be examples of changes that would go through RFCs? Either past changes that lacked such process, or future changes that are currently blocked and that could go through an RFC process?
Unless I missed something, we need to start a list of teams, while a few of them are well established (design, release?), the scope/existence of several of them is less clear to me, especially for core apps or circle apps (?).
I’m very happy to see this proposal. Thanks for working on it, @sophieherold ! I like the general approach of starting simple and building from there.
My main two questions are:
What do you expect the comment period to be? I read over the proposal and couldn’t see it mentioned.
How will RFC’s be approved/rejected? The line in the proposal is “The decision is determined by the disposition, specified at the beginning of the final comment period.” “Disposition” here is editors + stakeholders? Does that basically mean that there must be no unresolved concerns from stakeholders for the RFC to be approved?
I’d be interested in contributing some smaller wording changes if that would be helpful. Let me know if you’d like me to follow up with an MR.