From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: the latter half of october, the maintainer goes offline
Date: Thu, 03 Oct 2024 10:26:19 -0700 [thread overview]
Message-ID: <xmqqh69thzd0.fsf@gitster.g> (raw)
I plan to go offline for the latter half of this month (I may
sporadically pop up but may not be engaging deeply in the
discussions or picking up patches).
This time, can we try a fire drill that I do not nominate or ask
anybody to be an interim maintainer and see how well community
manages the discussion and patch flow during these two weeks?
It can be somebody stepping up and say "ok, I'll self nominate and
run the project as the interim maintainer, just like it was done in
the past years", or "let's do something differently, how about
everybody throws a merge request to this mob repository, use this
(possibly different) review procedure, and give back the tip of
'master' when Junio returns", or "OK, we'll discuss and exchange
patches for these two weeks among ourselves and we can cope without
a central meeting place".
IOW, I am interested to see if the community comes up with a
day-to-day project structure that may be better for the contributors
than what I have dictated in the past during my vacation time.
Thanks.
next reply other threads:[~2024-10-03 17:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 17:26 Junio C Hamano [this message]
2024-10-03 17:53 ` the latter half of october, the maintainer goes offline 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
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=xmqqh69thzd0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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).