public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Faraday Weller <welp@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Retiring
Date: Wed, 06 May 2009 21:41:54 +0100	[thread overview]
Message-ID: <1241642515.3120.16.camel@localhost.localdomain> (raw)
In-Reply-To: <1241635257.3999.1@NeddySeagoon>

On Wed, 2009-05-06 at 19:40 +0100, Roy Bamford wrote:
[..snip..]
> 
> [snip]
> > The only issue I have with the idea is that projects with dead 
> > members
> > and slacking leaders are unlikely to perform such a task, so you'll
> > never get any updates from them, so devs will be demotivated to work
> > on
> > $project, and thus we enter the vicious cycle again...
> > 
> > welp
> > 
> Welp,
> 
> Not so.
> 
> These projects would be delegated upwards to the council and either 
> scrapped offically, or some recruitment process started to breath new 
> life into them.
> 
> Maybe dead projects are cleaned like treecleaners ?

This actually sounds like a pretty good idea, and one that I might
actually be interested in.

Someone working within such a project would have to be in close
communication with most/all of the team leads within Gentoo. I feel that
this would be a better solution than asking for (semi-)regular updates
from the teams - having someone to have a chat with the team lead is
much less formal and more relaxed way of ensuring that things are well.
If it seems that the project is having problems staying alive, a call
for help could be put out. If there is no improvement, the project could
be referred to the Gentoo Council to see if it should be
removed/abolished, otherwise...

Opinions/ideas welpcome!

welp




  reply	other threads:[~2009-05-06 20:43 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-03 21:26 [gentoo-dev] Retiring Peter Faraday Weller
2009-05-03 22:51 ` [gentoo-dev] Retiring Duncan
2009-05-04 11:47   ` Ferris McCormick
2009-05-04 13:05     ` Duncan
2009-05-04  8:34 ` [gentoo-dev] Retiring Markos Chandras
2009-05-04 11:36   ` Peter Faraday Weller
2009-05-04 11:50   ` Ferris McCormick
2009-05-04 12:35     ` Markos Chandras
2009-05-04 17:48       ` Tiziano Müller
2009-05-04 18:24       ` Richard Freeman
2009-05-04 19:09         ` Markos Chandras
2009-05-05 13:50           ` Richard Freeman
2009-05-05 14:06             ` Markos Chandras
2009-05-05 16:18               ` Tobias Klausmann
2009-05-05 16:26                 ` Sergio D. Rodríguez Inclan
2009-05-05 16:36                   ` [gentoo-dev] Retiring Duncan
2009-05-05 16:46                   ` [gentoo-dev] Retiring Markos Chandras
2009-05-05 16:51                     ` Robert Bridge
2009-05-05 17:03                     ` Mounir Lamouri
2009-05-05 17:07                       ` Markos Chandras
2009-05-05 19:06                       ` Sergio D. Rodríguez Inclan
2009-05-05 16:26               ` Thomas Anderson
2009-05-05 16:41                 ` Markos Chandras
2009-05-05 16:52                   ` George Prowse
2009-05-05 17:05                     ` Markos Chandras
2009-05-04 15:54 ` Vlastimil Babka
2009-05-04 16:36   ` Markos Chandras
2009-05-04 17:02     ` Ciaran McCreesh
2009-05-04 17:06 ` George Prowse
2009-05-04 17:23   ` Mario Fetka
2009-05-04 19:11   ` Markos Chandras
2009-05-05 20:45   ` AllenJB
2009-05-05 22:45     ` Markos Chandras
2009-05-06 18:32       ` Peter Faraday Weller
2009-05-06 18:40         ` Roy Bamford
2009-05-06 20:41           ` Peter Faraday Weller [this message]
2009-05-06 21:28             ` [gentoo-dev] Retiring Duncan
2009-05-06 21:15           ` [gentoo-dev] Retiring Markos Chandras
  -- strict thread matches above, loose matches on Subject: below --
2015-01-29  2:34 [gentoo-dev] retiring Chris Brannon
2010-06-07 20:26 [gentoo-dev] Retiring Maurice van der Pot
2009-05-04 18:06 Mario Fetka
2008-02-04 21:18 Kevin F. Quinn
2008-02-04 23:46 ` Donnie Berkholz

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=1241642515.3120.16.camel@localhost.localdomain \
    --to=welp@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