1 |
Chris Gianelloni wrote: |
2 |
> Again, you are confusing herds and projects. |
3 |
> |
4 |
> Here's another example of it done correctly. If you add a game to the |
5 |
> tree, the herd should be listed as games. Period. Even if you are |
6 |
> going to be the sole maintainer of the package, games should be the |
7 |
> herd. Why? Because it is a game, silly. |
8 |
> |
9 |
> There are quite a few packages under games-* that are completely |
10 |
> maintained by someone not on the games team, which means it is not |
11 |
> maintained by the games project. That doesn't change the fact that it |
12 |
> is a game, and belongs in the games herd. |
13 |
> |
14 |
> Herd == grouping of packages |
15 |
> Project == team of people |
16 |
|
17 |
This new terminology plain sucks. If you are sticking games into <herd> |
18 |
in metadata.xml, you are just confusing me and other people who are |
19 |
assigning bugs. You'll get mis-assigned bugs. Either don't do it or find |
20 |
another tag and get the DTD updated. <herd> is being used for assigning |
21 |
bugs, you are using it as a placeholder for something else. Category |
22 |
already tells us that it's a game, don't stick games into <herd> unless |
23 |
you actually maintain it. Thanks. |
24 |
|
25 |
|
26 |
-- |
27 |
Best regards, |
28 |
|
29 |
Jakub Moc |
30 |
mailto:jakub@g.o |
31 |
GPG signature: |
32 |
http://subkeys.pgp.net:11371/pks/lookup?op=get&search=0xCEBA3D9E |
33 |
Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E |
34 |
|
35 |
... still no signature ;) |