1 |
> If anyone has any examples of where they really are being held back and |
2 |
> where they really have given the arch teams plenty of time to do |
3 |
> something, I'd like to see them... Somehow I doubt it happens very |
4 |
> often, if at all. |
5 |
|
6 |
Why? You aren't the person I or anyone else has to make a case to. In fact, I |
7 |
never would have mailed the list about this to prevent this very type of |
8 |
potentially-out-of-control discussion from occurring, except that the e-mail from |
9 |
Mike said that discussion topics needed to be sent to the list. |
10 |
|
11 |
We currently get rid of packages that are unmaintained or are old enough that they |
12 |
pose technical problems for developers with today's tools. I see no difference in |
13 |
establishing some similar kinds criteria for arch team keywords (which I'm not even |
14 |
asking for. I'm simply asking for dialogue to determine what kinds of criteria |
15 |
would be appropriate, if any). |
16 |
|
17 |
Similarly, what would the Gentoo policy be if at some time in the future an arch |
18 |
team had no members? What if it had two members, but they were unable to keep up |
19 |
with stabilization requests and were running 6-12 months behind? "Sorry, there |
20 |
isn't anybody who can mark that stable, but we're hoping to get someone on the team |
21 |
this year" isn't a valid answer in my book. |
22 |
|
23 |
I have no idea what the process is to add an "officially" support arch to the tree, |
24 |
but certainly it's more than just one guy making a few commits. There's some |
25 |
process that has to be gone through, right? Well, there also needs to be an exit |
26 |
strategy for when lack of interest in maintenance no longer means that arch should |
27 |
be supported. But right now, all I'm asking for it when it's appropriate for an |
28 |
ebuild maintainer to not have to spend any more time waiting for the arch team to |
29 |
respond to requests. If you believe that number is 1 billion days, fine. Those of |
30 |
us who have faced the issue and disagree can also make our opinions heard to the |
31 |
council, and let them decide what should be done, again, if anything. |
32 |
|
33 |
-- |
34 |
gentoo-dev@g.o mailing list |