public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Thomas Sachau <tommy@gentoo.org>
Subject: Re: [gentoo-dev] Empty herd: sgml
Date: Mon, 22 Mar 2010 02:59:18 -0400	[thread overview]
Message-ID: <201003220259.18739.vapier@gentoo.org> (raw)
In-Reply-To: <4BA68E2F.6080002@gentoo.org>

[-- Attachment #1: Type: Text/Plain, Size: 1268 bytes --]

On Sunday 21 March 2010 17:22:55 Thomas Sachau wrote:
> Am 21.03.2010 18:06, schrieb Mike Frysinger:
> > On Sunday 21 March 2010 08:41:15 Thomas Sachau wrote:
> >> I see, that the sgml herd seems to be empty for a longer time, so i
> >> would like to ask, if someone wants to take that herd and the related
> >> ebuilds and bugs over or if we should delete that herd and assign
> >> related ebuilds/bugs to m-n.
> > 
> > if someone were to step up, we'd have to undo any changes we just did. 
> > why not add m-n to the herd definition.
> 
> What exactly do you suggest?
> 
> My suggestion is to give people some time to join that herd (which had open
> bugs back from 2006!) for some time and if nothing happens, remove this
> unused herd and assign bugs and ebuilds to m-n, so people at least see,
> that those ebuilds are not maintained, instead of getting the false
> impression of maintainership by an empty herd.

deleting logical herds and updating all the xml files takes effort, as does 
reverting those changes when someone steps up.  from what i can see, there is 
no gain doing this.

simple mark the herd itself as m-n, update the staffing needs page, and then 
re-assign the bugs to m-n while keeping sgml herd in the cc.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-03-22  6:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-21 12:41 [gentoo-dev] Empty herd: sgml Thomas Sachau
2010-03-21 17:06 ` Mike Frysinger
2010-03-21 21:22   ` Thomas Sachau
2010-03-22  6:59     ` Mike Frysinger [this message]
2010-03-22  3:25 ` Jorge Manuel B. S. Vicetto
2010-03-22 13:29   ` Alex Alexander

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=201003220259.18739.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=tommy@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