public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council appointed leaders for QA and DevRel
Date: Wed, 17 Aug 2011 17:26:29 +0100	[thread overview]
Message-ID: <4E4BEBB5.8090300@gentoo.org> (raw)
In-Reply-To: <CAGfcS_mpZ_pGfpB5967f3K2zh57p6DEbfUiiPHy9JFmKFfYS0A@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 14/08/2011 12:35 μμ, Rich Freeman wrote:
> On Sun, Aug 14, 2011 at 7:06 AM, Markos Chandras
> <hwoarang@gentoo.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
good either.

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
going away.

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.

- -- 
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iQIcBAEBCgAGBQJOS+u1AAoJEPqDWhW0r/LCYCcP+gMKEHUR8M/4irz7N/1U0cy3
vt4xVNXticFha1uWmbF+GtjFnWoGYGQIFJnDsb81C9om6NGyEKwqGvDG/N2ELEHl
QgHEN1bDOs+i7+0iyk7I5WP4MNVgGTSFcsChHXCA50aOlUYW7mFvplJLNTxSw5zA
xi20Cr0bUj/4b4vbHfnhGY8htxpeQ1SKRGSnpm5Dwr1eid8HN8QtrPjhk/gWNxV5
neT2SGkxljcB9L55RO0gteKdolS8aLevomJegHLAPIy3BlfaYq0mY532K1qnX4Jc
WRAbQIFXrOhnNmlRwzSzPFlf86NqHn84Jq2tqBDCL61jTsoaBHnS7RJFJQTSvNcn
sm8DRn3wK6W2HP6sDhSyeJOSRvADvBtwlK/B0uyHbkluSr+4BRr2yBr4a7ubbhbw
dOJJrmfJW154n1qUXqRvbpXPFMFfqaHmQE4gd6nL9zCIq0xTICgp0ps4lm62Kl5T
2hIyZAK7TLrcdNUcyzqhPhW7wR82+w06m4WJMH3Ip1HTVV30ojir7mP+ur0Hao3c
rcHc1IVQcqBzm59mesOJ4A1iAlTqMNEKkLWxsbRKnPD8B1pOY1GIwKk+Fj/5YF7s
m3FdeQRSY2SgVwVkVypGTgOSzmL7jC1IaHfH6fGD0RghBNWkrIn96/E2o4qcFwtn
DVbVyq1RnOGf6RolgHij
=kXGN
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2011-08-17 16:28 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-14 11:06 [gentoo-project] Council appointed leaders for QA and DevRel Markos Chandras
2011-08-14 11:19 ` Fabian Groffen
2011-08-14 11:22   ` Markos Chandras
2011-08-14 11:31     ` Fabian Groffen
2011-08-14 11:36       ` Markos Chandras
2011-08-14 11:52         ` Rich Freeman
2011-08-14 11:58           ` Fabian Groffen
2011-08-14 11:35 ` Rich Freeman
2011-08-14 11:41   ` Markos Chandras
2011-08-17 16:26   ` Markos Chandras [this message]
2011-08-17 18:16     ` Rich Freeman
2011-08-17 18:47       ` Markos Chandras
2011-08-14 12:15 ` Thomas Sachau
2011-08-14 12:24   ` Markos Chandras
2011-08-14 13:07     ` Thomas Sachau
2011-08-14 13:38       ` Markos Chandras
2011-08-14 15:35         ` Roy Bamford
2011-08-14 15:43           ` Markos Chandras
2011-08-14 16:40             ` Roy Bamford
2011-08-14 17:27             ` Roy Bamford
2011-08-18  1:41             ` Jorge Manuel B. S. Vicetto
2011-08-14 16:07         ` Thomas Sachau
2011-08-14 16:19           ` Markos Chandras
2011-08-14 16:48             ` Thomas Sachau
2011-08-14 16:56               ` Markos Chandras
2011-08-14 18:03                 ` Roy Bamford
2011-08-14 18:50                   ` Markos Chandras
2011-08-14 17:54             ` Patrick Lauer
2011-08-14 14:19 ` Roy Bamford
2011-08-14 14:35   ` Petteri Räty
2011-08-14 16:31     ` Roy Bamford
2011-08-15 19:30       ` Petteri Räty
2011-08-14 14:36   ` Markos Chandras
2011-08-14 14:39   ` Rich Freeman
2011-08-14 14:39   ` Markos Chandras
2011-08-14 16:12     ` Roy Bamford
2011-08-14 16:22       ` Markos Chandras
2011-08-15 19:29       ` Petteri Räty
2011-08-18  1:56         ` Jorge Manuel B. S. Vicetto
2011-08-18  2:18 ` Jorge Manuel B. S. Vicetto

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=4E4BEBB5.8090300@gentoo.org \
    --to=hwoarang@gentoo.org \
    --cc=gentoo-project@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