1 |
On Thu, 3 Jun 2010 22:35:04 +0200 |
2 |
Ben de Groot <yngwin@g.o> wrote: |
3 |
|
4 |
> Also, there are herds that have several members, but none of them is |
5 |
> really active (games, most of the desktop-* herds, etc.). This also |
6 |
> leads to users being discouraged because the bugs they file are left |
7 |
> ignored. |
8 |
> |
9 |
> This needs a structural solution. I think we need a team to |
10 |
> systematically look at open bugs and to notify the community of such |
11 |
> problematic herds. I imagine this would be a QA subproject. |
12 |
|
13 |
That would basically be a task other than bug-wranglers, but jakub used |
14 |
to do all this and I do it sometimes, among a few others who either |
15 |
just scratch an itch or take a general interest. Maybe the |
16 |
bug-wranglers project can be extended since it at least has some active |
17 |
people (not just developers), but as it now stands there are again 150 |
18 |
unassigned bugs after only a week (up from ~40 since the last |
19 |
reassignment run I believe). |
20 |
|
21 |
"Calling in" QA as such usually isn't really beneficial. |
22 |
|
23 |
> Then we also need some structure to redirect some dev love to these |
24 |
> problematic areas. We need to advertise these needs more, to get |
25 |
> trusted users to proxy-maintain. We need to streamline the recruitment |
26 |
> process to make it easier for people who want to volunteer to become |
27 |
> devs. And I could go on for a while. There are a lot of areas where |
28 |
> Gentoo has a lot of room for improvement, and they all interlock. |
29 |
|
30 |
All these problems seem to come down to the fact that we're |
31 |
understaffed in most departments. |
32 |
|
33 |
Setting up yet another project isn't going to help much. Just looking |
34 |
at open bugs (bugzilla can help you figure out which bugs might need |
35 |
someone's particular attention). What might help right now is look at |
36 |
the herds.xml data and combining that with activity rates of the |
37 |
developers in all herds. Herds with few developers and lots of open |
38 |
bugs is something you could calculate and filter down into a monthly or |
39 |
weekly report you send to a mailing list (probably dev-announce?). |
40 |
|
41 |
> I believe we need to formulate a vision of what we want Gentoo to be, |
42 |
> and then develop strategies of how to get there. Having a team that |
43 |
> systematically looks at the state of herds as well as open bugs is |
44 |
> --in my opinion-- a crucial first step to adress some of the |
45 |
> structural problems that have plagued Gentoo for years. |
46 |
|
47 |
Do you mean we should redefine what Gentoo is about, to satisfy the lack |
48 |
of active developers? Bring down the number of packages? Or address the |
49 |
staff shortage? That last one is rather old, as recruiters have been |
50 |
clamouring for help for years now. |
51 |
|
52 |
|
53 |
Regards, |
54 |
jer |