From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev-announce] Re: Call for Council Agenda Items - 11-Nov-2014
Date: Wed, 5 Nov 2014 07:33:30 -0500 [thread overview]
Message-ID: <CAGfcS_mhCn47sacMuc=PEygcbP8cXJWfA=JxcAAe+Xa4f6Dcyw@mail.gmail.com> (raw)
In-Reply-To: <1415184549.15134.9.camel@gentoo.org>
On Wed, Nov 5, 2014 at 5:49 AM, Pacho Ramos <pacho@gentoo.org> wrote:
> El mié, 05-11-2014 a las 11:43 +0100, Alexander Berntsen escribió:
>> On 05/11/14 11:41, Pacho Ramos wrote:
>> > I was wondering about making mandatory for Gentoo developers to
>> > also be subscribed to gentoo-dev ML
>> The only possible outcomes of this is that people either disobey the
>> rule, or route all that traffic to its own directory that they
>> effectively treat as a rubbish bin.
>
> I mean: they can still ignore the threads there... but they are on their
> own if some important decision is taken there and they missed it because
> they send all mails to their trash.
>
They can ignore the threads on -dev now, and they're still just as on
their own if they miss something important.
* While it is any developer's choice not to participate on the gentoo-dev and
gentoo-project mailing lists, they nevertheless serve as main communication
channels. If something has been discussed there, and then action has been taken,
the council regards ignorance of the discussion not as a good foundation for
protests against the actions.
http://www.gentoo.org/proj/en/council/meeting-logs/20140408-summary.txt
I'd have to go back and re-read - I don't think that the Council was
specifically asked to make gentoo-dev mandatory. I can put that on
the agenda, but my personal opinion is that it is unlikely to result
in anything other than re-iterating the statement above, and leaving
gentoo-dev non-mandatory, with the existing guidelines for using
-dev-announce, etc. My personal opinion is that if devs want to just
maintain their packages in peace and follow new policies when they are
poked about them, I don't see the harm in it. If devs want to have a
big say in what the policies are, then they're going to get their
hands dirty.
Let me know if you still want this on the agenda. I speak for the
council only in the sense that I'm quoting the recent decision.
next prev parent reply other threads:[~2014-11-05 12:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGfcS_kUKB-U5iggJ+ieZF+m_0n_AH4DZSqBF1qgKaQVG5LjHA@mail.gmail.com>
[not found] ` <CAGfcS_mmV0O1J_dM60dccbYbPrSQzrNWQCf6W=EG+04ycAGSAg@mail.gmail.com>
2014-11-05 10:41 ` [gentoo-project] Re: [gentoo-dev-announce] Re: Call for Council Agenda Items - 11-Nov-2014 Pacho Ramos
2014-11-05 10:43 ` Alexander Berntsen
2014-11-05 10:49 ` Pacho Ramos
2014-11-05 10:54 ` Alexander Berntsen
2014-11-05 12:33 ` Rich Freeman [this message]
2014-11-05 22:47 ` Pacho Ramos
2014-11-05 12:34 ` Andreas K. Huettel
2014-11-05 22:50 ` Pacho Ramos
2014-11-05 11:06 ` Patrick Lauer
2014-11-05 15:56 ` hasufell
2014-11-06 11:53 ` Jeroen Roovers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGfcS_mhCn47sacMuc=PEygcbP8cXJWfA=JxcAAe+Xa4f6Dcyw@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox