From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] How to improve detection of unmaintained packages?
Date: Sat, 23 Mar 2019 15:36:18 -0400 [thread overview]
Message-ID: <CAGfcS_n+SRGiDvDdObYfGOAQDmUhc=vhXGD2uOVDRKbOu0tj7Q@mail.gmail.com> (raw)
In-Reply-To: <CAAr7Pr_5y5By2c6zD-dS1u-SkrmJUfgkEfj72iH+q=HVipvoHA@mail.gmail.com>
On Sat, Mar 23, 2019 at 3:22 PM Alec Warner <antarus@gentoo.org> wrote:
>
> I'm not saying "we should absolutely remove packages that have not been touched in N years" but I am saying "we should review packages that have not been touched in N years".
++
> Have you looked at mgorny's recent removals? its mostly stuff that doesn't build and hasn't been touched in 5 years and *yeah* I want that stuff out of the tree; its a net negative for everyone. Keeping packages in the tree isn't free.
Also, ++
I completely support the general intent. I'm just trying to maintain
balance as well. A good approach would be to just auto-file a bug as
a ping and let the maintainer ack it as a first step. If somebody is
getting a lot of pings maybe look at it more closely, and if a ping is
ignored then definitely react. Ask maintainers to include in their
ack a brief rationale - it need not be extensive/etc, or even
carefully scrutinized, but it could give some perspective. "Yes, I'm
aware that upstream has v25 and we're on v20, but API was broken in
v21 without SONAME change and most of the deps in the repo want v20 as
everybody thinks upstream is crazy." As long as we aren't pinging the
same packages often that shouldn't be a big deal and will also
simplify review.
--
Rich
next prev parent reply other threads:[~2019-03-23 19:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 7:32 [gentoo-project] How to improve detection of unmaintained packages? Michał Górny
2019-03-23 8:04 ` Joonas Niilola
2019-03-23 8:48 ` Toralf Förster
2019-03-23 8:51 ` Michał Górny
2019-03-23 14:17 ` Alec Warner
2019-03-23 17:05 ` Raymond Jennings
2019-03-23 17:38 ` Michał Górny
2019-03-23 17:53 ` Raymond Jennings
2019-03-23 18:25 ` Rich Freeman
2019-03-23 19:22 ` Alec Warner
2019-03-23 19:36 ` Rich Freeman [this message]
2019-03-23 20:14 ` Raymond Jennings
2019-03-23 20:32 ` Toralf Förster
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='CAGfcS_n+SRGiDvDdObYfGOAQDmUhc=vhXGD2uOVDRKbOu0tj7Q@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-project@lists.gentoo.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