From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: Aaron Bauman <bman@gentoo.org>,
"Andreas K.Huettel" <dilfridge@gentoo.org>,
Kristian Fiskerstrand <k_f@gentoo.org>,
slyfox <slyfox@gentoo.org>, Matthias Maier <tamiko@gentoo.org>,
Ulrich Mueller <ulm@gentoo.org>,
Thomas Deutschmann <whissi@gentoo.org>,
williamh <williamh@gentoo.org>, amynka <amynka@gentoo.org>,
soap <soap@gentoo.org>, Rich Freeman <rich0@gentoo.org>
Subject: Re: [gentoo-project] Gentoo Council nominee 2018/19 questions
Date: Wed, 27 Jun 2018 10:25:07 +0200 [thread overview]
Message-ID: <1530087907.849.13.camel@gentoo.org> (raw)
In-Reply-To: <1529997071.2250.6.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
(CC-ing the remaining people to remind them to be subscribed to -project
and read archives)
W dniu wto, 26.06.2018 o godzinie 09∶11 +0200, użytkownik Michał Górny
napisał:
> To improve readability of the thread, I'll ask my question in reply to
> myself ;-).
Three more questions from me:
1. Do you believe that Council members should respect the requests of
the developer community even if they disagree with them? Or should
Council members decide based on their own judgment of arguments
presented?
Example: there's a heated debate, and the majority of respondents
request that X is implemented. However, after reading all the arguments
you don't think that X is a good idea but you haven't managed to
convince others. Would you vote for X (as your electorate demands)
or against it (as you believe is better for the distro)?
2. Do you believe that the Council should proactively research the state
of affairs and make decisions whenever they believe the direction
of the distribution needs to be adjusted? Or should it be passive
and avoid involvement unless developers explicitly request Council's
intervention?
3. Do you believe the developer community should hold the power
to veto or dissolve the Council at any point? Provided there's a global
developer vote agreeing on that.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2018-06-27 8:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 7:11 [gentoo-project] Gentoo Council nominee 2018/19 questions Michał Górny
2018-06-26 7:12 ` Michał Górny
2018-06-26 16:27 ` Kristian Fiskerstrand
2018-06-26 16:54 ` Matthew Thode
2018-06-26 16:56 ` Michał Górny
2018-06-26 17:14 ` Matthew Thode
2018-06-26 17:00 ` Kristian Fiskerstrand
2018-06-26 17:20 ` Matthew Thode
2018-06-26 17:29 ` Kristian Fiskerstrand
2018-06-26 18:11 ` Matthew Thode
2018-06-26 23:02 ` Aaron Bauman
2018-06-26 23:07 ` M. J. Everitt
2018-06-27 5:35 ` Ulrich Mueller
2018-06-29 2:12 ` William Hubbs
2018-06-26 14:37 ` Christopher Díaz Riveros
2018-06-26 16:40 ` Kristian Fiskerstrand
2018-06-26 23:31 ` Aaron Bauman
2018-06-27 0:13 ` Georgy Yakovlev
2018-06-26 22:17 ` Aaron Bauman
2018-06-26 22:25 ` Kristian Fiskerstrand
2018-06-26 22:43 ` Kristian Fiskerstrand
2018-06-27 6:41 ` Michał Górny
2018-06-27 8:25 ` Michał Górny [this message]
2018-06-27 21:13 ` Aaron Bauman
2018-06-27 21:50 ` Thomas Deutschmann
2018-06-28 8:23 ` Kristian Fiskerstrand
2018-06-28 9:27 ` Ulrich Mueller
2018-07-02 15:03 ` William Hubbs
2018-07-11 14:35 ` Mart Raudsepp
2018-06-29 5:15 ` Eray Aslan
2018-06-29 13:13 ` Mart Raudsepp
2018-06-29 18:25 ` Kristian Fiskerstrand
2018-07-01 0:15 ` William Hubbs
2018-07-01 20:58 ` Aaron Bauman
2018-07-01 19:37 ` Michał Górny
2018-07-01 20:25 ` Aaron Bauman
2018-07-01 23:24 ` Mart Raudsepp
2018-07-02 15:38 ` William Hubbs
2018-07-01 21:04 ` Matthias Maier
2018-07-01 21:11 ` Matthias Maier
-- strict thread matches above, loose matches on Subject: below --
2018-07-02 3:48 M. J. Everitt
2018-07-03 0:37 ` Aaron Bauman
2018-07-11 13:13 ` Mart Raudsepp
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=1530087907.849.13.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=amynka@gentoo.org \
--cc=bman@gentoo.org \
--cc=dilfridge@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=k_f@gentoo.org \
--cc=rich0@gentoo.org \
--cc=slyfox@gentoo.org \
--cc=soap@gentoo.org \
--cc=tamiko@gentoo.org \
--cc=ulm@gentoo.org \
--cc=whissi@gentoo.org \
--cc=williamh@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