1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 06-08-2010 22:54, Markos Chandras wrote: |
5 |
> On Wed, Aug 04, 2010 at 08:47:36PM +0300, Petteri Räty wrote: |
6 |
>> On 08/04/2010 08:34 PM, Markos Chandras wrote: |
7 |
>>> On Wed, Aug 04, 2010 at 07:12:18PM +0300, Petteri Räty wrote: |
8 |
>>>> On 08/04/2010 02:50 PM, Markos Chandras wrote: |
9 |
>>>> |
10 |
>>>>> |
11 |
>>>>> @Council: Yet another example that we need to track the status of every |
12 |
>>>>> single project in order to have a clear picture of which projects are |
13 |
>>>>> active and which are dead |
14 |
>>>>> |
15 |
>>>> |
16 |
>>>> Pruning projects that don't actively elect a lead would be a good start |
17 |
>>>> and that doesn't require anything from the council to be implemented. |
18 |
>>>> |
19 |
>>>> Regards, |
20 |
>>>> Petteri |
21 |
>>>> |
22 |
>>> Don't you think we need a team for that? Who is eligible to filter the project |
23 |
>>> list and ask status updates from them? |
24 |
>>> |
25 |
>> |
26 |
>> I think undertakers can take care of any possible cleanup commits as |
27 |
>> they already touch project pages for developer retirements. |
28 |
> Is there enough manpower for that ? |
29 |
|
30 |
I've been meaning to raise this issue again in the council. |
31 |
At one point in time, around 4 years ago, a GentooStatus project was |
32 |
created under User Relations[1]. That project didn't last too long. |
33 |
Before and after that, a few developers have raised questions about this |
34 |
issue, some even started a few "What do we <herd|project> do?" threads |
35 |
now and again and the issue was brought to a few council meetings. |
36 |
Getting to the point of who is or should be responsible for this issue, |
37 |
I'd like to point everyone to a little project that seems to have been |
38 |
forgotten - "metastructure". I've thought before on joining that project |
39 |
as it seems the natural place to track the status of our projects and it |
40 |
doesn't seem to be active any longer. |
41 |
Addressing the suggestion to move this to undertakers, we could run the |
42 |
scripts to clean the project pages and update the metadata, but we |
43 |
neither have enough people nor are we "entitled" to go around poking |
44 |
herds and projects about their status. |
45 |
In the past, one objection that was constantly raised about mandatory |
46 |
period updates was that someone could just set up a cron job for it. |
47 |
|
48 |
>> If you want |
49 |
>> to join for that purpose just be in contact with them and I think they |
50 |
>> will accept my proposal. |
51 |
> I wish I could but I am involved in way too many projects. Maybe on September. |
52 |
>> As for just status queries I think anyone could |
53 |
>> query the status from projects and nothing special is required. Of |
54 |
>> course we should coordinate so that many simultaneous queries are not done. |
55 |
>> |
56 |
>> Regards, |
57 |
>> Petteri |
58 |
>> |
59 |
> The inactivity of many herds most of the time blocks the work of some other |
60 |
> herds. Isn't council's responsibility to step up and resolve these |
61 |
> interproject issues? It shouldn't be that difficult to ask for monthly project |
62 |
> status updates ( A simple "Yes, we are alive but slow kthxbye" would be |
63 |
> sufficient, just to know that somebody is actually listening to that e-mail |
64 |
> alias after all ), discuss this on Council's monthly meetings ( Shouldn't it take |
65 |
> more than 20' if you already have the status updates on your Inbox ) and decide whether |
66 |
> you should prune these herds or not. IMHO undertakers cannot handle the load |
67 |
> atm but council can. |
68 |
|
69 |
The issue to me is not council inquiring about projects / herds status, |
70 |
but the aftermath of that. Some people argue that the council should be |
71 |
able to close projects and or reform our structure. I don't like that |
72 |
for the reasons I've stated on my manifesto. |
73 |
About the montly updates check my above note about the cron jobs. |
74 |
One thing that has been raised and I think we can already do, is to have |
75 |
someone (who? - I'd suggest a reformed metastructure project) follow the |
76 |
yearly projects elections and report them on a global page about teams |
77 |
and leads. Another option would be to have the elections team publish |
78 |
all results under its project space. |
79 |
As GLEP39 already mandates on its specification[4] that all projects |
80 |
"must occur at least once every 12 months", we can have the |
81 |
metastructure project report any cases where that doesn't happen to the |
82 |
dev ml. What should happen after that is something I think the project |
83 |
needs to address. I'd prefer to have it done in the reform of GLEP39 |
84 |
process. |
85 |
|
86 |
> Furthermore this inactivity ( as I said before ) doesn't look that good at all |
87 |
> to our user community . Moreover it seems like dead herds don't even |
88 |
> bother to ask for help or "hire" more proxy maintainers to co-maintainer some |
89 |
> of their ebuilds. They just stay quiet on their corner and do nothing. Since |
90 |
> Council is supposed to be the leading entity of Gentoo I was wondering how |
91 |
> come this issue never popped up on any of your meetings. Do you really don't |
92 |
> see a problem here or I am just that weird and everything is running smoothly? |
93 |
|
94 |
This has been raised on previous council meetings, as far as I can |
95 |
remember not recently, though. |
96 |
I agree Gentoo has a problem with dead teams, but I don't think this |
97 |
problem can be fixed "by decree". Either we can get new people |
98 |
interested in a team or if possible we may have to drop it, but I |
99 |
believe a team status won't change just because council labels it as |
100 |
"moribund" or "dead". |
101 |
|
102 |
[1] - http://www.gentoo.org/proj/en/userrel/gentoostatus/ |
103 |
[2] - http://www.gentoo.org/proj/en/metastructure/ |
104 |
[3] - http://www.gentoo.org/proj/en/glep/glep-0039.html |
105 |
[4] - http://www.gentoo.org/proj/en/glep/glep-0039.html#specification |
106 |
|
107 |
- -- |
108 |
Regards, |
109 |
|
110 |
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org |
111 |
Gentoo- forums / Userrel / Devrel / KDE / Elections |
112 |
-----BEGIN PGP SIGNATURE----- |
113 |
Version: GnuPG v2.0.16 (GNU/Linux) |
114 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
115 |
|
116 |
iQIcBAEBAgAGBQJMXo/LAAoJEC8ZTXQF1qEPuY0P/0Im61ayyuqtkdjbzidUJA4c |
117 |
djcIyqsRL5xrfNZ/PgbfpGKbnputf7sRzQeCtLtD0mDT7YXZYiqoqSZonQpTT3H/ |
118 |
i0HmhVdYx3gedc3C/MTyzKaL2OLFnSeCYy2wF2WCiFCQr7MkGoMBajrM3AEALOdh |
119 |
7fLk4grrauACPIT0F65Od2inwHREvKjIKKm/n69nqPTLE7dnLIdQSAhH8C7Vp4Ye |
120 |
0mNVO8Kq4uTOXDO8cNV006MLbSyIfKSqJLklZts7z2W4uVS8ZjKE292ZIWQi4+W+ |
121 |
0USUi75SjwNT5OyDrDvhaKA7sVQy/UyL+sMntiB8d2g5KjNp7+CwGYDazCCwyeqA |
122 |
QGq3yEjfqwehUWwQxxTixNqSzABZgaREMR/yhYc/L+U32b+TWmpO6KZDq+dUa4U5 |
123 |
WlKUHIcrVTqkonXVL1m9+S6mqr1v+H0EzEGLU3l7X+wk1y7y4kEDELiWEVByuJ1W |
124 |
YBkKIUvKfdKiN0tXQEMmj5pNCNIMo+y5c4dlsnUsYGyf/DPTb+vcJ929FhCBs9JA |
125 |
4oezBvoqJIdUxACFQdZfc2nsXc+i0tfRdOuaPKkXUyuRZgY4n5MDh2YU2/dLq0yk |
126 |
BOpNt9/sCdtNPQTEfJ1KwR7BECYxaQKWz2vlnQi7sPesbfSmQE6R61Gz8NuYuCoh |
127 |
zovfiIZS4f2GI5rzt4NT |
128 |
=y6Ra |
129 |
-----END PGP SIGNATURE----- |