From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo Council nominee 2018/19 questions
Date: Thu, 28 Jun 2018 11:27:42 +0200 [thread overview]
Message-ID: <23348.43534.971234.375071@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <1530087907.849.13.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2931 bytes --]
>>>>> On Wed, 27 Jun 2018, Michał Górny wrote:
> 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)?
Things are usually not as clear cut as in your constructed example.
If there is consensus in a discussion (which doesn't exclude that
there could be single dissenting voices) then generally the council
should go with that. However, if there's consensus then normally
there's no reason for the council to get involved.
OTOH, if there is disagreement then the council may be asked to
resolve the issue. That's the reason why the council exists in the
first place, namely to have a procedure for deciding global issues,
without the need to have an all-devs vote for everything.
In short, I would not vote against developer consensus, but in case of
an unresolved controversy my vote would be based on my judgement what
will be best 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?
How would you even measure "proactivity", and how would you
distinguish between "the Council" and its members acting as
individuals? If I look at the number of agenda items for the past
term (excluding unfinished business and open bugs), then about 75% of
the items were submitted by council members, 20% by other developers,
and 5% by users. Then again, are council members simply submitting so
much because they at the same time are very active devs, or in their
capacity as council members?
> 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.
Presumably, I would not oppose a voting system similar to Debian's
"general resolution" (as suggested in [1]), if it has reasonably high
thresholds (because dissolving the Council every other month won't
help us either).
OTOH, I am a friend of the KISS principle [2], and we should be very
careful not to unnecessarily complicate our processes by adding too
many layers.
Ulrich
[1] https://projects.gentoo.org/council/meeting-logs/20180408-summary.txt
[2] https://en.wikipedia.org/wiki/KISS_principle
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2018-06-28 9:27 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
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 [this message]
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=23348.43534.971234.375071@a1i15.kph.uni-mainz.de \
--to=ulm@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