| 1 |
On Wed, Aug 04, 2010 at 08:47:36PM +0300, Petteri Räty wrote: |
| 2 |
> On 08/04/2010 08:34 PM, Markos Chandras wrote: |
| 3 |
> > On Wed, Aug 04, 2010 at 07:12:18PM +0300, Petteri Räty wrote: |
| 4 |
> >> On 08/04/2010 02:50 PM, Markos Chandras wrote: |
| 5 |
> >> |
| 6 |
> >>> |
| 7 |
> >>> @Council: Yet another example that we need to track the status of every |
| 8 |
> >>> single project in order to have a clear picture of which projects are |
| 9 |
> >>> active and which are dead |
| 10 |
> >>> |
| 11 |
> >> |
| 12 |
> >> Pruning projects that don't actively elect a lead would be a good start |
| 13 |
> >> and that doesn't require anything from the council to be implemented. |
| 14 |
> >> |
| 15 |
> >> Regards, |
| 16 |
> >> Petteri |
| 17 |
> >> |
| 18 |
> > Don't you think we need a team for that? Who is eligible to filter the project |
| 19 |
> > list and ask status updates from them? |
| 20 |
> > |
| 21 |
> |
| 22 |
> I think undertakers can take care of any possible cleanup commits as |
| 23 |
> they already touch project pages for developer retirements. |
| 24 |
Is there enough manpower for that ? |
| 25 |
> If you want |
| 26 |
> to join for that purpose just be in contact with them and I think they |
| 27 |
> will accept my proposal. |
| 28 |
I wish I could but I am involved in way too many projects. Maybe on September. |
| 29 |
> As for just status queries I think anyone could |
| 30 |
> query the status from projects and nothing special is required. Of |
| 31 |
> course we should coordinate so that many simultaneous queries are not done. |
| 32 |
> |
| 33 |
> Regards, |
| 34 |
> Petteri |
| 35 |
> |
| 36 |
The inactivity of many herds most of the time blocks the work of some other |
| 37 |
herds. Isn't council's responsibility to step up and resolve these |
| 38 |
interproject issues? It shouldn't be that difficult to ask for monthly project |
| 39 |
status updates ( A simple "Yes, we are alive but slow kthxbye" would be |
| 40 |
sufficient, just to know that somebody is actually listening to that e-mail |
| 41 |
alias after all ), discuss this on Council's monthly meetings ( Shouldn't it take |
| 42 |
more than 20' if you already have the status updates on your Inbox ) and decide whether |
| 43 |
you should prune these herds or not. IMHO undertakers cannot handle the load |
| 44 |
atm but council can. |
| 45 |
|
| 46 |
Furthermore this inactivity ( as I said before ) doesn't look that good at all |
| 47 |
to our user community . Moreover it seems like dead herds don't even |
| 48 |
bother to ask for help or "hire" more proxy maintainers to co-maintainer some |
| 49 |
of their ebuilds. They just stay quiet on their corner and do nothing. Since |
| 50 |
Council is supposed to be the leading entity of Gentoo I was wondering how |
| 51 |
come this issue never popped up on any of your meetings. Do you really don't |
| 52 |
see a problem here or I am just that weird and everything is running smoothly? |
| 53 |
|
| 54 |
|
| 55 |
-- |
| 56 |
Markos Chandras (hwoarang) |
| 57 |
Gentoo Linux Developer |
| 58 |
Web: http://hwoarang.silverarrow.org |
| 59 |
Key ID: 441AC410 |
| 60 |
Key FP: AAD0 8591 E3CD 445D 6411 3477 F7F7 1E8E 441A C410 |
Archives