git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: shejialuo <shejialuo@gmail.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Taylor Blau <me@ttaylorr.com>, Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: the latter half of october, the maintainer goes offline
Date: Sat, 5 Oct 2024 00:38:11 +0800	[thread overview]
Message-ID: <ZwAZ82gevwT2TDgL@ArchLinux> (raw)
In-Reply-To: <ZwAYccsboGIhGVIx@ArchLinux>

> 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. As far as I
> know, Junio is working at Google.
> 
> So, the biggest problem here is that most of us either work at other
> companies for full-time job which are not unrelated to Git or work at
> companies which are related to Git(upstream). Although it is an honor to
> be hired by an open source project, there are still many concerns for an
> individual.
> 

"which are not unrelated to Git" should be "which are unrelated to Git".
Sorry for typos here.

> From my perspective, we already did this. Junio will rely on the reviews
> from other contributors. This is what I got from the Git Contributor's
> Summit, 2024: [TOPIC 10/11] Project Tracking.
> 
>   https://lore.kernel.org/git/xmqqployf6z5.fsf@gitster.g/
> 

I forgot to show my intention here. I do not think we need to really
distinguish these two modes. Even if we hire an individual, the
individual still needs the help from the community about the unfamiliar
fields.

  reply	other threads:[~2024-10-04 16:38 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 [this message]
2024-10-04 16:58       ` Junio C Hamano
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=ZwAZ82gevwT2TDgL@ArchLinux \
    --to=shejialuo@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=me@ttaylorr.com \
    --cc=ps@pks.im \
    /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).