1 |
TL;DR |
2 |
ia64/ppc/sparc teams are pretty much dead. They have been for a long |
3 |
time and this won't change any time soon. Gentoo should focus its |
4 |
resources on archs that are important and has the manpower to support. |
5 |
Let us please drop these 3 archs to dev profiles to ease maintenance. |
6 |
|
7 |
Dear all, |
8 |
I'd like to request Council to consider my motion to drop the |
9 |
ia64/ppc/sparc profiles to dev (or exp). These arches are pretty much |
10 |
dead, minus the automated workflows of ago. Two months ago I have |
11 |
written to these 3 archs, and only received one reply from ppc agreeing |
12 |
with my sentiment, with no response from ia64 or sparc, which in itself |
13 |
is pretty telling. |
14 |
|
15 |
Currently, architecture projects think adding their keywords is a |
16 |
right, which I strongly disagree with. I believe being able to add (and |
17 |
stable) your keywords is a privilege - namely it carries with it the |
18 |
duty to react to keywording and stabilization requests in a timely |
19 |
manner. Let's compare the state of ia64/ppc/sparc to, say alpha: |
20 |
|
21 |
https://bugs.gentoo.org/show_bug.cgi?id=605278 |
22 |
|
23 |
alpha was keyworded within 6 hours. To date ia64/ppc/sparc are still |
24 |
not keyworded (the bot had some breakages due to jer again shifting |
25 |
around all the bugs). Within 4 months these arches have not managed to |
26 |
keyword those 4 packages. This is I believe the most striking example |
27 |
of how the only work done for these archs are ago's automated stablereq |
28 |
scripts. Why do I saw that keywording+stabling your arch is a |
29 |
privilege? Maintenance of packages is hampered by archs not stabling, |
30 |
because we cannot clean up broken packages. Adding keywords is a two- |
31 |
way street - if you don't act speedily, you're breaking part of the |
32 |
maintainer-arch social contract. |
33 |
|
34 |
Please don't turn this into a massive bikeshedding contest and just |
35 |
admit that it is extremely unlikely that these archs will see more |
36 |
activity in the near future. We should focus our resources on more |
37 |
important archs (arm64 maybe?) instead of these. I know you have that |
38 |
old Mac G4 or UltraSPARC sitting in your closet that you're 2 days away |
39 |
from installing Gentoo on, but the pain for maintainers and the rest of |
40 |
the community is just too great. If someone steps up to do the work, we |
41 |
can then move archs back to a stable profile, but so long as they |
42 |
linger in their present state, let's call a spade a spade. |
43 |
|
44 |
Anyhow, I formally request the Council to vote on dropping these archs |
45 |
to unstable/exp profiles for the next Council meeting, explicitly |
46 |
overriding any arch concerns that are likely to awake now and going to |
47 |
be running around like headless chicken. |
48 |
|
49 |
David |