Gentoo Archives: gentoo-project

From: Pacho Ramos <pacho@g.o>
To: gentoo-project@l.g.o
Subject: Re: [gentoo-project] Re: [gentoo-dev-announce] Re: Call for Council Agenda Items - 11-Nov-2014
Date: Wed, 05 Nov 2014 22:47:47
Message-Id: 1415227658.15134.12.camel@gentoo.org
In Reply to: Re: [gentoo-project] Re: [gentoo-dev-announce] Re: Call for Council Agenda Items - 11-Nov-2014 by Rich Freeman
1 El mié, 05-11-2014 a las 07:33 -0500, Rich Freeman escribió:
2 > On Wed, Nov 5, 2014 at 5:49 AM, Pacho Ramos <pacho@g.o> wrote:
3 > > El mié, 05-11-2014 a las 11:43 +0100, Alexander Berntsen escribió:
4 > >> On 05/11/14 11:41, Pacho Ramos wrote:
5 > >> > I was wondering about making mandatory for Gentoo developers to
6 > >> > also be subscribed to gentoo-dev ML
7 > >> The only possible outcomes of this is that people either disobey the
8 > >> rule, or route all that traffic to its own directory that they
9 > >> effectively treat as a rubbish bin.
10 > >
11 > > I mean: they can still ignore the threads there... but they are on their
12 > > own if some important decision is taken there and they missed it because
13 > > they send all mails to their trash.
14 > >
15 >
16 > They can ignore the threads on -dev now, and they're still just as on
17 > their own if they miss something important.
18 >
19 > * While it is any developer's choice not to participate on the gentoo-dev and
20 > gentoo-project mailing lists, they nevertheless serve as main communication
21 > channels. If something has been discussed there, and then action has been taken,
22 > the council regards ignorance of the discussion not as a good foundation for
23 > protests against the actions.
24 >
25 > http://www.gentoo.org/proj/en/council/meeting-logs/20140408-summary.txt
26 >
27 > I'd have to go back and re-read - I don't think that the Council was
28 > specifically asked to make gentoo-dev mandatory. I can put that on
29 > the agenda, but my personal opinion is that it is unlikely to result
30 > in anything other than re-iterating the statement above, and leaving
31 > gentoo-dev non-mandatory, with the existing guidelines for using
32 > -dev-announce, etc. My personal opinion is that if devs want to just
33 > maintain their packages in peace and follow new policies when they are
34 > poked about them, I don't see the harm in it. If devs want to have a
35 > big say in what the policies are, then they're going to get their
36 > hands dirty.
37 >
38 > Let me know if you still want this on the agenda. I speak for the
39 > council only in the sense that I'm quoting the recent decision.
40 >
41
42 Well, do what you prefer :)
43
44 I suggested it as I think would be more useful to know that we can rely
45 on gentoo-dev ML for really big and long discussions and to try to
46 ensure a bit more that people can at least remember that they saw some
47 thread that maybe would interest them... but if you, that have more
48 experience with this, think that it won't change much, no problem ;)