Introduce temporary voting process to approve jj governance structures #4400
Conversation
|
While this is LGTM, shouldn't the temporary governance be RFC 0? So I'd move it under |
Oh interesting! Would you rather see this doc explicitly outline that new proposals should go in |
Since it lays it out as that we start a RFC process, kinda (it also reminded me of my comment here #1411 (comment)). I'm not sure that they should move though, as each RFC could also have a "approved:" field with the final decision. |
Kinda. But kinda not :) It's a temporary process - one of the things we want to use this process to approve is an actual formal RFC process. So I don't know if I want to unilaterally guess what that RFC process is (that's one thing the working group hasn't talked about yet pretty much at all). Although it's easy to move things around later if we change our minds. |
|
looks pretty good. certainly adequate for a bootstrap process |
Since it's fine as is, we can postpone this and keep the |
Since CI passed, we know that this builds fine, but if you really wanted to check it manually, you'd need to use |
|
Rust's "this is the RFC for the RFC process" ended up being RFC 2, let alone zero, haha! I have no strong opinions on the topic, just thought it was a fun fact. |
In order for the governance working group to make progress establishing jj's governance structure, we need the approval of the jj community. Set up a temporary voting process to get that approval. Additionally, set up a governance dir for other governance-related documentation to sit in. Later, when we have a permanent governance structure and enough policy to let the community make changes without needing the governance working group, we can delete this document.
Hi! I'm Emily, part of the governance working group. I am not a regular contributor to jj, but part of my role at Google is to guide open source projects in Martin's and my organization, helping make sure our upstream communities are healthy and productive.
The governance working group (me, @arxanas, @thoughtpolice, and @martinvonz) wants to be able to get community approval on governance structure changes. Bootstrapping is hard - how do you get community approval for a process to get community approval? - so we're introducing this process by the normal pull request workflow.
Things to keep in mind:
Things I'm especially interested in during review:
governance/dir? (FWIW, I rancargo docand it passed with warnings unrelated to this file, but I'll openly admit that this is the first time I've built anything in jj and I might have missed :) )