From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo Council Elections Results for term 2014-2015
Date: Thu, 17 Jul 2014 17:13:56 +0200 [thread overview]
Message-ID: <201407171714.00108.dilfridge@gentoo.org> (raw)
In-Reply-To: <53C7B852.8070708@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 929 bytes --]
Am Donnerstag, 17. Juli 2014, 13:49:38 schrieb hasufell:
> Dirkjan Ochtman:
> > On Thu, Jul 17, 2014 at 1:38 PM, hasufell <hasufell@gentoo.org> wrote:
> >> Doesn't that make the vote invalid?
> >
> > I don't see why it would. Maybe if voters would have known in advance
> > that their votes might be compromised.
>
> IMO, it doesn't matter if the violation had an effect on the result. It
> matters that there was a violation of procedure.
Sure it was a violation of procedure.
Problem is, *if* we re-vote, then knowledge about the first vote enters the
decision. Which is a very tricky thing and can easily be argued to make the
hypothetical re-vote invalid in itself.
Unfortunate as the situation is, at least the voters' decision was not
influenced by the later publication of votes.
--
Andreas K. Huettel
Gentoo Linux developer (council, kde)
dilfridge@gentoo.org
http://www.akhuettel.de/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-07-17 15:08 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
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 [this message]
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=201407171714.00108.dilfridge@gentoo.org \
--to=dilfridge@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