From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
Patrick Steinhardt <ps@pks.im>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
BERENDSEN Arnoud <arnoud.berendsen@soprasteria.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Cleaning up "contrib/"
Date: Wed, 14 May 2025 13:05:36 -0700 [thread overview]
Message-ID: <xmqqo6vv7yb3.fsf@gitster.g> (raw)
In-Reply-To: <20250514181938.GC2196784@coredump.intra.peff.net> (Jeff King's message of "Wed, 14 May 2025 14:19:38 -0400")
Jeff King <peff@peff.net> writes:
> Right, I know people use them. What I meant was that if we wanted to
> spin them to out-of-tree projects, we'd need somebody to volunteer to be
> the maintainer of those projects. If they stay in-tree we can be a bit
> looser (your "I don't want to be _the_ maintainer, but I can
> contribute").
>
> It does put more load on Junio, though. E.g., if there is a security
> problem the project has to deal with embargoed release engineering,
> whereas a separate project would do its own releases.
Well, but it certainly is not more than what I currently need to do;
it does not make any difference whether it is housed in the contrib/
directory or in the tools/ directory.
> Last time wincred had a security hole (in 2020), the phrase "unsafe and
> unmaintained" was thrown about on the security list, but we ultimately
> fixed at least the immediate issue. But I find its general matching
> strategy to be not very confidence-inspiring.
>
> Dscho (or anybody else familiar with Windows) may want to comment
> further.
Thanks for a redirect.
prev parent reply other threads:[~2025-05-14 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 13:59 git svn clone failed BERENDSEN Arnoud
2025-05-04 8:19 ` Johannes Schindelin
2025-05-05 6:24 ` Cleaning up "contrib/" (was: git svn clone failed) Patrick Steinhardt
2025-05-05 7:36 ` Johannes Schindelin
2025-05-05 9:44 ` Patrick Steinhardt
2025-05-05 19:10 ` Cleaning up "contrib/" Junio C Hamano
2025-05-06 5:40 ` Patrick Steinhardt
2025-05-12 13:50 ` Jeff King
2025-05-13 0:13 ` brian m. carlson
2025-05-13 9:06 ` Patrick Steinhardt
2025-05-13 16:59 ` Junio C Hamano
2025-05-14 18:19 ` Jeff King
2025-05-14 20:05 ` Junio C Hamano [this message]
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=xmqqo6vv7yb3.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=arnoud.berendsen@soprasteria.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=ps@pks.im \
--cc=sandals@crustytoothpaste.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.
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).