Documenting the governance of the git project?

Hi all,

As an occasional contributor to Git, I have been interested in getting a 
clear picture of the project's governance. By governance, I primarily 
mean a list of roles people can have in the project, the associated 
privileges and expectations, the ways people get in and out of those 
roles, and any decision processes in place for important matters (which 
`Documentation/DecisionMaking.adoc` already does a pretty good job at 
describing).

For instance, I'm aware that Junio is the one merging patches, but are 
any other responsibilities delegated to other contributors? What are the 
responsibilities of the Project Leadership Committee and how are its 
members renewed? If Junio wasn't available anymore, would there be an 
agreed on process to find a successor? Are those aspects of the project 
documented anywhere?

Through my experience in other projects, I have learned that it can be 
beneficial to write such things down. I think it can help avoid some 
conflicts, help onboard contributors, spread responsibilities in a more 
intentional way and increase the bus factor. See [1] for more background 
on the why and how of documenting governance. There is an emerging 
convention to document those things in a `GOVERNANCE.md` file at the 
root of the repository, but many projects choose to publish this 
information in other ways (such as on their website).

If there is interest, I would be happy to try and document this. All I 
need is the confirmation that people see value in maintaining such a 
piece of documentation, and the readiness of project leadership to 
answer my questions (which I would try to do in a way that respects 
their time, using the communication channel they prefer). I would then 
submit my write-up as a patch in the location/format you prefer. I would 
of course be delighted to team up with others in this endeavor.

Best,

Antonin

[1]: 
https://theopensourceway.github.io/production/en/growing-contributors/project-and-community-governance.html