From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: Notify people about empty herds (Was: Re: [gentoo-dev] FTR: media-optical@g.o has no developers)
Date: Thu, 3 Jun 2010 16:32:59 +0300 [thread overview]
Message-ID: <AANLkTikhSADjKwX9eIXbj0cTmgmKFWczQJ4Iz-kTHu1u@mail.gmail.com> (raw)
In-Reply-To: <1275570192.7629.24.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]
And maybe it would be a wise move to merge/remove some herds because ,as I
see, the number of herds is equal ( or even higher ) to the number of
developers.
2010/6/3 Pacho Ramos <pacho@gentoo.org>
> El jue, 03-06-2010 a las 13:36 +0300, Samuli Suominen escribió:
> > For the record, media-optical herd is currently without any devs and
> > also the mail alias in d.g.o is empty so nobody is really reading the
> > bugmail.
> >
> > In case you want to join it...
> >
> > - Samuli
>
> Would be possible to modify script that generates
> http://www.gentoo.org/proj/en/metastructure/herds/herds.xml to list
> empty herds on a different section at the top of the webpage for
> detecting herds without people easier?
>
> Even better would be to also provide information about "devway"
> developers, indicating something like, for example:
> 41. gnome
> - Description
> GNOME Desktop and related packages
> - Herd maintainers' email address
> gnome@gentoo.org
> - Maintainers
> ...
> pacho@gentoo.org (Pacho Ramos) (Devway)
>
> But I am not sure if it would be possible :-/
>
> Also, maybe we should consider change the assignment for bugs assigned
> to empty herds, assigning them to maintainers-needed and CCing affected
> herd, that way, once somebody revives the herd, he could simply revert
> the assign to the old way and, until then, people reviewing
> maintainers-needed bugs would also notice that bug reports.
>
> Thanks a lot
>
[-- Attachment #2: Type: text/html, Size: 1971 bytes --]
next prev parent reply other threads:[~2010-06-03 13:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 10:36 [gentoo-dev] FTR: media-optical@g.o has no developers Samuli Suominen
2010-06-03 13:03 ` Notify people about empty herds (Was: Re: [gentoo-dev] FTR: media-optical@g.o has no developers) Pacho Ramos
2010-06-03 13:32 ` Markos Chandras [this message]
2010-06-03 14:28 ` "Paweł Hajdan, Jr."
2010-06-03 14:44 ` Markos Chandras
2010-06-03 15:38 ` Mike Pagano
2010-06-03 16:32 ` Jorge Manuel B. S. Vicetto
2010-06-03 17:34 ` Markos Chandras
2010-06-03 18:54 ` Jeroen Roovers
2010-06-03 20:35 ` Ben de Groot
2010-06-03 22:55 ` Jeroen Roovers
2010-06-04 1:15 ` Ben de Groot
2010-06-03 20:22 ` Eray Aslan
2010-06-03 14:12 ` [gentoo-dev] FTR: media-optical@g.o has no developers Steve Dibb
2010-06-03 14:19 ` Steve Dibb
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=AANLkTikhSADjKwX9eIXbj0cTmgmKFWczQJ4Iz-kTHu1u@mail.gmail.com \
--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