public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Pagano" <mpagano@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] seeds, GLEPs, and projects
Date: Thu, 21 Sep 2006 17:01:02 -0400	[thread overview]
Message-ID: <eadeaeea0609211401y1d8ea831q417aefaffe733c72@mail.gmail.com> (raw)
In-Reply-To: <4512FACC.3080306@gentoo.org>

On 9/21/06, Simon Stelling <blubb@gentoo.org> wrote:
> Ciaran McCreesh wrote:
> > Huge amounts of time, effort and users. How much arch team time was
> > spent fixing genkernel? How much time was spent fixing the OS X mess?
> > How many users did we lose as a result of all the QA screwups?
>
> Eh, I wanted answers, not more questions :P
>
> > As much as I hate relying upon slashdot for anything reasonable at all,
> > an awful lot of people in that thread were suggesting that more time be
> > spent on QA and fixing existing bugs and much less on fancy new
> > things...
>
> These users are ignoring the fact that time is not the only and most
> important factor. Motivation is far more important IMO, and it's pretty
> hard to get the motivation together to test 60 packages instead of
> tinkering around with a new idea. At least for me it often is.
>
> --
> Kind Regards,
>
> Simon Stelling
> Gentoo/AMD64 developer
> --
> gentoo-dev@gentoo.org mailing list
>
>

Maybe a recruiting drive to help with the maintenance.  A typical
business brings on new blood and assigns them just that role to free
up more senior developers for more complicated projects.

New developers should definitely meet a standard, but the possibility
of bringing developers with energy and potential to assist in
maintenance might be worth a consideration.
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-09-21 21:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21 17:55 [gentoo-dev] seeds, GLEPs, and projects Grant Goodyear
2006-09-21 18:28 ` Simon Stelling
2006-09-21 20:03   ` Joshua Jackson
2006-09-21 20:34   ` Ciaran McCreesh
2006-09-21 20:49     ` Simon Stelling
2006-09-21 21:01       ` Mike Pagano [this message]
2006-09-21 21:43         ` [gentoo-dev] " Peter
2006-09-22  9:25           ` [gentoo-dev] Delay in approval of new developers Andrew Ross
2006-09-22 10:47             ` [gentoo-dev] " Peter
2006-09-22 11:15               ` Jochen Maes
2006-09-22 11:35                 ` Peter
2006-09-22 12:14                   ` Jochen Maes
2006-09-22 12:29                     ` Peter
2006-09-22 12:44                       ` Simon Stelling
2006-09-22 12:55                       ` Seemant Kulleen
2006-09-22 13:26                         ` Peter
2006-09-22 13:42                           ` Seemant Kulleen
2006-09-22 14:13                           ` Chris Gianelloni
2006-09-22 14:47                             ` Peter
2006-09-22 15:08                               ` Andrew Gaffney
2006-09-22 18:37                           ` Alec Warner
2006-09-22 18:54                             ` Chris Gianelloni
2006-09-22 13:56                         ` Josh Saddler
2006-09-22 13:39                       ` Grant Goodyear
2006-09-22 14:06           ` [gentoo-dev] Re: seeds, GLEPs, and projects Mike Kelly
2006-09-22 14:14             ` Peter
2006-09-25  2:25           ` Christel Dahlskjaer
2006-09-21 21:24 ` [gentoo-dev] " Lance Albertson

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=eadeaeea0609211401y1d8ea831q417aefaffe733c72@mail.gmail.com \
    --to=mpagano@gmail.com \
    --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