From: Christian Couder <christian.couder@gmail.com>
To: Taylor Blau <me@ttaylorr.com>, Jeff King <peff@peff.net>
Cc: git <git@vger.kernel.org>, "Junio C Hamano" <gitster@pobox.com>,
"Christian Couder" <chriscool@tuxfamily.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: taking a break from Git
Date: Thu, 16 Dec 2021 10:46:05 +0100 [thread overview]
Message-ID: <CAP8UFD2pL3V2ty_TGiXkbDMG5YMUA815K=pW4zopGf57yiTheA@mail.gmail.com> (raw)
In-Reply-To: <YbohRy22vBuDZsG4@nand.local>
On Wed, Dec 15, 2021 at 6:09 PM Taylor Blau <me@ttaylorr.com> wrote:
>
> On Wed, Dec 15, 2021 at 11:38:25AM -0500, Jeff King wrote:
> > Hey all,
> >
> > I'm going to be offline and completely absent from the mailing list for
> > five months starting at the end of December. After that, things are up
> > in the air, but I may not be as involved in the project as I have been.
> >
> > Sorry, there's no juicy gossip or drama to share. I still like everyone,
> > and think it's a cool project. ;) After 15 years, it just feels like
> > it's time for a break and to perhaps apply my brain to something else
> > for a while.
>
> I am going to miss seeing patches and review from you tremendously.
Yeah, you will be missed a lot Peff!
[...]
> I am a better programmer and Git contributor directly because of Peff's
> efforts. I am sure that anybody who has been fortunate enough to get
> review or advice from Peff feels the same as I do.
Yeah, I feel the same too.
> > There are a couple logistical things related to this:
> >
> > - I'm planning to step down from Git's Project Leadership Committee
> > (the entity that represents Git within Software Freedom Conservancy,
> > and which occasionally makes decisions on things like our project
> > funds or assets like the trademark).
> >
> > That leaves Junio, Ævar, and Christian on the PLC, and the charter
> > calls for having at least 3 members. So I don't technically need to
> > be replaced, but maybe it's an opportunity for somebody else to get
> > involved.
> >
> > We don't have a formal process here. The last discussion on adding
> > new members was this thread from a few years ago:
> >
> > https://lore.kernel.org/git/20180816224138.GA15490@sigill.intra.peff.net/
>
> I would be honored to serve on the PLC if that is something others would
> be in favor of, too. I can talk a little bit about my background and
> thoughts here in a separate thread from this one.
I am in favor of you serving on the PLC and I would appreciate it if
others would nominate themself or others either publicly or privately
by emailing git@sfconservancy.org. I think it's a good idea to open
this up every few years.
> > - I maintain the git-scm.com site (well, insofar as anybody does).
> > There are a few regulars who review and merge pull requests at
> > https://github.com/git/git-scm.com, but more help is always welcome
> > there.
> >
> > The production parts of the site run on Heroku and Cloudflare. They
> > don't need touched often, though we do trigger a manual update and
> > flush the caches right after Junio releases, so that the site is
> > updated immediately. The Git PLC has the necessary credentials for
> > those sites, though in practice I think I'm the only one there that
> > touched it. Taylor (cc'd) has been helping out with that and also
> > has access.
>
> Yes, I have credentials to our Heroku and Cloudfare accounts, and (I
> believe) write access to the git-scm.com repository on GitHub. So I can
> help do some light triage there, and at least prevent the site from
> bit-rotting.
>
> I've been doing the post-release manual update and cache purging as part
> of my usual release routine for the past several releases, so I don't
> mind continuing to do that, either.
Thanks for doing this!
> > - I really am going to stop reading the list. Even if you cc me. So
> > please don't get mad if I don't review your patches, or respond to
> > bug reports. :)
>
> Please do ;). Enjoy your well deserved time off, and thank you.
Yeah, thanks!
next prev parent reply other threads:[~2021-12-16 9:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 16:38 taking a break from Git Jeff King
2021-12-15 17:09 ` Taylor Blau
2021-12-16 9:46 ` Christian Couder [this message]
2021-12-20 19:18 ` Kaartic Sivaraam
2021-12-15 18:42 ` Junio C Hamano
2021-12-16 14:26 ` rsbecker
2021-12-17 11:06 ` Phillip Wood
2021-12-20 12:45 ` Ævar Arnfjörð Bjarmason
2021-12-20 13:43 ` Jeff King
2021-12-21 16:02 ` Philip Oakley
2021-12-21 18:23 ` Elijah Newren
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP8UFD2pL3V2ty_TGiXkbDMG5YMUA815K=pW4zopGf57yiTheA@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=avarab@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).