1 |
On Tuesday 17 May 2005 10:13, Brian Harring wrote: |
2 |
> On Tue, May 17, 2005 at 09:58:43AM +0200, Thierry Carrez wrote: |
3 |
> > Stefan Schweizer wrote: |
4 |
> > > Many bugs in bugzilla have ebuilds contributed, the work is done, |
5 |
> > > there is just no developer to add them to the tree and review them. |
6 |
> > > Bugvoting would allow other developers to see where they can help. For |
7 |
> > > example I am using kde but dont read all kde bugs, so if I would know |
8 |
> > > there is a kde bug with many votes I would maybe look at it. |
9 |
> > |
10 |
> > I have mixed feelings about this. |
11 |
> > |
12 |
> > Voting would be useful to judge which package gathers sufficient |
13 |
> > popularity to be added to Portage for example. Currently only packages a |
14 |
> > developer cares for are added, voting would help to get user opinion. |
15 |
> > |
16 |
> > On the other hand, on base system bugs for example voting would be more |
17 |
> > a pressure tool that might not help much... |
18 |
> > |
19 |
> > We could enable voting on a "New Ebuilds" section and see how it goes ? |
20 |
> |
21 |
> Seems like a good approach in my opinion. Most of the nays have |
22 |
> basically come down to "I don't want people voting on stuff I'm |
23 |
> working on, I know what needs to be done, don't need extra input to |
24 |
> discern it". |
25 |
> Ebuild submissions fall squarely outside of that arguement, and would |
26 |
> be a good test run of it. |
27 |
> |
28 |
> Personally, I'd be interested in it for actual portage bugs; that |
29 |
> said, I'm not totally sure if I'd want it enabled _now_ since there |
30 |
> are internal changes needed rather then more feature bloat, so voting |
31 |
> would be ignored till internal bits are done. |
32 |
|
33 |
So who can make the decision here? |
34 |
|
35 |
> |
36 |
> My 2 cents... |
37 |
> ~harring |
38 |
mfg, heinrich :-) |
39 |
-- |
40 |
gentoo-dev@g.o mailing list |