git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Taylor Blau <me@ttaylorr.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	shejialuo <shejialuo@gmail.com>,
	git@vger.kernel.org
Subject: Re: the latter half of october, the maintainer goes offline
Date: Mon, 7 Oct 2024 07:47:07 +0200	[thread overview]
Message-ID: <ZwN10b28Aaj3roz2@pks.im> (raw)
In-Reply-To: <ZwBtwFeVYmu6/Sc0@nand.local>

On Fri, Oct 04, 2024 at 06:35:44PM -0400, Taylor Blau wrote:
> On Fri, Oct 04, 2024 at 09:58:52AM -0700, Junio C Hamano wrote:
> > shejialuo <shejialuo@gmail.com> writes:
> >
> > > On Fri, Oct 04, 2024 at 05:22:27PM +0200, Patrick Steinhardt wrote:
> > >
> > > [snip]
> > >
> > >> There are two maintainership models I can think of: either a single
> > >> individual or a group of people would take over.
> > >>
> > >>   - A single individual needs funding. The ideal situation would be if
> > >>     that funding came independent of any of the large forges. Or
> > >>     alternatively, the big players in this context come together to all
> > >>     pay into the same pot to fund that person. In theory, the role could
> > >>     be elected and serve for a limited amount of time so that overall,
> > >>     the community is in control.
> > >
> > > Well, I think we cannot easily fund a single individual. It it is a
> > > full-time job, we have to also pay for the insurances. I don't know
> > > how to hire an individual in an open source project. But intuitively I
> > > think there would be a lot of trouble here due to the laws.
> 
> It is definitely true that the Git project alone could not fund a full
> year of the maintainer's salary [1].

Yes. As Junio said, ...

> > I think the model Patrick has in mind for the above is like how
> > Linux Foundation hires Linus Torvalds to work full time on Linux,
> > while the Foundation is funded by large industry players.

... something like this is what I have in mind here.

> > Git has become important enough that such a model may be workable,
> > and that may make it easier to maintain appearance of impartiality
> > by whoever is being funded.

Indeed. There's at least two large companies that care very deeply about
Git being healthy in the long term. So securing funding from those
companies should be a no-brainer for them.

> Sure, though I would add that my personal feeling is that it is a
> possibility, not a requirement, that the maintainer's funding come from
> either an independent entity (like the Linux Foundation) or from a pool
> funded by industry leaders.
> 
> I say that only to point out that while Junio is employed by Google, I
> don't think any of us would doubt his impartiality with regard to the
> project.

Oh, yes, and I've explicitly mentioned that Junio is doing an awesome
job of that indeed. But I see the employment by Google as kind of an
outlier here, because Google itself is not really competing in the Git
ecosystem. They do not sell a Git-based product directly to customers as
both GitHub and GitLab do, to the best of my knowledge.

> I think as long as the maintainer's employer does not unfairly influence
> the maintainer's decisions on their behalf, then it is OK.

So yes, I would probably be okay with a maintainer that is employed by a
company which I don't see as competing in this space. But I would
strongly disagree with this statement if the intent were to ever have a
GitHub or GitLab employee become the single maintainer.

Impartiality is only one part of the picture here. The other part is
that Git would start to feel like a project owned by that company. There
simply is too much political tension for this to work out in the long
term, in my opinion.

So if we do not have an individual at the ready that is independent,
then I would strongly favor a model where the maintainer role is shared
across a group of people.

Patrick

> Thanks,
> Taylor
> 
> [1]: https://lore.kernel.org/git/Zusxcweod1O88h7j@nand.local/

  reply	other threads:[~2024-10-07  5:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-03 17:26 the latter half of october, the maintainer goes offline Junio C Hamano
2024-10-03 17:53 ` Taylor Blau
2024-10-04 15:22   ` Patrick Steinhardt
2024-10-04 16:31     ` shejialuo
2024-10-04 16:38       ` shejialuo
2024-10-04 16:58       ` Junio C Hamano
2024-10-04 22:35         ` Taylor Blau
2024-10-07  5:47           ` Patrick Steinhardt [this message]
2024-10-07 14:56             ` Taylor Blau
2024-10-07 15:28               ` Patrick Steinhardt
2024-10-04 22:47     ` Taylor Blau
2024-10-08 16:56       ` Junio C Hamano
2024-10-09  5:51         ` Patrick Steinhardt

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=ZwN10b28Aaj3roz2@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=me@ttaylorr.com \
    --cc=shejialuo@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;
as well as URLs for NNTP newsgroup(s).