public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Mailing list moderation and community openness
Date: Wed, 21 Mar 2018 07:07:35 -0400	[thread overview]
Message-ID: <CAGfcS_n-LSOFsjpM3bdkbbc4ARJ8+xnLYwuF5GZQj34rau5_Cg@mail.gmail.com> (raw)
In-Reply-To: <20180321053601.GA4705@angelfall.a21an.org>

On Wed, Mar 21, 2018 at 1:36 AM, Eray Aslan <eras@gentoo.org> wrote:
> On Tue, Mar 20, 2018 at 10:28:48AM -0500, Matthew Thode wrote:
>> While I personally do no agree with mailing list moderation infra has
>> been tasked with moving forward on it.
>
> That was a somewhat tongue-in-cheek comment but not wholly.  You cant
> cop out by saying it was an order from council.  I understand if you
> dont but do consider it.  Fight the good fight.

Interesting.  When exactly should we all start ignoring the Council,
and when should we do what they say?  And what is the likely result of
that?

For all the complaining of "cabals" in Gentoo it seems odd to suggest
putting the final decisions of the one group that is about the least
democratic in the organization.

(That isn't really intended as a criticism: there are a lot of
practical reasons why infra operates as it does and I've yet to come
up with any better approach.  With the council/trustees the authority
comes from the collective, and nobody would pay attention to a
directive that didn't have a majority backing or the appearance of due
process.  With any other project the decisions are appealable to
council.  With infra one guy with the root password can cause a lot of
havoc, and the computer isn't going to stop and question what they're
doing.  That creates a lot of incentive to minimize the number of
people who are trusted.  In any case, I think it makes the most sense
to do the decision-making in more open/democratic processes, and then
minimize the execution footprint that requires "cabals.")

As I've commented elsewhere [1] I think an issue here is that we just
don't have enough of a critical mass to be able to afford to split
along ideological lines.  The set of developers interested in a
source-based distro is barely sufficient to create a viable
source-based distro.  If you split it into the subsets who prefer open
vs closed mailing lists on top of this then the individual groups lack
critical mass.  And so we're forced to co-exist, and agree on one or
the other, or some kind of compromise.

1 - https://rich0gentoo.wordpress.com/2016/02/27/gentoo-ought-to-be-about-choice/

-- 
Rich


  reply	other threads:[~2018-03-21 11:07 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 12:17 [gentoo-dev] Mailing list moderation and community openness Michael Palimaka
2018-03-20 12:22 ` Kristian Fiskerstrand
2018-03-20 12:26 ` Lars Wendler
2018-03-20 13:41   ` Gregory Woodbury
2018-03-20 16:09     ` [gentoo-project] " Rich Freeman
2018-03-20 15:28 ` Matthew Thode
2018-03-20 18:17   ` Kristian Fiskerstrand
2018-03-21 23:56     ` Chí-Thanh Christopher Nguyễn
2018-03-22  0:24       ` Kristian Fiskerstrand
2018-03-21  5:36   ` Eray Aslan
2018-03-21 11:07     ` Rich Freeman [this message]
2018-03-21 14:44     ` Alec Warner
2018-03-21 16:31       ` Eray Aslan
2018-03-21 16:46         ` Alec Warner
2018-03-21 16:55       ` R0b0t1
2018-03-21 17:19         ` Rich Freeman
2018-03-21 23:44           ` Gregory Woodbury
2018-03-22  5:24       ` [gentoo-dev] " Duncan
2018-03-20 15:44 ` [gentoo-dev] " Alexander Berntsen
2018-03-20 16:03   ` William Hubbs
2018-03-20 23:54     ` Benda Xu
2018-03-21  0:08       ` Rich Freeman
2018-03-21 23:56         ` Chí-Thanh Christopher Nguyễn
2018-03-22  0:33           ` Kristian Fiskerstrand
2018-03-22  0:37             ` M. J. Everitt
2018-03-22  6:31         ` Benda Xu
2018-03-22  8:30           ` Alexander Berntsen
2018-03-22 11:38             ` Rich Freeman
2018-03-22 12:07               ` Kristian Fiskerstrand
2018-03-27  1:19         ` kuzetsa
2018-03-27  1:26           ` Rich Freeman
2018-03-27  2:38             ` kuzetsa
2018-03-27  7:35               ` Rich Freeman
2018-03-27  7:34         ` [gentoo-dev] " Martin Vaeth
2018-03-27 12:55           ` Rich Freeman
2018-03-27 16:12             ` Martin Vaeth
2018-03-27 16:39               ` Rich Freeman
2018-03-28  2:21                 ` M. J. Everitt
2018-03-28  2:55                 ` R0b0t1
2018-03-28  4:41                   ` Stephen Christie
2018-03-28 13:48                     ` Michael Orlitzky
2018-03-28 11:03                   ` Rich Freeman
2018-03-28  6:11                 ` Dawid Weglinski
2018-03-28  6:33                 ` Martin Vaeth
2018-03-28 11:21                   ` Rich Freeman
2018-03-29  7:13                     ` Martin Vaeth
2018-06-11  1:55                     ` R0b0t1
2018-03-20 15:53 ` [gentoo-dev] " Pengcheng Xu
2018-03-21  2:22 ` Paweł Hajdan, Jr.
2018-03-21 23:56 ` Chí-Thanh Christopher Nguyễn
2018-03-22  0:27   ` Kristian Fiskerstrand
2018-06-10 18:29 ` Tom Wijsman

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_n-LSOFsjpM3bdkbbc4ARJ8+xnLYwuF5GZQj34rau5_Cg@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@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