public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stuart Herbert" <stuart@myrddraal.demon.co.uk>
To: "'Paul de Vrieze'" <pauldv@gentoo.org>, <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] Gentoo part II.
Date: Tue, 15 Jul 2003 12:39:54 +0100	[thread overview]
Message-ID: <03d901c34ac5$d249a3c0$c200a8c0@Churchill> (raw)
In-Reply-To: <200307151319.13920.pauldv@gentoo.org>

> I hope you realise that your desires are conflicting. more 
> ebuilds leads to 
> more unmaintained ebuilds. More QA needs more time.

Rubbish.  Totally utter rubbish.

The right levels of QA *save* time, because things are done
as-right-as-they-can-be first time.  Instead of time going into bug fixing
and constantly re-doing what has been done, the time instead goes into
moving forward, and doing new things.  *Too much* QA just bogs the whole
thing down, and makes it impossible to get anything done in a timely
fashion.  The two are very different.

I can think of one way to make dealing with unmaintained ebuilds easy
enough.  First of all, put in place a mechanism to remove the guesswork
about whether a particular package is maintained or not.  Then, create a
pool of developers who will handle new ebuilds for these packages.  Finally,
make a site where people can come and tell you when an ebuild is out of date
(or just use Bugzilla).  That way, packages that no-one particularly wants
to maintain are driven by 'customer demand' (for lack of a better phrase).
Final step is to setup some 'tinderbox' machines, where the unmaintained
ebuilds are automatically built.  When they finally break, a bug could be
automatically raised on Bugzilla for someone in the pool to look at it.

There's also another way.  Encourage more opensource projects to maintain
their own ebuilds.  Many of them maintain SPEC files for building RedHat
RPMs.  So why not try and distribute the work more widely too?

What are *your* proposals for addressing this?  I'd like to hear them.

> We are trying to address these problems in a way that is 
> satisfactory for everyone.

Are you speaking for yourself, or for TheManagement(tm)?

> Be assured that these issues are being addressed. This 
> requires time though, as restructuring is necessary for it to happen.

You talk like we should run along and play, and not bother BigPeople(tm)
like yourself.  You'll have to excuse me if I don't like that ;-)  It's
exactly this sort of *presentation* (I use the work presentation because
you've included nothing of substance in your reply!) that makes people call
for more openness in the community.  Interesting.

Best regards,
Stu
--



--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-07-15 11:40 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15  1:46 [gentoo-dev] Gentoo part II John Davis
2003-07-15  3:02 ` splite
2003-07-15  3:08   ` John Davis
2003-07-15  4:15     ` splite
2003-07-15  4:55       ` Kumba
2003-07-15  5:29         ` splite
2003-07-15  9:06           ` Paul de Vrieze
2003-07-15 10:05             ` Stroller
2003-07-15 10:37             ` splite
2003-07-15 10:50               ` Daniel Jaeggi
2003-07-15 18:04                 ` Jon Portnoy
2003-07-15 18:17                   ` John Davis
2003-07-15 18:28                     ` Jon Portnoy
2003-07-15 18:37                       ` Todd Berman
2003-07-15 19:13                         ` John Davis
2003-07-15 19:12                       ` John Davis
2003-07-15 11:40               ` Paul de Vrieze
2003-07-15 15:13                 ` oford
2003-07-15 17:32                   ` John Davis
2003-07-15 18:12                 ` Jon Portnoy
2003-07-15 13:20       ` cal
2003-03-17 13:42         ` Patrick Lauer
2003-07-15 13:47         ` John Davis
2003-07-15  3:40   ` Brad Cowan
2003-07-15  4:36     ` Ralph F. De Witt
2003-07-15  5:01       ` Brad Cowan
2003-07-15  6:31         ` splite
2003-07-15  4:50     ` splite
2003-07-15  4:38   ` Stewart Honsberger
2003-07-15 10:04     ` Paul de Vrieze
2003-07-15  5:53 ` William McArthur
2003-07-15  6:16 ` Brandon Low
2003-07-15  7:21   ` Ralph F. De Witt
2003-07-15 10:14     ` Paul de Vrieze
2003-07-15 10:31       ` Stuart Herbert
2003-07-15 14:03       ` Grant Goodyear
2003-07-15  8:56   ` Brad Laue
2003-07-15  7:01 ` [gentoo-dev] " Martin Gramatke
2003-07-15 10:28   ` Paul de Vrieze
2003-07-15 10:19 ` [gentoo-dev] " Stuart Herbert
2003-07-15 11:19   ` Paul de Vrieze
2003-07-15 11:39     ` Stuart Herbert [this message]
2003-07-15 12:01       ` Paul de Vrieze
2003-07-15 12:23       ` Spider
2003-07-15 18:08       ` Jon Portnoy
2003-07-15 20:27         ` Paul de Vrieze
2003-07-15 11:51 ` Spider
2003-07-16  1:44 ` Brett I. Holcomb
2003-07-16  4:25   ` Owen Gunden

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='03d901c34ac5$d249a3c0$c200a8c0@Churchill' \
    --to=stuart@myrddraal.demon.co.uk \
    --cc=gentoo-dev@gentoo.org \
    --cc=pauldv@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