Gentoo Archives: gentoo-dev

From: James Le Cuirot <chewi@g.o>
To: Markos Chandras <hwoarang@g.o>
Cc: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Inconsistent and messy layout of team maintainership in Gentoo
Date: Thu, 17 Sep 2015 20:06:36
Message-Id: 20150917210559.553689c5@symphony.aura-online.co.uk
In Reply to: Re: [gentoo-dev] Inconsistent and messy layout of team maintainership in Gentoo by Markos Chandras
1 On Thu, 17 Sep 2015 21:02:02 +0100
2 Markos Chandras <hwoarang@g.o> wrote:
3
4 > On 09/17/2015 12:05 PM, James Le Cuirot wrote:
5 > > On Thu, 17 Sep 2015 06:57:08 -0400
6 > > "Anthony G. Basile" <blueness@g.o> wrote:
7 > >
8 > >> Totally rethink the idea of emails aliases as something that is
9 > >> created on the fly. We just need to know who should get emails
10 > >> for a package when it comes to bug reports. Why can't that be
11 > >> calculated on the fly from the metadata.xml?
12 > >
13 > > I've not read every last part of this thread but I think I like
14 > > where this is going. I just want to be sure that people besides
15 > > those in the Java herd/project/whatever can continue to receive
16 > > emails for java@g.o. For instance, gnu_andrew is not a dev
17 > > and does not intend to be but he still likes to be CC'd on all Java
18 > > mail. I would not like to have to add his address to the
19 > > metadata.xml of every Java package.
20 > >
21 > i might not understand 100% what you are trying to say but why not add
22 > gnu_andrew to the java mail alias on pecker? how is metadata.xml going
23 > to solve this problem?
24
25 That's how we're already doing it now but I was concerned because of
26 what blueness said above. He was suggesting that the alias would be
27 created on the fly and I thought he meant from the project member list
28 but perhaps I misunderstood.
29
30 --
31 James Le Cuirot (chewi)
32 Gentoo Linux Developer