From: Junio C Hamano <gitster@pobox.com>
To: shejialuo <shejialuo@gmail.com>
Cc: Patrick Steinhardt <ps@pks.im>, Taylor Blau <me@ttaylorr.com>,
git@vger.kernel.org
Subject: Re: the latter half of october, the maintainer goes offline
Date: Fri, 04 Oct 2024 09:58:52 -0700 [thread overview]
Message-ID: <xmqqmsjjereb.fsf@gitster.g> (raw)
In-Reply-To: <ZwAYccsboGIhGVIx@ArchLinux> (shejialuo@gmail.com's message of "Sat, 5 Oct 2024 00:31:45 +0800")
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.
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.
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.
next prev parent reply other threads:[~2024-10-04 16:58 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 [this message]
2024-10-04 22:35 ` Taylor Blau
2024-10-07 5:47 ` Patrick Steinhardt
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=xmqqmsjjereb.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=ps@pks.im \
--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).