public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] net-proxy/squid needs your love
Date: Sat, 7 Aug 2010 01:54:19 +0300	[thread overview]
Message-ID: <20100806225419.GA3436@Mystical> (raw)
In-Reply-To: <4C59A7B8.6070208@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2750 bytes --]

On Wed, Aug 04, 2010 at 08:47:36PM +0300, Petteri Räty wrote:
> On 08/04/2010 08:34 PM, Markos Chandras wrote:
> > On Wed, Aug 04, 2010 at 07:12:18PM +0300, Petteri Räty wrote:
> >> On 08/04/2010 02:50 PM, Markos Chandras wrote:
> >>
> >>>
> >>> @Council: Yet another example that we need to track the status of every
> >>> single project in order to have a clear picture of which projects are
> >>> active and which are dead
> >>>
> >>
> >> Pruning projects that don't actively elect a lead would be a good start
> >> and that doesn't require anything from the council to be implemented.
> >>
> >> Regards,
> >> Petteri
> >>
> > Don't you think we need a team for that? Who is eligible to filter the project
> > list and ask status updates from them?
> > 
> 
> I think undertakers can take care of any possible cleanup commits as
> they already touch project pages for developer retirements. 
Is there enough manpower for that ?
> If you want
> to join for that purpose just be in contact with them and I think they
> will accept my proposal. 
I wish I could but I am involved in way too many projects. Maybe on September.
> As for just status queries I think anyone could
> query the status from projects and nothing special is required. Of
> course we should coordinate so that many simultaneous queries are not done.
> 
> Regards,
> Petteri
> 
The inactivity of many herds most of the time blocks the work of some other
herds. Isn't council's responsibility to step up and resolve these
interproject issues? It shouldn't be that difficult to ask for monthly project
status updates ( A simple "Yes, we are alive but slow kthxbye" would be
sufficient, just to know that somebody is actually listening to that e-mail
alias after all ), discuss this on Council's monthly meetings ( Shouldn't it take 
more than 20' if you already have the status updates on your Inbox ) and decide whether
you should prune these herds or not. IMHO undertakers cannot handle the load
atm but council can.

Furthermore this inactivity ( as I said before ) doesn't look that good at all
to our user community . Moreover it seems like dead herds don't even
bother to ask for help or "hire" more proxy maintainers to co-maintainer some
of their ebuilds. They just stay quiet on their corner and do nothing. Since
Council is supposed to be the leading entity of Gentoo I was wondering how
come this issue never popped up on any of your meetings. Do you really don't
see a problem here or I am just that weird and everything is running smoothly?


-- 
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
Key ID: 441AC410
Key FP: AAD0 8591 E3CD 445D 6411 3477 F7F7 1E8E 441A C410

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-08-06 22:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04 11:50 [gentoo-dev] net-proxy/squid needs your love Markos Chandras
2010-08-04 16:12 ` Petteri Räty
2010-08-04 17:34   ` Markos Chandras
2010-08-04 17:47     ` Petteri Räty
2010-08-06 22:54       ` Markos Chandras [this message]
2010-08-08 11:06         ` Jorge Manuel B. S. Vicetto
2010-08-08 11:27           ` Markos Chandras
2010-08-04 17:10 ` [gentoo-dev] " Alin Năstac
2010-08-04 17:33   ` Markos Chandras

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100806225419.GA3436@Mystical \
    --to=hwoarang@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox