| 1 |
Hello, all. |
| 2 |
|
| 3 |
So considering the previous thread, the Council and QA discussions, I |
| 4 |
have prepared a new version of the metadata.xml update. To hopefully |
| 5 |
make everyone happy, I come with this three-step process: |
| 6 |
|
| 7 |
1. Add type="" attribute to <maintainer/> tag (see attached patch), |
| 8 |
|
| 9 |
2. Convert <herd/> to <maintainer type="herd"/>, |
| 10 |
|
| 11 |
3. Eventually drop <herd/> from DTD. |
| 12 |
|
| 13 |
If you like the idea, I'll prepare a smart conversion script soon. |
| 14 |
|
| 15 |
As for the exact details, I've pretty much decided to go for featurism |
| 16 |
here, IOW making everyone happy. It also proves how absurd typing |
| 17 |
maintainers is but if you really feel like having it, sure. The default |
| 18 |
is 'developer', <herd/> tags would be converted into 'herd' and there |
| 19 |
are other options including 'proxy-maintainer', 'project', 'team' meant |
| 20 |
to fit all our wannabies. The diff explains the particular options. |
| 21 |
|
| 22 |
The main benefit of this project over other ideas is that it preserves |
| 23 |
backwards compatibility. We're adding a new attribute which should |
| 24 |
simply be ignored by old tools. Since we still require <email/> to be |
| 25 |
something valid, the output will change a bit but will still be |
| 26 |
meaningful (or even more meaningful in some cases). |
| 27 |
|
| 28 |
And since I removed <herd>no-herd</herd> some time ago, we can drop |
| 29 |
<herd/> tags without worrying. |
| 30 |
|
| 31 |
Note: this is just about metadata.xml, I'm not touching herds.xml. |
| 32 |
|
| 33 |
What do you think? |
| 34 |
|
| 35 |
-- |
| 36 |
Best regards, |
| 37 |
Michał Górny |
Archives