Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-project
Navigation:
Lists: gentoo-project: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-project@g.o, gentoo-dev@g.o
From: Markus Ullmann <jokey@g.o>
Subject: maintainer-wanted bugcount
Date: Mon, 26 Nov 2007 10:46:12 +0100
Hi fellows,

when taking a look at the open bug count for bugs assigned to
maintainer-wanted (2450 at the time of writing), it seems pretty obvious
that we really can't handle all of them, at least not without growing at
least two dozen devs to maintain it properly.

As I highly doubt this will happen within a week, we have to make a
decision how to proceed with this stuff. So what options do we have?
These come to mind:

a) WONTFIX them within 4 or 8 weeks without picking them up
b) reassign them to herds (some herds are on CC) and have them
   respond withing 4-8 weeks and give a yey or boo.
c) let interested users move it to sunrise (some of them are there)
   so that the ebuilds are at least at our QA level we maintain for
   gentoo-x86 and are there to be picked up by devs if they're
   interested

If you have more options or comments, I'd like to hear about them, as we
definitely have to do something there.
F'up is set to gentoo-project as this is more a political thing.

Greetz
-Jokey


Attachment:
signature.asc (OpenPGP digital signature)
Replies:
Re: [gentoo-dev] maintainer-wanted bugcount
-- Donnie Berkholz
Navigation:
Lists: gentoo-project: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: CoC enforcement proposal
Next by thread:
Re: [gentoo-dev] maintainer-wanted bugcount
Previous by date:
Re: CoC enforcement proposal
Next by date:
Re: [gentoo-dev] maintainer-wanted bugcount


Updated Jun 17, 2009

Summary: Archive of the gentoo-project mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.