From: Daniel Campbell <zlg@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Splitting developer-oriented and expert user mailing lists
Date: Tue, 5 Dec 2017 13:16:10 -0800 [thread overview]
Message-ID: <20171205211610.GA18378@clocktown> (raw)
In-Reply-To: <20171205085940.GA4167@stuge.se>
[-- Attachment #1: Type: text/plain, Size: 3365 bytes --]
On Tue, Dec 05, 2017 at 08:59:40AM +0000, Peter Stuge wrote:
> Daniel Campbell wrote:
> > On Sun, Dec 03, 2017 at 12:18:04AM +0100, Michał Górny wrote:
> > > I'd like to establish the following changes to the mailing lists:
> > >
> > > 1. Posting to gentoo-dev@ and gentoo-project@ mailing lists will be
> > > initially restricted to active Gentoo developers.
> >
> > I don't think this plan will have the effect you're going for,
>
> I agree, and I'll double down on my previous comment on this proposal:
>
> I consider the proposal to be the wrong solution.
>
>
> > but let's be honest here: the "RFC" is just a formality; the decision's
> > already been made.
>
> I hope that a mere proposal doesn't automatically mean policy change.
>
If proposals come from a select couple of people, there are high odds
that it's been discussed privately and the relevant people've been
convinced or otherwise pushed to implement the change. By the time it
hits the list, any cricitism is met with "too bad, we're doing it
anyway". I'm not sure how new you are to Gentoo, but it's been this way
since at least 2012.
>
> > If the "real leaders" of Gentoo want to divide and fragment the
> > community, it's their prerogative.
>
> When there is a request for comments, there should also be comments. :)
>
> Far too many fall into the simple trap that is tribalism, and I'd like
> to encourage everyone on this list to not be that kind of person,
> because there really is no "us and them", there is only "us".
>
I think the plan to split mailing lists serves as a way to insulate
developers from the effects of their decisions. Anyone with an
incongenial tone will have their voice bit revoked and their mail will
be dropped or rejected. It will likely be a silent rejection, so the
fallout is minimal. The plan itself is a manifestation of tribalism.
The "us" is a select group of people who've been blessed by mgorny and
friends. Everyone else is deemed a "do nothing" or some other insult,
regardless of their history or efforts with the distribution. Yes,
talking about that is ugly, but it's the truth. I've been on the
receiving end of it multiple times and have been witness to it many
others. It shows up in just about every corner of Gentoo. Creating a
technical schism won't fix it.
>
> > As we tell users who do something they're not supposed to: You get
> > to keep the pieces.
>
> Well, let's see what happens, now that both developers and
> non-developers have clearly spoken out *against* this proposal.
>
I'm not holding my breath on any positive change, but we'll see. It's
not like we have a choice in the matter. I guess we'll have to subscribe
to yet another mailing list if we want to stay informed. Maybe in a
year's time, we'll have gentoo-dev-expert as well, so the Chosen Ones
don't have to deal with developers they don't like.
This is my last mail in this thread. I've made my points and know they
will fall on deaf ears. You're not wrong in your approach; I don't share
that faith, is all. So I hope you don't interpret this as me yelling at
you.
>
> Kind regards
>
> //Peter
>
--
Daniel Campbell - Gentoo Developer, Trustee, Treasurer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-05 21:16 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 23:18 [gentoo-dev] [RFC] Splitting developer-oriented and expert user mailing lists Michał Górny
2017-12-03 1:33 ` R0b0t1
2017-12-03 22:03 ` Michał Górny
2017-12-04 5:59 ` R0b0t1
2017-12-04 17:28 ` Michał Górny
2017-12-06 7:42 ` R0b0t1
2017-12-03 18:01 ` kuzetsa
2017-12-03 18:34 ` Vincent-Xavier JUMEL
2017-12-03 21:31 ` Michał Górny
2017-12-04 20:29 ` Vincent-Xavier JUMEL
2017-12-04 21:21 ` William L. Thomson Jr.
2017-12-03 18:52 ` Alec Warner
2017-12-03 21:26 ` Michał Górny
2017-12-04 1:25 ` [gentoo-project] " Alec Warner
2017-12-03 19:19 ` Róbert Čerňanský
2017-12-03 21:35 ` Michał Górny
2017-12-04 18:11 ` Christopher Head
2017-12-04 18:34 ` kuzetsa
2017-12-04 19:31 ` Róbert Čerňanský
2017-12-03 20:30 ` Dirkjan Ochtman
2017-12-03 21:29 ` William Hubbs
2017-12-03 21:43 ` [gentoo-project] " Michał Górny
2017-12-03 22:33 ` Gerion Entrup
2017-12-03 23:23 ` Richard Bradfield
2017-12-04 13:18 ` [gentoo-project] " Dirkjan Ochtman
2017-12-04 17:02 ` Michał Górny
2017-12-05 11:05 ` Nils Freydank
2017-12-03 21:16 ` Damo Brisbane
2017-12-03 21:22 ` Damo Brisbane
2017-12-03 22:06 ` [gentoo-dev] Re: [gentoo-project] " Matt Turner
2017-12-04 17:05 ` Michał Górny
2017-12-04 0:37 ` Matt Turner
2017-12-04 0:51 ` Rich Freeman
2017-12-04 1:19 ` kuzetsa
2017-12-04 13:15 ` M. J. Everitt
2017-12-04 18:51 ` William L. Thomson Jr.
2017-12-04 18:57 ` kuzetsa
2017-12-04 19:19 ` William L. Thomson Jr.
2017-12-06 6:35 ` R0b0t1
2017-12-04 19:17 ` Alec Warner
2017-12-04 19:37 ` William L. Thomson Jr.
2017-12-04 19:54 ` Alec Warner
2017-12-04 21:08 ` William L. Thomson Jr.
2017-12-04 21:36 ` OT " William L. Thomson Jr.
2017-12-04 21:39 ` Kristian Fiskerstrand
2017-12-07 18:06 ` William L. Thomson Jr.
2017-12-08 20:22 ` That's all folks. (Re: OT Re: [gentoo-dev] Re: [gentoo-project] [RFC] Splitting developer-oriented and expert user mailing lists) Andreas K. Huettel
2017-12-08 20:30 ` Peter Stuge
2017-12-08 20:43 ` Gordon Pettey
2017-12-08 20:46 ` Alexander Berntsen
2017-12-10 0:29 ` Daniel Campbell
2017-12-10 1:13 ` Rich Freeman
2017-12-10 4:31 ` Daniel Campbell
2017-12-10 14:55 ` Rich Freeman
2017-12-10 8:21 ` Michał Górny
2017-12-10 8:24 ` R0b0t1
2017-12-10 19:54 ` kuzetsa
2018-02-11 19:42 ` Matthew Thode
2017-12-11 10:30 ` Andrew Savchenko
2017-12-08 7:43 ` OT Re: [gentoo-dev] Re: [gentoo-project] [RFC] Splitting developer-oriented and expert user mailing lists R0b0t1
2017-12-09 1:20 ` Georg Rudoy
2017-12-09 1:57 ` R0b0t1
2017-12-09 2:18 ` R0b0t1
2017-12-04 20:15 ` Ulrich Mueller
2017-12-04 1:07 ` [gentoo-dev] " kuzetsa
2017-12-04 1:19 ` Peter Stuge
2017-12-04 2:56 ` kuzetsa
2017-12-04 6:02 ` R0b0t1
2017-12-04 20:30 ` Daniel Campbell
2017-12-05 8:59 ` Peter Stuge
2017-12-05 21:16 ` Daniel Campbell [this message]
2017-12-05 22:12 ` Rich Freeman
2017-12-05 22:19 ` Kristian Fiskerstrand
2017-12-05 22:25 ` Rich Freeman
2017-12-05 22:27 ` Kristian Fiskerstrand
2017-12-05 22:37 ` Rich Freeman
2017-12-05 22:41 ` Kristian Fiskerstrand
2017-12-05 23:01 ` Kristian Fiskerstrand
2017-12-05 23:14 ` [gentoo-project] " Rich Freeman
2017-12-05 23:12 ` Rich Freeman
2017-12-06 12:16 ` kuzetsa
2017-12-05 22:46 ` William L. Thomson Jr.
2017-12-05 23:02 ` Rich Freeman
2017-12-05 23:22 ` William L. Thomson Jr.
2017-12-05 23:25 ` Kristian Fiskerstrand
2017-12-05 23:40 ` William L. Thomson Jr.
2017-12-06 8:51 ` Andreas K. Huettel
2017-12-06 17:44 ` William L. Thomson Jr.
2017-12-07 2:48 ` R0b0t1
2017-12-05 23:34 ` William L. Thomson Jr.
2017-12-06 7:22 ` R0b0t1
2017-12-06 13:04 ` Rich Freeman
2017-12-07 2:36 ` R0b0t1
2017-12-04 23:58 ` kuzetsa
2017-12-05 21:53 ` Aaron W. Swenson
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=20171205211610.GA18378@clocktown \
--to=zlg@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