Open Stack

On Fri, Apr 03, 2015 at 02:35:13PM -0400, Matthew Treinish wrote:
> On Fri, Apr 03, 2015 at 01:15:28PM -0400, Anita Kuno wrote:
> > Problem Statement: OpenStack is growing, the election tools we use for
> > gathering nominations and communicating status of nominations, the
> > current workflow can be found on this wikipage:
> > https://wiki.openstack.org/wiki/Election_Officiating_Guidelines is
> > unable to be accessed by election officials and the electorate in a
> > clear way. The process we use for actually conducting the polls is fine.
> > We need to discuss and agree on a new workflow for posting
> > self-nominations and platforms for elections.
> > 
> > Does anyone have  input on tools that we might use to meet these
> > requirements for self nomination and platform management in elections?
> > Requirements:
> > * archivable
> > * public
> > * unable to be edited once posted
> > * clear differentiation between governed and ungoverned elections
> > * candidates can self-nominate
> > * low barrier to entry for tools, candidates shouldn't be restricted due
> > to lack of knowledge of tools
> 
> Well, doesn't the ML actually meet all of these requirements, except for having
> the distinction between governed and ungoverned elections. Maybe we should just
> build some tooling that watches the ML for posts with a certain subject (like
> what you and the other election officials are currently manually enforcing) and
> check whether the project election is governed or not, updates a wiki, etc. I
> don't think a little bot to do that would be that difficult to write. (although
> I could be easily overlooking something)
> 

I brought this up on IRC earlier today, but I figured I should post it to the ML
too just in case people missed it in the scrollback. I wrote a bit of code to show
how I thought the ML could still be used to do this:

https://github.com/mtreinish/electionbot

I haven't actually tried to run anything in the repo yet, it's just a concept at
this point. But, I wanted to share it before I put too much effort into it to
get some feedback on the approach.

-Matt Treinish
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20150422/908e464f/attachment.pgp>