Re: Documenting the governance of the git project?

From: Christian Couder <christian.couder@gmail.com>
Date: Oct 6, 2026, 11:47 UTC
Message-ID: <CAP8UFD1yx_Z+TyxYP6GA3xKOq12Y5OWfEbiHOEhx9bVZwZ0egw@mail.gmail.com>
In-Reply-To: <97c58bb0-5030-4e66-b183-44db2ab216db@delpeuch.eu>

Hi Antonin,

On Tue, Oct 6, 2026 at 1:13 PM Antonin Delpeuch <antonin@delpeuch.eu> wrote:

Show 14 quoted lines

>
> Hi all,
>
> I am planning to go ahead with this project, unless anyone thinks it's a
> bad idea.
>
> My plan is to write an initial document based on the information I can
> find on my own, and then fill the gaps by asking questions about the
> points I couldn't figure out myself.
>
> It would be great if I don't have to bother Junio too much with those
> questions, so if you have a good grasp of the social structures in place
> in this project, I'd appreciate it a lot if you could let me know you're
> available to help.

If you write an initial document and send it to the list as a patch to add that document to the Git code base, that would be a good start.

The people who will reply to your patch will be the people willing to help. That's how it works here. Someone could tell you they are willing to help but then for example get sick or have a vacation when your first draft is ready, and cannot actually help. That's why it's better if the process does not rely on people making such promises.

> My goal will be to write something that you are happy to include in the
> official documentation or website, but if that doesn't work out, I'll
> publish it externally (making its unofficial status clear, of course).

Sure, no worries. I think we are not perfect, but overall do a good job at helping people who are willing to put some effort in useful quality work. In this case, if it's not accepted in the code base, nor on the git-scm.org website, maybe we will accept it on the Git Developer Pages at https://git.github.io/ or as a "How the Git project works" article in Git Rev News. Just trust the process and community as a whole that you are going to describe in your document ;-)

Best, Christian.