From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Time based retirements
Date: Wed, 26 Dec 2012 09:46:42 -0800 [thread overview]
Message-ID: <CAAr7Pr9fbUxoZKKmnxPATBvCEVT377juS76mZbs_icoJg8Hp=A@mail.gmail.com> (raw)
In-Reply-To: <CAFWqQMQ+W=h_0rZ2oABgk=sYGArCYxxa7=4uzbAtdYhSa+veBw@mail.gmail.com>
On Thu, Dec 20, 2012 at 7:21 PM, Doug Goldstein <cardoe@gentoo.org> wrote:
> I'm curious who had the brain dead idea to retire Gentoo developers
> that are still interested in the distro, that maintain low activity
> packages for herds that are stretched way too thin, and are still
> contributing to the distro in many ways other than direct CVS commits
> (e.g. overlays, user support, providing hardware to other devs, etc).
>
> I could MAYBE understand it if they're consuming some valuable
> resource that we need to free up by retiring them. But instead they
> get a nasty-gram about their impending retirement and decide if that's
> how they are to be treated that they can be retired. When they finally
> want to contribute again they have the lovely uphill of our dreadfully
> painful recruitment process.
>
> I'm really just trying to understand the sense in this.
Often people stop maintaining packages. We use heuristics to detect
these people. These are based on commits and bug activity, along with
a whitelist for non-ebuild developers (forum moderators, irc ops, pr
people, and so forth.) They are just heuristics; they are obviously
not perfect. I'd be happy to just add steev to the whitelist for 12
months and then see where we are then (so he stops showing in the
report).
> --
> Doug Goldstein
>
prev parent reply other threads:[~2012-12-26 17:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 3:21 [gentoo-dev] Time based retirements Doug Goldstein
2012-12-21 3:26 ` Peter Stuge
2012-12-21 3:33 ` Rich Freeman
2012-12-21 4:23 ` Peter Stuge
2012-12-21 4:31 ` Peter Stuge
2012-12-21 6:09 ` [gentoo-dev] " Duncan
2012-12-21 10:38 ` Markos Chandras
2012-12-21 16:16 ` Peter Stuge
2012-12-21 16:57 ` Diego Elio Pettenò
2012-12-22 7:14 ` Alan McKinnon
2012-12-21 3:44 ` [gentoo-dev] " Matt Turner
2012-12-21 5:30 ` "Paweł Hajdan, Jr."
2012-12-21 8:25 ` Pacho Ramos
2012-12-21 8:33 ` Dirkjan Ochtman
2012-12-21 8:49 ` Brian Dolbec
2012-12-21 10:46 ` Markos Chandras
2012-12-21 15:22 ` Brian Dolbec
2012-12-21 22:50 ` Peter Stuge
2012-12-22 1:05 ` Markos Chandras
2012-12-23 2:06 ` Doug Goldstein
2012-12-23 9:39 ` Markos Chandras
2012-12-23 11:57 ` Rich Freeman
2012-12-21 8:18 ` Pacho Ramos
2012-12-21 8:19 ` Pacho Ramos
2012-12-21 9:21 ` Markos Chandras
2012-12-21 12:06 ` Ciaran McCreesh
2012-12-21 12:32 ` Arun Raghavan
2012-12-21 12:36 ` Arun Raghavan
2012-12-21 12:57 ` Rich Freeman
2013-01-07 15:07 ` Marijn
2012-12-26 17:46 ` Alec Warner [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='CAAr7Pr9fbUxoZKKmnxPATBvCEVT377juS76mZbs_icoJg8Hp=A@mail.gmail.com' \
--to=antarus@gentoo.org \
--cc=gentoo-dev@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