public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] irregular metdata.xml check - 3rd edition
Date: Wed, 13 Feb 2008 00:42:17 -0800	[thread overview]
Message-ID: <20080213084217.GG4761@curie-int.orbis-terrarum.net> (raw)
In-Reply-To: <200802130930.18749.bangert@gentoo.org>

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

On Wed, Feb 13, 2008 at 09:30:14AM +0100, Thilo Bangert wrote:
> > 2. Check that metadata with a proxy maint also has a non-retired Gentoo
> > person listed.
> 'Proxy maintainer without gentoo association' means 'there is neither a 
> herd nor a gentoo maintainer listed'. you want to require a maintainer? a 
> lot more ebuilds will fail this check...
> 
> one may actually want to restrict that even further, and require both a 
> herd and a maintainer, as to define a pool of backup people in case the 
> gentoo maintainer retires.
I actually ran into this when jakub asked me to check some email
addresses that were in metadata.xml for bugzilla validity.

Originally, the one package was proxy maintained, having the external
and two Gentoo devs, with no-herd. The devs then retired, but the
external contributer was still interested, just lacking a contact.


-- 
Robin Hugh Johnson
Gentoo Linux Developer & Infra Guy
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

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

  reply	other threads:[~2008-02-13  8:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 21:01 [gentoo-dev] irregular metdata.xml check - 3rd edition Thilo Bangert
2008-02-12 23:44 ` Gilles Dartiguelongue
2008-02-13  3:21 ` Robin H. Johnson
2008-02-13  6:21   ` Alec Warner
2008-02-13  6:30     ` Robin H. Johnson
2008-02-13  8:30   ` Thilo Bangert
2008-02-13  8:42     ` Robin H. Johnson [this message]
2008-02-13  7:53 ` [gentoo-dev] " Christian Faulhammer

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=20080213084217.GG4761@curie-int.orbis-terrarum.net \
    --to=robbat2@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