List Archive: gentoo-project
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
-----BEGIN PGP SIGNED MESSAGE-----
On 14/08/2011 12:35 μμ, Rich Freeman wrote:
> On Sun, Aug 14, 2011 at 7:06 AM, Markos Chandras
> <firstname.lastname@example.org> wrote:
>> Some time ago, few people proposed to have Council appointed
>> leaders for QA and DevRel. I like the idea because this way the
>> Council can ensure that the team is active or either force some
>> activity in case the current leader slacks big time.
Well, to be honest, I have no clear understanding of what you guys think
about this problem. From what I gathered, it seems to me that we need to
establish a process to identify dead/slacking projects and then have the
appropriate mechanism within the council to deal with it.
Having all the project sending a "ping" e-mail to council is not a
solution. Having a bunch of people monitoring all the projects is not
What I propose, is to compile a list with projects that are known to be
dead, and give them a final warning or verify their "dead" status. After
that, their broken package shall be removed, and the rest of them can
remain as maintainer-needed@. 2-3 developers can take care of the
removals. It is not a big deal.
Personally, I want to shrink portage. There is no way for 250 listed
developers ( I would be glad if 100 of us were really active ) to
maintain thousands of ebuilds. I have already said that many many times
and I will say it again. We need to stop pretending that everything is
fine. We need to support only the packages that we can *really* support
and lets hope that more people will join in when they see their packages
I think this is quite honest not just to our selves but to our users as
well. If we keep stalling, then heavy committers will probably get
demotivated ( by trying to keep everything working ) and Gentoo will
slowly die or portage will become unmanageable.
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
-----END PGP SIGNATURE-----