public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-council@lists.gentoo.org
Cc: Markus Ullmann <jokey@gentoo.org>
Subject: Re: [gentoo-council] Retirement of slacking peeps
Date: Tue, 15 Jan 2008 06:36:37 -0500	[thread overview]
Message-ID: <200801150636.37961.vapier@gentoo.org> (raw)
In-Reply-To: <478C95D0.6000502@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2107 bytes --]

On Tuesday 15 January 2008, 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).

the metric for retirement lies with devrel and whatever sub projects they've 
partitioned/created for these topics.  the larger developer base is free to 
make their opinions known to devrel on the various matters and if they feel 
things are not moving in the right direction, we can review the matter.  but 
i would say this is hardly close to the point for us to review

> Reason that brought it to attention is the retirement bug for the
> current QA lead spb. (https://bugs.gentoo.org/show_bug.cgi?id=64840)
>
> To resolve the current situation there I gave the advice to just hold
> project lead votings that every project has to do every 12 months.

i think the rules are in place to help keep things moving smoothly.  in other 
words, they are guidelines which are not absolute, especially in an open 
source project such as ours.

in this particular case, i would consider these facts to be self evident (and 
painfully so):
 - the current QA lead has effectively done nothing for the entire run of 
holding the position
 - the current QA lead is pretty inactive in many (most?) Gentoo things
 - the previous QA lead was very active in constantly improving Gentoo life
 - the previous QA lead would like to resume improving Gentoo life

taking these facts into consideration, the logical move would be for the 
current QA lead to step down and allow the previous QA lead to step up.  Mark 
has more than proved his constant drive for quality.  Stephen on the other 
hand has done nothing of the sort.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2008-01-15 11:36 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 [this message]
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
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=200801150636.37961.vapier@gentoo.org \
    --to=vapier@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