| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA512 |
| 3 |
|
| 4 |
On 14/08/2011 12:35 μμ, Rich Freeman wrote: |
| 5 |
> On Sun, Aug 14, 2011 at 7:06 AM, Markos Chandras |
| 6 |
> <hwoarang@g.o> wrote: |
| 7 |
>> Some time ago, few people proposed to have Council appointed |
| 8 |
>> leaders for QA and DevRel. I like the idea because this way the |
| 9 |
>> Council can ensure that the team is active or either force some |
| 10 |
>> activity in case the current leader slacks big time. |
| 11 |
> |
| 12 |
|
| 13 |
Well, to be honest, I have no clear understanding of what you guys think |
| 14 |
about this problem. From what I gathered, it seems to me that we need to |
| 15 |
establish a process to identify dead/slacking projects and then have the |
| 16 |
appropriate mechanism within the council to deal with it. |
| 17 |
|
| 18 |
Having all the project sending a "ping" e-mail to council is not a |
| 19 |
solution. Having a bunch of people monitoring all the projects is not |
| 20 |
good either. |
| 21 |
|
| 22 |
What I propose, is to compile a list with projects that are known to be |
| 23 |
dead, and give them a final warning or verify their "dead" status. After |
| 24 |
that, their broken package shall be removed, and the rest of them can |
| 25 |
remain as maintainer-needed@. 2-3 developers can take care of the |
| 26 |
removals. It is not a big deal. |
| 27 |
|
| 28 |
Personally, I want to shrink portage. There is no way for 250 listed |
| 29 |
developers ( I would be glad if 100 of us were really active ) to |
| 30 |
maintain thousands of ebuilds. I have already said that many many times |
| 31 |
and I will say it again. We need to stop pretending that everything is |
| 32 |
fine. We need to support only the packages that we can *really* support |
| 33 |
and lets hope that more people will join in when they see their packages |
| 34 |
going away. |
| 35 |
|
| 36 |
I think this is quite honest not just to our selves but to our users as |
| 37 |
well. If we keep stalling, then heavy committers will probably get |
| 38 |
demotivated ( by trying to keep everything working ) and Gentoo will |
| 39 |
slowly die or portage will become unmanageable. |
| 40 |
|
| 41 |
- -- |
| 42 |
Regards, |
| 43 |
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2 |
| 44 |
-----BEGIN PGP SIGNATURE----- |
| 45 |
Version: GnuPG v2.0.18 (GNU/Linux) |
| 46 |
|
| 47 |
iQIcBAEBCgAGBQJOS+u1AAoJEPqDWhW0r/LCYCcP+gMKEHUR8M/4irz7N/1U0cy3 |
| 48 |
vt4xVNXticFha1uWmbF+GtjFnWoGYGQIFJnDsb81C9om6NGyEKwqGvDG/N2ELEHl |
| 49 |
QgHEN1bDOs+i7+0iyk7I5WP4MNVgGTSFcsChHXCA50aOlUYW7mFvplJLNTxSw5zA |
| 50 |
xi20Cr0bUj/4b4vbHfnhGY8htxpeQ1SKRGSnpm5Dwr1eid8HN8QtrPjhk/gWNxV5 |
| 51 |
neT2SGkxljcB9L55RO0gteKdolS8aLevomJegHLAPIy3BlfaYq0mY532K1qnX4Jc |
| 52 |
WRAbQIFXrOhnNmlRwzSzPFlf86NqHn84Jq2tqBDCL61jTsoaBHnS7RJFJQTSvNcn |
| 53 |
sm8DRn3wK6W2HP6sDhSyeJOSRvADvBtwlK/B0uyHbkluSr+4BRr2yBr4a7ubbhbw |
| 54 |
dOJJrmfJW154n1qUXqRvbpXPFMFfqaHmQE4gd6nL9zCIq0xTICgp0ps4lm62Kl5T |
| 55 |
2hIyZAK7TLrcdNUcyzqhPhW7wR82+w06m4WJMH3Ip1HTVV30ojir7mP+ur0Hao3c |
| 56 |
rcHc1IVQcqBzm59mesOJ4A1iAlTqMNEKkLWxsbRKnPD8B1pOY1GIwKk+Fj/5YF7s |
| 57 |
m3FdeQRSY2SgVwVkVypGTgOSzmL7jC1IaHfH6fGD0RghBNWkrIn96/E2o4qcFwtn |
| 58 |
DVbVyq1RnOGf6RolgHij |
| 59 |
=kXGN |
| 60 |
-----END PGP SIGNATURE----- |
Archives