public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: Markus Ullmann <jokey@gentoo.org>
Cc: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Retirement of slacking peeps
Date: Wed, 16 Jan 2008 00:15:44 -0800	[thread overview]
Message-ID: <20080116081544.GA20346@supernova> (raw)
In-Reply-To: <478C95D0.6000502@gentoo.org>

On 12:15 Tue 15 Jan     , Markus Ullmann wrote:
> Hi guys,
>
> 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.

Thanks,
Donnie
-- 
gentoo-council@lists.gentoo.org mailing list



  parent reply	other threads:[~2008-01-16  8:15 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 [this message]
2008-01-16 10:57   ` Mike Doty
2008-01-16 11:06     ` Mike Doty
2008-01-16 11:43     ` Mike Frysinger
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=20080116081544.GA20346@supernova \
    --to=dberkholz@gentoo.org \
    --cc=gentoo-council@lists.gentoo.org \
    --cc=jokey@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