From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] metadata.xml un<herd/>-ization, v2
Date: Tue, 9 Dec 2014 12:59:26 +0100 [thread overview]
Message-ID: <21638.58398.407361.825969@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20141209004628.4de52564@pomiot.lan>
[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]
>>>>> On Tue, 9 Dec 2014, Michał Górny wrote:
> As for the exact details, I've pretty much decided to go for
> featurism here, IOW making everyone happy. It also proves how absurd
> typing maintainers is but if you really feel like having it, sure.
> The default is 'developer', <herd/> tags would be converted into
> 'herd' and there are other options including 'proxy-maintainer',
> 'project', 'team' meant to fit all our wannabies. The diff explains
> the particular options.
> <!ELEMENT maintainer ( email, (description| name)* )>
> + <!-- maintainer organizational type -->
> + <!-- developer: regular Gentoo developer (direct e-mail) -->
> + <!-- herd: herd (defined in herds.xml) -->
As the previously stated goal was to get rid of herds, I don't
understand why you want to reintroduce them as a value of the
type attribute. The existing herd elements should become either
type="project" or type="team" (everything that is not a project,
I suppose).
> + <!-- project: project (having Wiki/g.o project page) -->
> + <!-- proxy-maintainer: maintainer that is not a Gentoo developer
> + and commits via a proxy -->
"proxy-maintainer" is very confusing because you won't put the proxy
maintainer there, but the user who is being proxied. Please rename
to something like "proxied" (assuming that this exists as a word in
English) or "by-proxy".
> + <!-- team: team of people that is not a herd nor a project -->
> + <!ATTLIST maintainer type (developer|herd|project|proxy-maintainer|team) "developer" >
Ulrich
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-12-09 11:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 23:46 [gentoo-dev] metadata.xml un<herd/>-ization, v2 Michał Górny
2014-12-09 9:15 ` Michał Górny
2014-12-09 18:30 ` Michał Górny
2014-12-09 11:59 ` Ulrich Mueller [this message]
2014-12-09 15:23 ` Jeroen Roovers
2014-12-20 21:35 ` Tom Wijsman
2014-12-09 16:04 ` Michał Górny
2014-12-10 1:33 ` Rich Freeman
2014-12-10 7:06 ` Ulrich Mueller
2014-12-10 12:20 ` Rich Freeman
2014-12-20 21:52 ` Peter Stuge
2014-12-10 7:41 ` Sergey Popov
2014-12-12 13:52 ` Aaron W. Swenson
2014-12-09 15:49 ` Andreas K. Huettel
2014-12-09 16:02 ` Michał Górny
2014-12-09 16:17 ` Andreas K. Huettel
2014-12-09 16:34 ` Michał Górny
2014-12-09 17:59 ` Ulrich Mueller
2014-12-09 18:28 ` Michał Górny
2014-12-09 19:35 ` Luca Barbato
2014-12-11 6:23 ` [gentoo-dev] " Michael Palimaka
2014-12-11 16:45 ` Rich Freeman
2014-12-09 21:33 ` [gentoo-dev] " Michał Górny
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=21638.58398.407361.825969@a1i15.kph.uni-mainz.de \
--to=ulm@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