1 |
Santiago M. Mola wrote: |
2 |
> A lot of users don't feel comfortable using Bugzilla and often are |
3 |
> lost with our procedures for keyword (both ~ and stable) requests. I |
4 |
> think we could use an easy web interface for requesting specific |
5 |
> keywords for packages in a point-and-click fashion. |
6 |
|
7 |
Speaking about Bugzilla in general, I think ours could really use a facelift. |
8 |
When you look at what some other projects have done to make their bug reporting |
9 |
and tracking interface more user-friendly, it's obvious we have a lot of room |
10 |
for improvement. I remember back when I first started using Gentoo seeing a |
11 |
mock-up some dev had done for a bugzilla redesign that was much simpler and |
12 |
visually appealing, but I can't remember who and I suppose they've probably |
13 |
retired since. I've always thought it was a shame it never saw implementation. |
14 |
Anyways, I think this could make a good project for someone in our community |
15 |
who would like to participate but perhaps is more artistic than technical. |
16 |
Previous web design work and a good understanding of user interface design would |
17 |
be required of course. I suppose we should probably ask infra if this is |
18 |
possible first too. ;) |
19 |
|
20 |
On keywording/stabilizing, Bugzilla has a flags feature that might be used to |
21 |
track what has been tested where. For example: |
22 |
|
23 |
https://bugzilla.mozilla.org/show_bug.cgi?id=12345 |
24 |
|
25 |
Flags have three states: +, -, and ?. + and - are obvious, and ? is a request. |
26 |
So imagine having a "x86 tested" flag that the maintainer sets to "?" to |
27 |
request stabilization of their package. An email is sent to the arch alias |
28 |
notifying them of the request. The arch tester tests it out and sets the flag |
29 |
to + or - depending on their results. The arch dev stabilizes the package as |
30 |
normal. |
31 |
|
32 |
If we added a "Keyword/Stable Request" component to the "Gentoo Linux" product |
33 |
we could also have it dependent on that, so only bugs in that component would |
34 |
display the flags. We can also make it so only people with editbugs privileges |
35 |
and request or set flags. |
36 |
|
37 |
http://www.bugzilla.org/docs/2.22/html/flags-overview.html |
38 |
|
39 |
Again, this would require infra to be on board. |
40 |
|
41 |
|
42 |
-- |
43 |
fonts, by design, by neglect |
44 |
gcc-porting, for a fact or just for effect |
45 |
wxwindows @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |