From: Alec Warner <antarus@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] Foundation meeting agenda for April 2018
Date: Sun, 8 Apr 2018 21:38:47 -0400 [thread overview]
Message-ID: <CAAr7Pr8xE2fwk1OmWY5Kwr=gVe8csf=4iBWwdieQq3fNUTicvw@mail.gmail.com> (raw)
In-Reply-To: <876051rxwc.fsf@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]
On Sun, Apr 8, 2018 at 9:06 PM, Matthias Maier <tamiko@gentoo.org> wrote:
> This is a request by two developers (and not by the council). But I
> would like to answer one of your questions.
>
>
> On Sun, Apr 8, 2018, at 19:11 CDT, zlg <zlg@gentoo.org> wrote:
>
> > [...]
> >
> > To the Council:
> >
> > What makes you accountable to this community? Why should we trust or
> > respect you when you have nothing on the line except a title? What
> > happens next if these affirmations are made? What's your angle, your
> > real motivation?
>
> The Gentoo Developer community has used GLEP 39 [1] for its
> self-organization for the last 12 years. Our "real motivation" (speaking
> as individual developers) is to keep it that way.
>
>
> > How do you trust a Council member when they have nothing to lose by
> > acting against the community?
>
> I fail to see how trying to get an affirmation that the Gentoo
> Foundation is still on board with GLEP 39 is "acting against the
> community".
>
> We have had a very public case of prometheanfire pushing for dissolving
> the current metastructure and reorganizing the community under the
> Foundation. Andreas and I, personally, disagree with that.
>
I'm curious what the difference between 'discussing an idea' and 'pushing
for an idea' is.
I want a community where we can discuss ideas (even ideas the council or
you dislike) without it causing a major incident or people getting upset
about it.
What would you have people who have these ideas do differently?
-A
> Best,
> Matthias
>
> [1] https://www.gentoo.org/glep/glep-0039.html
>
[-- Attachment #2: Type: text/html, Size: 2453 bytes --]
next prev parent reply other threads:[~2018-04-09 1:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 20:27 [gentoo-project] Foundation meeting agenda for April 2018 Matthew Thode
2018-04-08 20:43 ` Matthias Maier
2018-04-08 20:48 ` Andreas K. Huettel
2018-04-09 0:11 ` zlg
2018-04-09 0:14 ` Rich Freeman
2018-04-09 1:06 ` Matthias Maier
2018-04-09 1:38 ` Alec Warner [this message]
2018-04-09 4:10 ` William Hubbs
2018-04-09 11:11 ` Luca Barbato
2018-04-09 3:29 ` zlg
2018-04-09 3:42 ` Virgil Dupras
2018-04-09 4:39 ` zlg
2018-04-09 5:47 ` Michał Górny
2018-04-09 6:28 ` Paweł Hajdan, Jr.
2018-04-09 14:12 ` William Hubbs
2018-04-09 7:17 ` Matthias Maier
2018-04-09 7:50 ` zlg
2018-04-09 12:38 ` Rich Freeman
2018-04-09 8:23 ` Andreas K. Huettel
2018-04-09 9:56 ` Matthew Thode
2018-04-09 11:36 ` Luca Barbato
2018-04-09 15:44 ` Matthew Thode
2018-04-09 12:01 ` Alexis Ballier
2018-04-09 6:12 ` Michał Górny
2018-04-09 4:25 ` Alec Warner
2018-04-09 15:53 ` Matthias Maier
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='CAAr7Pr8xE2fwk1OmWY5Kwr=gVe8csf=4iBWwdieQq3fNUTicvw@mail.gmail.com' \
--to=antarus@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