| 1 |
On Wed, 2006-06-14 at 15:54 +0200, Harald van Dijk wrote: |
| 2 |
> On Wed, Jun 14, 2006 at 09:13:34AM -0400, Chris Gianelloni wrote: |
| 3 |
> > > A great example of this are web-based applications. The web-apps project |
| 4 |
> > > does not own all the web-based packages in the Portage tree. There are many |
| 5 |
> > > such packages in the tree that are managed by developers that are not part |
| 6 |
> > > of the project. The web-apps project gets to decide what happens to the |
| 7 |
> > > packages grouped in the web-apps herd, but we neither have the right (nor |
| 8 |
> > > the desire) to tell other developers that they can't add web-based packages |
| 9 |
> > > to the tree; nor do other developers require our permission before adding |
| 10 |
> > > packages to the tree. |
| 11 |
> > |
| 12 |
> > Again, you are confusing herds and projects. |
| 13 |
> > |
| 14 |
> > Here's another example of it done correctly. If you add a game to the |
| 15 |
> > tree, the herd should be listed as games. Period. Even if you are |
| 16 |
> > going to be the sole maintainer of the package, games should be the |
| 17 |
> > herd. Why? Because it is a game, silly. |
| 18 |
> |
| 19 |
> Why do no games' metadata.xml specify games@ as the maintainer? I |
| 20 |
> thought it was because <herd>games</herd> implies this already, but if |
| 21 |
> it doesn't, then dozens of games can be considered unmaintained right |
| 22 |
> now, and fair game for anyone to mess with without approval. Are you |
| 23 |
> sure you like this interpretation of 'herd'? |
| 24 |
> |
| 25 |
> You're probably right that herd is supposed to mean what you say it |
| 26 |
> does, but existing practise, even by yourself, is very different from |
| 27 |
> it. |
| 28 |
|
| 29 |
Umm... no. |
| 30 |
|
| 31 |
See, if there's no maintainer listed, it defaults to the maintaining |
| 32 |
project *for that herd*... Here's another good example. Go and look at |
| 33 |
herds.xml and you'll see this: |
| 34 |
|
| 35 |
<herd> |
| 36 |
<name>games</name> |
| 37 |
<email>games@g.o</email> |
| 38 |
<description>Gentoo Games Team</description> |
| 39 |
|
| 40 |
<maintainingproject>/proj/en/desktop/games/index.xml</maintainingproject> |
| 41 |
</herd> |
| 42 |
|
| 43 |
As you can plainly see, the games team is the maintaining project for |
| 44 |
applications within the games herd, except in cases where a maintainer |
| 45 |
is explicitly listed. |
| 46 |
|
| 47 |
That wasn't so hard, now, was it? |
| 48 |
|
| 49 |
-- |
| 50 |
Chris Gianelloni |
| 51 |
Release Engineering - Strategic Lead |
| 52 |
x86 Architecture Team |
| 53 |
Games - Developer |
| 54 |
Gentoo Linux |
Archives