Gentoo Archives: gentoo-project

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

Replies