From: Junio C Hamano <gitster@pobox.com>
To: Antonin Delpeuch <antonin@delpeuch.eu>
Cc: Antonin Delpeuch via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Christian Couder <christian.couder@gmail.com>
Subject: Re: [PATCH] doc: document the current project governance
Date: Fri, 06 Nov 2026 10:31:14 -0800 [thread overview]
Message-ID: <xmqq4idtke19.fsf@gitster.g> (raw)
In-Reply-To: <e977b49f-8462-4b63-bdff-daee75994a36@delpeuch.eu> (Antonin Delpeuch's message of "Fri, 6 Nov 2026 13:10:24 +0100")
Antonin Delpeuch <antonin@delpeuch.eu> writes:
> Do you know who moderates the IRC channel and the Discord server? Is it
> also the PLC?
No and I do not know.
>>> +=== Project Leadership Committee
>>> +
>>> +The Project Leadership Committee (PLC) liaises between the project
>>> +and the Software Freedom Conservancy, Git's fiscal sponsor.
>> We are a "member project" of SFC, which acts as our "fiscal sponsor"
>> for us, providing non-profit administrative, financial and legal
>> infrastructure.
> Is this a comment, or text that you would like to see part of the
> document? I think it's a good idea to make the term "fiscal sponsor"
> more precise as you did, as it's a confusing term for many people (who
> might otherwise think that SFC funds the Git project).
Exactly.
> Thanks. I think it would be worth documenting who is able to add
> subscribers to this list. I am assuming you are, but are you the only one?
You ask for membership for the security mailing list and access to
other resources necessary for the security related discussions and
reviews, and releases by asking <git-security@googlegroups.com>.
You will get a response for by somebody, then join the security
mailing list (or not).
I do not know if it is necessary to advertise anything beyond that
to the general public.
>>> +=== Localization maintainer
>>> +
>>> +Jiang Xin coordinates the localization of Git by maintaining https://github.com/git-l10n/git-po[git-po].
>>> +
>>> +NOTE: How would their successor be appointed?
>> Not limited to this, but there is in general no "appointing"
>> process. If there becomes an open seat that needs to be filled,
>> it will stay vacant until somebody volunteers.
>
> Makes sense. Here again, I should have asked my question differently:
> who is able to give the necessary permissions to a new localization
> maintainer? Are you an "Owner" of the https://github.com/git-l10n org?
>
> Or would you just stop pulling localization changes from this repository
> into your tree, and point it to another repository, where the new
> localization maintainer would have the necessary permissions?
It is something to be decided when the time comes.
Jiang volunteered, set up a repository, and I respond to pull
requests from there. When Jiang wants to hand it over to somebody
else, the successor may have to be somebody who are already well
known in the community around here that people trust, or perhaps
there is some effort for the successor to gain the necessary trust.
The successor may inherit the current repository or set up a new one
to be pulled from.
prev parent reply other threads:[~2026-11-06 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 15:13 [PATCH] doc: document the current project governance Antonin Delpeuch via GitGitGadget
2026-11-02 22:57 ` Junio C Hamano
2026-11-06 12:10 ` Antonin Delpeuch
2026-11-06 18:31 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq4idtke19.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=antonin@delpeuch.eu \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox