From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2012-04-03
Date: Tue, 20 Mar 2012 10:41:38 +0100 [thread overview]
Message-ID: <1332236498.9921.6.camel@belkin4> (raw)
In-Reply-To: <20328.10318.193096.854402@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 1950 bytes --]
El mar, 20-03-2012 a las 07:48 +0100, Ulrich Mueller escribió:
> In two weeks from now, the council will meet again. This is the time
> to raise and prepare items that the council should put on the agenda
> to discuss or vote on.
>
> Please respond to this email with agenda items. Please do not
> hestitate to repeat your agenda item here with a pointer if you
> previously suggested one (since the last meeting).
>
> The agenda for the next meeting will be sent out on Tuesday 27th
> of March 2012.
>
> Please respond to the gentoo-project list, if possible.
>
> Ulrich
>
>
I would like to see this suggestion discussed if possible:
About making herds.xml addition mandatory for devs when adding to mail
alias
Currently, looks like there are developers that add them to mail aliases
for "zombie" herds (herds that are empty and unmaintained usually) but
don't want to add them to herds.xml because they prefer to not be
considered as officially being part of that hers. This causes that herds
to be not maintained very actively as we rely on that "hidden"
maintainer having enough time to take care of *all* packages included in
that herd. The situation is, then, like a "pseudo-unmaintained" herd as
bugs are still assigned to that alias and get out of radar of
maintainer-needed alias (that includes people wanting to help with that
unmaintained packages, trying to find maintainers or proxy-maintainers
for them or removing them is needed) and we depend on that dev added to
mail alias to take care of them, this is also problematic when dev
decides to drop him from alias getting herd totally unmaintained without
any notice to gentoo-dev ML.
Since there is no need to stay in the herd some prefixed time, I see no
reason to allow developers to be in mail aliases without adding them to
herds.xml, and this allows others to "easily" review herds.xml looking
for empty herds.
Thanks a lot
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-03-20 12:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 6:48 [gentoo-project] Call for agenda items - Council meeting 2012-04-03 Ulrich Mueller
2012-03-20 6:55 ` [gentoo-project] " Ulrich Mueller
2012-03-20 20:29 ` Markos Chandras
2012-03-20 20:37 ` Ciaran McCreesh
2012-03-20 21:21 ` Markos Chandras
2012-03-20 21:00 ` Ulrich Mueller
2012-03-20 21:34 ` Pacho Ramos
2012-03-21 7:38 ` Fabian Groffen
2012-03-21 8:09 ` Ulrich Mueller
2012-03-21 11:52 ` Brian Harring
2012-03-21 15:31 ` Rich Freeman
2012-03-21 16:46 ` Ulrich Mueller
2012-03-20 9:41 ` Pacho Ramos [this message]
2012-03-20 12:34 ` [gentoo-project] " Chí-Thanh Christopher Nguyễn
2012-03-20 18:35 ` Pacho Ramos
2012-03-20 15:32 ` Mike Gilbert
2012-03-20 18:37 ` Pacho Ramos
2012-03-24 5:23 ` [gentoo-project] " Ryan Hill
2012-03-24 8:04 ` Pacho Ramos
2012-03-24 10:04 ` Markos Chandras
2012-03-24 5:21 ` Ryan Hill
2012-03-20 11:23 ` [gentoo-project] " Tony "Chainsaw" Vroon
2012-03-21 18:12 ` Zac Medico
2012-03-21 19:31 ` Rich Freeman
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=1332236498.9921.6.camel@belkin4 \
--to=pacho@gentoo.org \
--cc=gentoo-project@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