1 |
Alan McKinnon wrote: |
2 |
> Masking already accomplishes everything you propose, which is to |
3 |
> communicate "there is something wrong with this package and it is in |
4 |
> danger of leaving the tree. To get it out of this state, you need to |
5 |
> take action". |
6 |
|
7 |
I disagree strongly that this is what masking communicates, |
8 |
specifically the words "is in danger of leaving." |
9 |
|
10 |
Masking is the result of a developer decision and is something users |
11 |
are unable to influence, because the decision has already been made. |
12 |
|
13 |
When the decision has been made the package isn't in danger of |
14 |
leaving the tree anymore, it has been decided that the package *will* |
15 |
leave the tree. I consider the difference to be significant. |
16 |
|
17 |
|
18 |
The way I see it, every ebuild is in danger of leaving the tree. |
19 |
|
20 |
Masking is the next step, and means that a developer has decided that |
21 |
now (soon) is the time for that package to go. |
22 |
|
23 |
As Rich mentioned, sometimes this happens too quickly or on wrong |
24 |
grounds. Most of the time not, but the sometimes is still a problem, |
25 |
and in general I think it would be cool to make bugs more visible. |
26 |
|
27 |
I think there are other Gentoo users like myself, who are able to fix |
28 |
broken things that they care about. We don't use bugzilla unless we |
29 |
are reporting bugs however, because since fixes don't go into portage |
30 |
anyway there is little motivation. |
31 |
|
32 |
I fix what I need for myself and push fixes into my overlay, and |
33 |
usually I document both bugs and their fixes in bugzilla. The common |
34 |
case, in my experience, is that *nothing* further happens. |
35 |
|
36 |
Bugzilla is very much write-only for us users, but at the same time |
37 |
it has valuable information for upstream, and I think the bug metric |
38 |
would be a good way to push knowledge in bugzilla onto users, so that |
39 |
we can engage upstream early and make a difference for Gentoo without |
40 |
first needing to play through the recruitment game. |
41 |
|
42 |
|
43 |
//Peter |