1 |
On Nov 26, 2007 4:46 AM, Markus Ullmann <jokey@g.o> wrote: |
2 |
|
3 |
> Hi fellows, |
4 |
> |
5 |
> when taking a look at the open bug count for bugs assigned to |
6 |
> maintainer-wanted (2450 at the time of writing), it seems pretty obvious |
7 |
> that we really can't handle all of them, at least not without growing at |
8 |
> least two dozen devs to maintain it properly. |
9 |
> |
10 |
> As I highly doubt this will happen within a week, we have to make a |
11 |
> decision how to proceed with this stuff. So what options do we have? |
12 |
> These come to mind: |
13 |
> |
14 |
> a) WONTFIX them within 4 or 8 weeks without picking them up |
15 |
> b) reassign them to herds (some herds are on CC) and have them |
16 |
> respond withing 4-8 weeks and give a yey or boo. |
17 |
> c) let interested users move it to sunrise (some of them are there) |
18 |
> so that the ebuilds are at least at our QA level we maintain for |
19 |
> gentoo-x86 and are there to be picked up by devs if they're |
20 |
> interested |
21 |
> |
22 |
> If you have more options or comments, I'd like to hear about them, as we |
23 |
> definitely have to do something there. |
24 |
> F'up is set to gentoo-project as this is more a political thing. |
25 |
> |
26 |
> Greetz |
27 |
> -Jokey |
28 |
> |
29 |
> |
30 |
> Hi everyone, |
31 |
|
32 |
I did the "Collective Maintenance" project this summer: |
33 |
http://code.google.com/soc/2007/gentoo/appinfo.html?csaid=2881CA66D3587EA2 |
34 |
|
35 |
My vision was to move things in to a direction where the "maintainer-wanted" |
36 |
packages would be collectively maintained without the need for a specific |
37 |
herd or maintainer. To get to this vision, I set out to create a web |
38 |
interface that would allow work to be coordinated in an organized, |
39 |
efficient, and by-demand manner. Here is where I am currently at with that |
40 |
interface: http://afalko.homelinux.net/tskdemo/ |
41 |
|
42 |
I think the current state of the interface is not going to allow for enough |
43 |
organization. My fear is that it will turn into an unnavigable |
44 |
dumping-ground when a lot of tasks/"maintainer-wanted" bugs are added to the |
45 |
list. I am one year from earning at B.S. degree in Industrial Engineering |
46 |
and my requirement this school year is to complete an IE design project. I |
47 |
was able to get a group of four together to work on redesigning the |
48 |
interface. My group members have been generating some excellent ideas so |
49 |
far. I am optimistic that the end product will allow my vision to be |
50 |
achieved. I will push to get the interface ready before the end of May 2008. |
51 |
|
52 |
So in sum, I guess you can add a fourth option to the list: wait until the |
53 |
end of May 2008 for the completion/deployment of an interface for |
54 |
collectively maintaining packages. Or even a fifth option: use the current |
55 |
interface right now and upgrade in May 2008 to a re-designed revision. |
56 |
|
57 |
Best regards, |
58 |
Andrey Falko |