1 |
Diego 'Flameeyes' Pettenò wrote: |
2 |
|
3 |
> Steve Long <slong@××××××××××××××××××.uk> writes: |
4 |
> |
5 |
>>> It makes moving a bug from one package to another quite a complex task |
6 |
>>> though, as it requires two confirmation screens... and trust me that |
7 |
>>> happens often enough. |
8 |
>>> |
9 |
>> Shouldn't that just be scripted via pybugz? A GUI for that would be nice; |
10 |
>> perhaps as a pida[1] module. Frankly it appals me that y'all have so much |
11 |
>> time to write bash scriptlets and none to develop tools for your own |
12 |
>> use. |
13 |
> |
14 |
> I like Bugzilla for the very reason I can look, comment and in general |
15 |
> manage bugs with decency without needing client software beside a |
16 |
> webbrowser, and I'm rarely without a webbrowser, heck, I had one at hand |
17 |
> even while I was hospitalised (not in the ICU though, that was boring). |
18 |
> Anything that requires me an extra software is something that I'm more |
19 |
> likely _not_ going to use. |
20 |
> |
21 |
OK so you'd like a webapp version as well. |
22 |
|
23 |
[@project: |
24 |
Users regularly offer help in this kind of area, simply because they use the |
25 |
same interfaces as the devs, only for it to fall at the second or third dev |
26 |
they interact with, if they're lucky. |
27 |
] |
28 |
|
29 |
>>> Plus that would work fine if we had a bugzilla for ebuilds only, but |
30 |
>>> would you really mix categories together with Infra, Portage, Gentoo |
31 |
>>> Hosted Projects, ... ? |
32 |
>>> |
33 |
>> Who cares? |
34 |
> |
35 |
> Uh, I do, as I tend to report a lot of bugs and I don't want to have to |
36 |
> use the find command of my browser to see where the heck should I report |
37 |
> it. Don't even get me started on template bugs that I use to mass-report |
38 |
> problems. |
39 |
> |
40 |
> And probably most users would find the huge and long product |
41 |
> list to choose from most likely confusing. Users can't get it right |
42 |
> already with the short list we have, reporting bugs on Bugzilla product |
43 |
> which have nothing to do with Bugzilla... |
44 |
> |
45 |
Yeah but the point of hierarchy is so that you do one step at a time (if you |
46 |
want) via category -> package or just file the way you're used to. We're |
47 |
still only talking about a small part, in data structural terms, of |
48 |
bugzilla's schema, however much storage is allocated to the base level |
49 |
bugs. |
50 |
|
51 |
Keeping existing workflow would seem to be a requirement. |
52 |
|
53 |
|
54 |
-- |
55 |
gentoo-dev@l.g.o mailing list |