| 1 |
On Wed, 2006-06-14 at 20:01 +0200, Jakub Moc wrote: |
| 2 |
> Chris Gianelloni wrote: |
| 3 |
> > Again, you are confusing herds and projects. |
| 4 |
> > |
| 5 |
> > Here's another example of it done correctly. If you add a game to the |
| 6 |
> > tree, the herd should be listed as games. Period. Even if you are |
| 7 |
> > going to be the sole maintainer of the package, games should be the |
| 8 |
> > herd. Why? Because it is a game, silly. |
| 9 |
> > |
| 10 |
> > There are quite a few packages under games-* that are completely |
| 11 |
> > maintained by someone not on the games team, which means it is not |
| 12 |
> > maintained by the games project. That doesn't change the fact that it |
| 13 |
> > is a game, and belongs in the games herd. |
| 14 |
> > |
| 15 |
> > Herd == grouping of packages |
| 16 |
> > Project == team of people |
| 17 |
> |
| 18 |
> This new terminology plain sucks. If you are sticking games into <herd> |
| 19 |
> in metadata.xml, you are just confusing me and other people who are |
| 20 |
> assigning bugs. You'll get mis-assigned bugs. Either don't do it or find |
| 21 |
> another tag and get the DTD updated. <herd> is being used for assigning |
| 22 |
> bugs, you are using it as a placeholder for something else. Category |
| 23 |
> already tells us that it's a game, don't stick games into <herd> unless |
| 24 |
> you actually maintain it. Thanks. |
| 25 |
|
| 26 |
"New" terminology? That is the definition of a herd. If you're using |
| 27 |
it incorrectly to mean something else, that doesn't mean I'm changing |
| 28 |
anything. |
| 29 |
|
| 30 |
The category doesn't tell you *anything* about who maintains it. Take |
| 31 |
dev-util/catalyst as an example, or app-misc/livecd-tools. You can't |
| 32 |
glean *any* maintainer information from the category. It just happens |
| 33 |
that all of the games are also in games-* categories. However, there |
| 34 |
are even some packages which are not in games-* that belong to the games |
| 35 |
herd, and are maintained by the games team. |
| 36 |
|
| 37 |
Also, we almost *never* get bugs assigned to us that don't belong, |
| 38 |
except for in the cases where a maintainer is listed, yet games gets the |
| 39 |
bug anyway. These cases are simple cases of whomever is doing the |
| 40 |
reassigning not checking the metadata, so any changes in behavior won't |
| 41 |
make a bit of difference here. |
| 42 |
|
| 43 |
-- |
| 44 |
Chris Gianelloni |
| 45 |
Release Engineering - Strategic Lead |
| 46 |
x86 Architecture Team |
| 47 |
Games - Developer |
| 48 |
Gentoo Linux |
Archives