From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo Council Elections Results for term 2014-2015
Date: Sat, 19 Jul 2014 09:14:46 -0400 [thread overview]
Message-ID: <CAGfcS_=0niktFyaV=n5-z94REdF6J2JEh16egQsVmqhm9AAYtA@mail.gmail.com> (raw)
In-Reply-To: <20140719135836.764bf605@googlemail.com>
On Sat, Jul 19, 2014 at 8:58 AM, Ciaran McCreesh
<ciaran.mccreesh@googlemail.com> wrote:
> On Fri, 18 Jul 2014 07:37:09 -0400
> Rich Freeman <rich0@gentoo.org> wrote:
>> Don't take rankings too personally. The algorithm has to stick
>> something at the top, and something at the bottom, and it isn't like
>> we have tons of dead wood on the ballot.
>
> The more interesting issue is the number of times some people were
> ranked below _ron, though. There are people serving on the Council who,
> for some developers, are less preferable than rerunning the entire
> election with new candidates.
>
Whatever. Votes are preferences. I'd just as soon that people be
honest with them. I sometimes vote for people below reopen and I'm
not going to be bothered if some place me below it. You can never
elect a body that matches everybody's preferences, and I'd like to
think that people would tend to vote for council members that will
strive to at least try to represent everybody regardless of whether
they disagree.
For my part, if somebody thinks I'm about to do something stupid,
you're always welcome to let me know. I try to post my feelings on
any controversial issue on -project before any meeting to give people
the opportunity to do just that. I can't promise that I'll agree, but
I will listen with the assumption that devs in general are fairly
smart people. Usually I try to favor compromises that at least
provide some way for everybody to get what they want, since that is
the "Gentoo Way(TM)."
Rich
next prev parent reply other threads:[~2014-07-19 13:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 1:00 [gentoo-project] Gentoo Council Elections Results for term 2014-2015 Chris Reffett
2014-07-17 1:48 ` Jorge Manuel B. S. Vicetto
2014-07-17 11:38 ` hasufell
2014-07-17 11:47 ` Dirkjan Ochtman
2014-07-17 11:49 ` hasufell
2014-07-17 12:15 ` Anthony G. Basile
2014-07-17 12:36 ` Samuli Suominen
2014-07-17 14:28 ` Richard Yao
2014-07-17 17:37 ` Tom Wijsman
2014-07-19 12:47 ` hasufell
2014-07-19 20:19 ` Tom Wijsman
2014-07-19 20:46 ` hasufell
2014-07-19 20:53 ` Seemant Kulleen
2014-07-19 21:03 ` Tom Wijsman
2014-07-17 17:50 ` Seemant Kulleen
2014-07-18 3:06 ` Richard Yao
2014-07-18 5:57 ` Ulrich Mueller
2014-07-18 10:07 ` Alexander Berntsen
2014-07-18 11:37 ` Rich Freeman
2014-07-19 12:58 ` Ciaran McCreesh
2014-07-19 13:14 ` Rich Freeman [this message]
2014-07-21 3:58 ` Donnie Berkholz
2014-07-17 13:04 ` Rich Freeman
2014-07-17 13:16 ` hasufell
2014-07-17 14:26 ` Rich Freeman
2014-07-17 15:59 ` Alexander Berntsen
2014-07-17 16:29 ` hasufell
2014-07-17 17:14 ` Manuel Rüger
2014-07-17 17:16 ` Rich Freeman
2014-07-17 17:49 ` Rich Freeman
2014-07-18 0:59 ` Jorge Manuel B. S. Vicetto
2014-07-18 7:01 ` Joshua Kinard
2014-07-18 9:39 ` Rich Freeman
2014-07-17 14:12 ` Richard Yao
2014-07-17 14:20 ` Ulrich Mueller
2014-07-17 15:13 ` Andreas K. Huettel
2014-07-17 11:44 ` Chris Reffett
2014-07-17 4:23 ` Samuli Suominen
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_=0niktFyaV=n5-z94REdF6J2JEh16egQsVmqhm9AAYtA@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