Gentoo Archives: gentoo-dev

From: George Shapovalov <george@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Herds, Teams and Projects
Date: Fri, 28 Apr 2006 22:51:49
Message-Id: 200604290047.12079.george@gentoo.org
In Reply to: Re: [gentoo-dev] Herds, Teams and Projects by "Kevin F. Quinn (Gentoo)"
1 Saturday, 29. April 2006 00:28, Kevin F. Quinn (Gentoo) Ви написали:
2 > On Fri, 28 Apr 2006 21:29:58 +0200
3 >
4 > George Shapovalov <george@g.o> wrote:
5 > > Friday, 28. April 2006 21:20, Kevin F. Quinn (Gentoo) wrote:
6 > > > 3) A herd does not have an email address - it's not a person or
7 > > > group of people so an email address is nonsensical.
8 > >
9 > > 3a) A herd has an associated alias
10 > > 3b) Individual developers add yourself (explicitly or get added by
11 > > means of herds.xml (gentoo module in cvs, under misc)) to this alias.
12 >
13 > I thought this was the whole point of seemant's original message - it
14 > is projects or teams that have a mail alias. Some herds happen to have
15 > the same name as a project or team, but it's the team that you email,
16 > not the herd. It doesn't make sense to email a herd, any more than it
17 > makes sense to send email to an ebuild. It does however make sense to
18 > email the maintainer of a herd, in the same way as it makes sense to
19 > email the maintainer of an ebuild.
20 Well, yes, you don't email a herd per se (if we strictly stick to these
21 terms :)), but rather maintainers associated with it (via some project or
22 listed in herds.xml). Above is just a mechanism that makes sure your email
23 gets delivered to the right people. But we really now just do nitpicking of
24 the terminology (which, although, the original message by Seemant was about).
25 I just wanted to mention aliases to clarify the connection between packages,
26 maintainers and herds.xml/metadata.xml.
27
28 George
29
30 --
31 gentoo-dev@g.o mailing list