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