Re: taking a break from Git

[Philip Oakley <philipoakley@iee.email>]

On 15/12/2021 16:38, 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.

May I wish you a very happy Christmas, a great New Year and enjoyable break.

Thank you for all the contributions and help over the years, and it was
good to see you at Git Merge 2019 (seems so long ago now)

All the best

Philip

>
> 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.
>
> 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 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.
>
>     If you want to get involved, I'd suggest subscribing to the repo
>     linked above, and just helping out with issue/PR triage and
>     response.  And of course bug fixes, features, and content updates
>     are welcome, too. The README.md and ARCHITECTURE.md documents give
>     an overview.
>
>   - 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. :)
>
>     Likewise, I'll be around for a bit more, and am trying to wrap up
>     some personal topics and reviews. But undoubtedly I'll end up
>     dropping many on the floor. Though that probably would have happened
>     over the holidays anyway!
>
> -Peff