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