From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-council@lists.gentoo.org
Cc: Mike Doty <kingtaco@gentoo.org>,
Donnie Berkholz <dberkholz@gentoo.org>,
Markus Ullmann <jokey@gentoo.org>
Subject: Re: [gentoo-council] Retirement of slacking peeps
Date: Wed, 16 Jan 2008 06:43:01 -0500 [thread overview]
Message-ID: <200801160643.02650.vapier@gentoo.org> (raw)
In-Reply-To: <478DE307.1010906@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1745 bytes --]
On Wednesday 16 January 2008, Mike Doty wrote:
> Donnie Berkholz wrote:
> > On 12:15 Tue 15 Jan , Markus Ullmann wrote:
> >> our retirement folks brought up a discussion about retiring people that
> >> do a small amount of commits (1-2 mostly) right before the 60 day period
> >> ends so they stay active yet are effectively slacking.
> >>
> >> I gave a starting idea to change the minimum amount to something like
> >> $count of fixed bugs per month for ebuild developers. As we have enough
> >> bugs that are trivial to fix this shouldn't be a real problem at the
> >> moment (considering we have ~6.5k bugs open excluding
> >> maintainer-wanted).
> >
> > I don't see a good reason to turn away any amount of help, and I don't
> > think we should ever forcibly retire developers because of inactivity.
> > If we let them stay developers, they might continue contributing a few
> > fixes we wouldn't otherwise get, or they may become more active again in
> > the future. Developers are valuable people, and a lot of time has gone
> > into their training and experience.
> >
> > Do I think we should reassign their packages after a while, if they need
> > love? Sure.
> >
> > Do I think we should remove them from roles besides "ebuild developer"?
> > Sure.
>
> How about calling them inactive. infra will remove cvs/svn/git access
> and when they have time to contribute to a manner that we expect that
> access can be restored.
>
> Know that infra is/has been planning to automatically disable
> cvs/svn/git access for those who haven't committed in some time period
> (2 months is the current idea)
the timeframe should follow whatever devrel is using (which i think is longer
than 2 months)
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2008-01-16 11:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 11:15 [gentoo-council] Retirement of slacking peeps Markus Ullmann
2008-01-15 11:36 ` Mike Frysinger
2008-01-15 11:41 ` Mike Frysinger
2008-01-16 8:15 ` Donnie Berkholz
2008-01-16 10:57 ` Mike Doty
2008-01-16 11:06 ` Mike Doty
2008-01-16 11:43 ` Mike Frysinger [this message]
2008-01-16 20:40 ` Ned Ludd
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=200801160643.02650.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=dberkholz@gentoo.org \
--cc=gentoo-council@lists.gentoo.org \
--cc=jokey@gentoo.org \
--cc=kingtaco@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