From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: Gentoo Elections <elections@gentoo.org>
Subject: Re: [gentoo-project] Gentoo Council Election Results for term 2018/2019 - verification of election result needed
Date: Fri, 13 Jul 2018 16:36:04 +0000 [thread overview]
Message-ID: <robbat2-20180713T162939-597035497Z@orbis-terrarum.net> (raw)
In-Reply-To: <1531463728.880.8.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]
On Fri, Jul 13, 2018 at 08:35:28AM +0200, Michał Górny wrote:
> W dniu pią, 13.07.2018 o godzinie 05∶50 +0000, użytkownik Robin H.
> Johnson napisał:
> > Point of order: Can the Infra contact for the election please clarify
> > the exact time that countify phase was run, because it looks like the
> > election was closed the election 20 minutes early.
...
> Countify was run at ~6:19 the next morning.
Thank you for verifying.
> Unless you have a very good reason to suspect that someone went as far
> as to create a submitted ballot manually after midnight and change its
> timestamp to cover the fact, I don't think we have any reason to
> be concerned with the results. That said, I'm all for improving
> the election software to prevent that.
Yes, it was reading jmb's mail and mentally thinking, hey, why is the
timestamp shown as 20 mins before the end of the election.
Action-item: make countify print 'FINAL' stats, and modify the cronjob
to clearly state 'INTERIM'
Later goals should really be moving the ballot submission/collection
system to something like Debian's balloting system that requires
GPG-signing ballots (and optionally encryption). We can keep votify for
tabulation or switch to a voting engine, since I'm not sure if Debian
uses the same STV tabulation method we do.
--
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Treasurer
E-Mail : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 1113 bytes --]
next prev parent reply other threads:[~2018-07-13 16:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 15:36 [gentoo-project] Gentoo Council Election Results for term 2018/2019 Jorge Manuel B. S. Vicetto
2018-07-12 15:54 ` Matthias Maier
2018-07-12 15:57 ` Matthew Thode
2018-07-13 16:57 ` Andrey Utkin
2018-07-12 16:21 ` Toralf Förster
2018-07-12 16:22 ` R0b0t1
2018-07-13 0:03 ` Benda Xu
2018-07-13 5:50 ` [gentoo-project] Gentoo Council Election Results for term 2018/2019 - verification of election result needed Robin H. Johnson
2018-07-13 6:35 ` Michał Górny
2018-07-13 16:36 ` Robin H. Johnson [this message]
2018-07-13 14:52 ` [gentoo-project] Gentoo Council Election Results for term 2018/2019 Jorge Manuel B. S. Vicetto
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=robbat2-20180713T162939-597035497Z@orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=elections@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