Difference between revisions of "Electronic Voting"

From OSGeo
Jump to navigation Jump to search
(Created page with "Until 2013 elections were a completely manual process. For the 2014 elections we intend to introduce an Electronic Voting process to automize some of the tasks involved. The effo...")
 
 
(2 intermediate revisions by one other user not shown)
Line 2: Line 2:
  
 
== Requirements ==
 
== Requirements ==
* Nomination data is maintained on a server  
+
* Nomination data is maintained on a server
 
* Candidates from the nomination list are automatically transfered / copied / referenced by the elections form
 
* Candidates from the nomination list are automatically transfered / copied / referenced by the elections form
 
* Charter Members maintain their own data (email address, postal address, land of birth and/or residence (this needs to be clarified))
 
* Charter Members maintain their own data (email address, postal address, land of birth and/or residence (this needs to be clarified))
Line 11: Line 11:
  
 
== Implementation ==
 
== Implementation ==
The technology used for the elections is ... options:
 
* implemented and maintained by OSGeo
 
** what technology?
 
** who maintains it?
 
** Is the data private / do we need privacy statement and all Charter Members to sign it (is ticking a checkbox when loggin in sufficient)?
 
* a generic elections software
 
** installation, maintenace
 
** Does OSGeo have to change the elections process to fit with the software req'
 
  
== Time Plan ==
+
The technology used for the elections is a [https://www.limesurvey.org/en/ Lime Survey] instance hosted by [http://www.ucdavis.edu/ UC Davis] until 2015 and by [http://geo-spatial.org/ OSGeo Romania] since 2016.
This is just a proposal so we have something to aim for:
+
 
* 2014.01.01 Decide on which software to use
+
* Access url: http://geo-spatial.org/osgeo2016/
* Modify election proces accordingly
+
* Software maintained by OSGeo Romania members
** Requires board approval
+
* Isolated instance for OSGeo, not shared database with other organizations
* 2014.03.01 Implement the system
+
* Currently (2016) administered by [[Vasile Craciunescu]] with [[Alex Mandel]] and [[Jorge Sanz]] as backups.
* 2014.04.01 Enter Charter Member data
+
* It will store minimal Charter Members data (name, e-mail) to allow send them notifications and updates.
** notify Charter Members to doublecheck and update
+
* Main [https://www.limesurvey.org/en/about-limesurvey/features features]
* 2014.05.01 Test run, modify, fix
+
** 28 question types
* 2014.06.01 Board approval of the policy, system and implementation
+
** Validation
* 2014.07.01 Elections 2014
+
** Open surveys or closed and only available to selected groups
 +
** It can register ballot metadata (timestamps and IP)
 +
** Generates reports in HTML/CSV/PDF/etc.
 +
 
 +
Some of the requirements are not fulfilled by this system:
 +
 
 +
* The nominees is not automatically transferred from our wiki
 +
** Minor problem, it's usually a short list
 +
* If we want to keep things simple (avoid creating users to everyone), the CRO (or the Survey admins) will have to maintain the Charter Members database
 +
** Major problem, before the elections we will have to send a confirmation mail (we can do this with the system) but also announce it on the lists to assure everyone is aware of this system and ask them to notify the CRO about non working e-mail addresses or whatever.
  
 
== Members ==
 
== Members ==
 +
 
* [[Bart van den Eijnden]] (Lead)
 
* [[Bart van den Eijnden]] (Lead)
 
* [[Michael Gerlek]] (past CRO, OSGeo Secretary)
 
* [[Michael Gerlek]] (past CRO, OSGeo Secretary)
 
* [[Arnulf Christl]] (past CRO)
 
* [[Arnulf Christl]] (past CRO)
 +
* [[Jorge Sanz]]
 +
* [[Vasile Craciunescu]]
 
* NN implementer
 
* NN implementer
 
* NN maintainer
 
* NN maintainer
Line 42: Line 46:
 
[[Category:Membership]]
 
[[Category:Membership]]
 
[[Category:Elections]]
 
[[Category:Elections]]
 +
[[Category:Election 2014]]

Latest revision as of 12:46, 7 June 2016

Until 2013 elections were a completely manual process. For the 2014 elections we intend to introduce an Electronic Voting process to automize some of the tasks involved. The effort will be lead by Bart van den Eijnden.

Requirements

  • Nomination data is maintained on a server
  • Candidates from the nomination list are automatically transfered / copied / referenced by the elections form
  • Charter Members maintain their own data (email address, postal address, land of birth and/or residence (this needs to be clarified))
  • Charter Members vote by logging into the system and filling out an electronic form.
  • Charter members receive a notification of their vote by mail (content stripped / clarify)
  • The CRO oversees the process
  • Individual election results are not public

Implementation

The technology used for the elections is a Lime Survey instance hosted by UC Davis until 2015 and by OSGeo Romania since 2016.

  • Access url: http://geo-spatial.org/osgeo2016/
  • Software maintained by OSGeo Romania members
  • Isolated instance for OSGeo, not shared database with other organizations
  • Currently (2016) administered by Vasile Craciunescu with Alex Mandel and Jorge Sanz as backups.
  • It will store minimal Charter Members data (name, e-mail) to allow send them notifications and updates.
  • Main features
    • 28 question types
    • Validation
    • Open surveys or closed and only available to selected groups
    • It can register ballot metadata (timestamps and IP)
    • Generates reports in HTML/CSV/PDF/etc.

Some of the requirements are not fulfilled by this system:

  • The nominees is not automatically transferred from our wiki
    • Minor problem, it's usually a short list
  • If we want to keep things simple (avoid creating users to everyone), the CRO (or the Survey admins) will have to maintain the Charter Members database
    • Major problem, before the elections we will have to send a confirmation mail (we can do this with the system) but also announce it on the lists to assure everyone is aware of this system and ask them to notify the CRO about non working e-mail addresses or whatever.

Members