public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [pre-GLEP] Secrecy-respecting voting mechanism for Gentoo projects
Date: Sat, 28 Aug 2021 21:08:36 +0200	[thread overview]
Message-ID: <d5ecff0b0e2f4aedb0e6ef1d81ca5a02251270a2.camel@gentoo.org> (raw)
In-Reply-To: <YSqIEXE3bttIOLKv@Aaron-Baumans-MacBook-Pro.local>

On Sat, 2021-08-28 at 15:01 -0400, Aaron Bauman wrote:
> On Sat, Aug 28, 2021 at 12:30:15PM +0200, Michał Górny wrote:
> > Hi,
> > 
> > Please review the following pre-GLEP.
> > 
> > ---
> > GLEP: 9999
> > Title: Secrecy-respecting voting mechanism for Gentoo projects
> > Author: Michał Górny <mgorny@gentoo.org>
> > Type: Standards Track
> > Status: Draft
> > Version: 1
> > Created: 2021-08-27
> > Last-Modified: 2021-08-27
> > Post-History: 2021-08-27
> > Content-Type: text/x-rst
> > ---
> > 
> > Abstract
> > ========
> > 
> > A new voting system is devised with the aim of providing a single voting
> > system for all Gentoo elections and votes.  Automation is used to
> > eliminate the human bottleneck in processing the elections.  Votes are
> > submitted via random identifers, and the identifiers are sent to voters
> > via encrypted e-mail to protect the vote secrecy.  E-mail is used to
> > enable non-developer voters to participate.
> > 
> > 
> > Motivation
> > ==========
> > 
> > The votify/countify tooling used to run Gentoo elections dates back
> > to 2005.  While it still serves it purpose, it has grown antiquated
> > and is facing a few problems that are discouraging the developers from
> > using it.  These are:
> > 
> > The problems with the current tooling include:
> > 
> > 1. The elections require a lot of manual setup and attention.  This is
> >    causing noticeable delays and can raise doubts about the validity
> >    of elections.  For example, voters can still submit or modify votes
> >    after the deadline until the infra official collects them.
> > 
> 
> Given what we have seen in the security election this year, what
> determines *who* can start an election? Maybe some clarity in GLEP 39?

This is outside the scope of this GLEP.  It's about providing a tool,
not telling how projects select leads.  That's really in scope of GLEP
39 indeed.

> > At this point, votify is  practically used only for the Council
> > and Trustee elections.  The late attempts of using it for the Base
> > System and Security project elections have resulted in a lot of
> > frustration from the developers participating.  The vast majority of
> > project elections are currently run using third-party services or plain
> > mail votes.
> > 
> 
> I am not aware of anyone from the security team having issues with
> this... would you please expound on the issues of use?
> 

The complaints I've seen were primarily because of how long it took for
Elections team to publish results.  I suppose it was in comparison with
Helios where the results are immediately available.

-- 
Best regards,
Michał Górny




  parent reply	other threads:[~2021-08-28 19:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-28 10:30 [gentoo-project] [pre-GLEP] Secrecy-respecting voting mechanism for Gentoo projects Michał Górny
2021-08-28 12:59 ` Michael Orlitzky
2021-08-28 13:36 ` Rich Freeman
2021-08-28 19:01 ` Aaron Bauman
2021-08-28 19:07   ` Rich Freeman
2021-08-28 19:08   ` Michał Górny [this message]
2021-08-28 20:05 ` Alec Warner
2021-08-30  5:23 ` Robin H. Johnson
2021-08-30  8:09   ` 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=d5ecff0b0e2f4aedb0e6ef1d81ca5a02251270a2.camel@gentoo.org \
    --to=mgorny@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