From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Clarify language of GLEP 39
Date: Sun, 15 Jan 2017 08:15:32 -0500 [thread overview]
Message-ID: <CAGfcS_=DoPgq8TwUj5vXEB4x2VJppyuC4YO15R2=izNCC2hKeQ@mail.gmail.com> (raw)
In-Reply-To: <90c70b17-6ae6-47d7-8f1b-32b327a25779@gentoo.org>
On Sun, Jan 15, 2017 at 7:58 AM, Aaron Bauman <bman@gentoo.org> wrote:
>
> It seems the developer community at large may need to revisit and vote on
> such a change for GLEP39. Assuming it is deemed important enough to pursue.
>
Nobody is going to organize such an action over a matter this trivial.
I'm not saying they can't, just that I'd be shocked if it happened.
And hence my point that deciding not to take any action is effectively
a decision that leads are not necessary, since nobody is empowered to
actually do anything over the lack of a lead. And that suits me fine
anyway.
I did clearly state that I didn't think the Council should change the
wording of GLEP39. It would merely clarify what it means. And
obviously it would take into account any opinions expressed by the
developer community at large.
On a side note, I think there is far too much tendency in these
debates to hold ourselves to decisions made a long time ago by
entirely different people. When big issues come up people ask
questions like "what did those people who only a few of us even have
ever talked to mean when they wrote xyz" or "what would Daniel do" and
so on. While sometimes understanding historical perspective can be
useful I don't consider ourselves bound by it. Ultimately how we
govern ourselves today is up to the developers of today.
--
Rich
next prev parent reply other threads:[~2017-01-15 13:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 2:17 [gentoo-project] Clarify language of GLEP 39 Doug Freed
2017-01-15 3:28 ` Rich Freeman
2017-01-15 3:40 ` Gokturk Yuksek
2017-01-15 3:53 ` Doug Freed
2017-01-15 9:10 ` Ulrich Mueller
2017-01-15 12:28 ` Rich Freeman
2017-01-15 12:58 ` Aaron Bauman
2017-01-15 13:00 ` Ciaran McCreesh
2017-01-15 13:13 ` Aaron Bauman
2017-01-15 13:19 ` Ciaran McCreesh
2017-01-15 13:21 ` Aaron Bauman
2017-01-15 14:18 ` Ulrich Mueller
2017-01-15 13:15 ` Rich Freeman [this message]
2017-01-15 13:18 ` Aaron Bauman
2017-01-15 14:27 ` Rich Freeman
2017-01-15 14:32 ` Ulrich Mueller
2017-01-15 4:58 ` Seemant Kulleen
2017-01-15 9:29 ` Michał Górny
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_=DoPgq8TwUj5vXEB4x2VJppyuC4YO15R2=izNCC2hKeQ@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