From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HmJeG-0000Nu-85 for garchives@archives.gentoo.org; Fri, 11 May 2007 01:10:20 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l4B19H9P030419; Fri, 11 May 2007 01:09:17 GMT Received: from snowy.fizzelpark.com (snowy.fizzelpark.com [85.25.140.198]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l4B17OTh028180 for ; Fri, 11 May 2007 01:07:24 GMT Received: (qmail 13534 invoked from network); 11 May 2007 01:07:24 -0000 Received: from 212.242.130.102 ([212.242.130.102]) by mail.fizzelpark.com ([85.25.252.58]) with ESMTP via SSL; 11 May 2007 01:07:24 -0000 From: Thilo Bangert Organization: Gentoo To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] missing tag in metadata.xml Date: Fri, 11 May 2007 03:05:23 +0200 User-Agent: KMail/1.9.5 References: <200705101738.42962.bangert@gentoo.org> <46433E31.4070107@gentoo.org> In-Reply-To: <46433E31.4070107@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3142085.VxJAkjlFVs"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200705110305.26339.bangert@gentoo.org> X-Archives-Salt: 1acf7ae6-92f6-4d4f-9edb-f902545f561a X-Archives-Hash: cd7e782e918f28a26f77cb7703f4fa9d --nextPart3142085.VxJAkjlFVs Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > you should look at > the archives to see what people decided. from reading the archives and the response so far as well as the current=20 documentation on the subject i conclude that the issue is still not clear=20 and people make up their own stuff as they go along. the following may be a formalisation of current (best) practices: - maintainers fall into three categories. herds, gentoo developers and non-gentoo proxy maintainers. - a herd is defined in herds.xml. exception: no-herd. no-herd is limited to the situation where no suitable herd can be found. - a gentoo developer is defined in dev-rel/roll-call/userinfo.xml. - every ebuild has a herd. - a package can belong to more than one herd. - a package can be maintened by no or more parties. - a package with herd different from 'no-herd' is said to be maintained by the members of that herd. - all maintainers different from herds state their maintainership using the tag. the tag requires the tag. - a package with herd 'no-herd' and no additional maintainers is said to be unmaintained. - a of maintainer-needed@g.o indicates no maintainership and is only allowed as the sole maintainer. meaning a single tag and a single no-herd tag. infact it is semantically equivalent to a single no-herd tag and no additional maintainers. - a package that is proxy maintained needs an additional gentoo association in form of a maintaining herd or gentoo developer. maintainer-needed@g.o may be such an association, but only if the original one disappeared. optionally one may want to include, although personally i prefer to state=20 it explicitly: - a missing or empty tag is equivalent to no-herd open questions: - what does it mean when the package is maintained by a herd and an additional maintainer? how does one determine the order in which to contact multiple maintainers? - are there situations in which we specify a other than no-herd but don't want its members to act as maintainers? =2E.. what are your current best practices regarding metadata? regards Thilo --nextPart3142085.VxJAkjlFVs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBGQ8FWxRElEoA5AncRAlIEAJ4/2FUGRkuVO11LzE4B1WjPDj188ACdEmzE e3zlgeQYRChLSkIFrGt1QRQ= =zyNo -----END PGP SIGNATURE----- --nextPart3142085.VxJAkjlFVs-- -- gentoo-dev@gentoo.org mailing list