| 1 |
>>>>> On Tue, 9 Dec 2014, Michał Górny wrote: |
| 2 |
|
| 3 |
> As for the exact details, I've pretty much decided to go for |
| 4 |
> featurism here, IOW making everyone happy. It also proves how absurd |
| 5 |
> typing maintainers is but if you really feel like having it, sure. |
| 6 |
> The default is 'developer', <herd/> tags would be converted into |
| 7 |
> 'herd' and there are other options including 'proxy-maintainer', |
| 8 |
> 'project', 'team' meant to fit all our wannabies. The diff explains |
| 9 |
> the particular options. |
| 10 |
|
| 11 |
> <!ELEMENT maintainer ( email, (description| name)* )> |
| 12 |
> + <!-- maintainer organizational type --> |
| 13 |
> + <!-- developer: regular Gentoo developer (direct e-mail) --> |
| 14 |
> + <!-- herd: herd (defined in herds.xml) --> |
| 15 |
|
| 16 |
As the previously stated goal was to get rid of herds, I don't |
| 17 |
understand why you want to reintroduce them as a value of the |
| 18 |
type attribute. The existing herd elements should become either |
| 19 |
type="project" or type="team" (everything that is not a project, |
| 20 |
I suppose). |
| 21 |
|
| 22 |
> + <!-- project: project (having Wiki/g.o project page) --> |
| 23 |
> + <!-- proxy-maintainer: maintainer that is not a Gentoo developer |
| 24 |
> + and commits via a proxy --> |
| 25 |
|
| 26 |
"proxy-maintainer" is very confusing because you won't put the proxy |
| 27 |
maintainer there, but the user who is being proxied. Please rename |
| 28 |
to something like "proxied" (assuming that this exists as a word in |
| 29 |
English) or "by-proxy". |
| 30 |
|
| 31 |
> + <!-- team: team of people that is not a herd nor a project --> |
| 32 |
> + <!ATTLIST maintainer type (developer|herd|project|proxy-maintainer|team) "developer" > |
| 33 |
|
| 34 |
Ulrich |
Archives