From: Roy Bamford <neddyseagoon@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-project <gentoo-project@lists.gentoo.org>,
Gentoo Elections <elections@gentoo.org>,
infrastructure <infrastructure@gentoo.org>,
council <council@gentoo.org>, trustees <trustees@gentoo.org>
Subject: [gentoo-project] Re: [RFC] vote.gentoo.org - a new voting frontend for Gentoo Elections
Date: Sat, 27 Jul 2019 11:40:12 +0100 [thread overview]
Message-ID: <IVJWTX3Z.ONQLCJ2P.H6HOYBYA@VOYN4NAJ.RTHOZEQV.J3JUG5JJ> (raw)
In-Reply-To: <d91bbdafe1390dc9b168fb0db7b334c8d87f29fe.camel@gentoo.org> (from mgorny@gentoo.org on Sat Jul 27 07:21:54 2019)
[-- Attachment #1: Type: text/plain, Size: 2467 bytes --]
On 2019.07.27 07:21, Michał Górny wrote:
> Hi,
>
> (CC-ing all parties interested in technicals, plus main consumers)
>
> I'd like to work on providing new web-based frontend for voting
> in Gentoo elections. It would replace votify in the pipeline but
> generate countify-compatible data, so the votes would still be counted
> using old tooling.
>
>
> Goals
> =====
> The goals for the new system would be to:
>
> 1. Improve privacy of votes by removing connection between voters
> and their confirmation IDs ASAP (not storing them unencrypted
> on permanent storage at all).
>
> 2. Unifying voting mechanism for developers and non-developers.
> The latter currently vote by mail and get their votes manually hacked
> into the system.
>
> 3. Removing dependency on dev.gentoo.org shell access for voting.
> This
> is implied by 2. but should also support any future efforts of
> reducing
> reliance on the single system in Infra.
>
> 4. Make it possible to use the system for unofficial elections (e.g.
> team lead votes). Currently setting a vote up requires root
> privileges
> on dev.g.o which is not really feasible.
>
5. Election Officials shall have a means to determine the voter turmout
from time to time while the election is in progress.
Today, its carried out by the -infra contact and publicised in reminders
to vote, IRC channel topics etc
[snip]
> Before the election starts, election officials prepare a list of voters
> containing their e-mail addresses and OpenPGP key fingerprints. They
> run a script which creates tokens for all voters, encrypts them, then
> mails them to voters.
How do we deal with expired public keys?
Devs get a warning at commit time before their key expires. Non devs
will not be permitted (by gpg) to sign a ballot with an expired key.
Here, the election officials script will be attempting to make use of
expired keys.
I can see another requirement ...
6. At the record date for any election, voters public keys shall be
checked for validity until at least the end of the voting period.
That will give election officials time to remind the electorate to fix
their keys.
[snip]
> Your comments
> =============
> What are your thoughts?
>
> --
> Best regards,
> Michał Górny
>
>
No showstopper comments from me.
--
Regards,
Roy Bamford
(Neddyseagoon) a member of
elections
gentoo-ops
forum-mods
arm64
[-- Attachment #2: Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-27 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 6:21 [gentoo-project] [RFC] vote.gentoo.org - a new voting frontend for Gentoo Elections Michał Górny
2019-07-27 10:40 ` Roy Bamford [this message]
2019-07-27 11:18 ` [gentoo-project] " Michał Górny
2019-08-09 5:49 ` Robin H. Johnson
2019-08-09 6:02 ` Michał Górny
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=IVJWTX3Z.ONQLCJ2P.H6HOYBYA@VOYN4NAJ.RTHOZEQV.J3JUG5JJ \
--to=neddyseagoon@gentoo.org \
--cc=council@gentoo.org \
--cc=elections@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=infrastructure@gentoo.org \
--cc=mgorny@gentoo.org \
--cc=trustees@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