Changes between Initial Version and Version 1 of PSC/Election2020

Timestamp:

Dec 10, 2019, 3:04:45 PM (5 years ago)

Author:

neteler

Comment:

Draft PSC Election2020

PSC/Election2020

@@ +1 @@
+__[[TOC]]__
+
+= PSC Election 2020 =
+
+**-- DRAFT --**
+
+== Call for election == 
+
+The PSC election 2020 starts on **DD MM YYYY** and ends on **DD MM YYYY**.
+The new committee will be formed by **N** members.
+This is in accordance with the current PSC chair and the original planning when constituting the PSC.
+
+
+=== 1. The process===
+
+The election process is split essentially in two phases:  1) the Nomination
+and 2) the Voting.  Final actions are announcing the results and officially
+forming the new PSC, formed by **N** members.
+
+
+==== 1.1 Nominations ====
+
+During the Nomination phase, '''any''' member of the GRASS-GIS community,
+can nominate '''any''' community member for being a candidate for the PSC.
+
+To set a nomination in motion, an e-mail should be directed to the CRO
+including '''name''', '''contact email''' and shortly '''why''' a person is recommended as
+a PSC member. The CRO will then contact the recommended person asking for
+confirmation.  The nominated person has to accept the candidacy for the PSC.
+
+In short, a nomination and its acceptance '''are required to be sent directly to
+the CRO''', in private.  Following, it is the CRO's task to officially announce a
+nomination.
+
+'''Note''', current PSC members will be asked if they wish to stand as a
+candidate for the upcoming election.
+
+
+==== 1.2 Voting ====
+
+The CRO will ensure to invite all eligible voters. 
+
+During the Voting period, eligible voters, being community members '''with SVN write access'''|in the contributors file **TODO**, can vote their preferred
+candidate(s) via an on-line tool which will protect privacy.
+
+Each voter can vote one time.  However, there is no limit as to how many, among
+the candidates, a voter can select.
+
+
+=== 2. Time frame ===
+
+ * announcement of elections: DD MM YYYY (incl. CRO)
+ * nomination period: DD MM YYYY to DD MM YYYY
+ * presentation of the candidates: DD MM YYYY to DD MM YYYY
+ * elections: DD MM YYYY to DD MM YYYY
+ * announcement of the newly elected PSC: DD MM YYYY
+
+==== 2.1 Nomination Period ====
+
+The nomination starts on DD MM YYYY at 12:00 UTC, runs strictly
+for 3 weeks and ends on DD MM YYYY.  Following this period,
+there will be a one week of no-action to have time to reflect and decide.
+
+You are kindly asked to refrain from canceling an already announced nomination
+or support and request for a new nomination.  Unless there are serious reasons
+to cancel a nomination, modification of the list of nominees will not be
+possible after the end of the 3rd week.
+
+
+==== 2.2 Voting Period ====
+
+The voting period will run from DD MM YYYY at 12:00 UTC up until DD MM YYYY.
+
+==== 2.3 Results ====
+
+Votes will be counted and the top **N** voted candidates will fill the seats
+to form the new PSC.  In case of a vote tie, the CRO will randomise the
+selection between the tied candidates for a PSC seat.
+
+Results to be announced, at latest, on DD MM YYYY.
+
+Afterwards, the newly formed PSC will elect the chair person, being one of the
+new members.
+
+
+=== 3. Overview ===
+
+==== 3.1 Nomination (I) ====
+
+  - from DD MM YYYY to DD MM YYYY
+  - e-mails directed to the CRO by:
+    - a community member to nominate a candidate
+    - the nominee to confirm acceptance of candidacy
+
+==== 3.2 Nomination (II) ====
+
+  - from DD MM YYYY to DD MM YYYY
+  - re-think, evaluate, decide for candidate(s)
+  - email directed to the CRO by a candidate for canceling candidacy
+   (possible '''only''' for important reasons)
+
+
+==== 3.3 Voting: from DD MM YYYY to DD MM YYYY ====
+
+  - eligible to vote are ~~all subscribers to either the
+   https://lists.osgeo.org/mailman/listinfo/grass-user  or  the
+   https://lists.osgeo.org/mailman/listinfo/grass-dev list~~
+  - community members with SVN/!GitHub/**TODO** write access (this includes translators) see https://lists.osgeo.org/pipermail/grass-psc/2016-May/001477.html, https://lists.osgeo.org/pipermail/grass-psc/2016-June/001488.html
+  - privacy/anonymity guaranteed by using https://vote.heliosvoting.org, an on-line voting system
+  - ~~system currently under consideration/evaluation is https://vote.heliosvoting.org~~
+  - voters will be invited via email
+
+==== 3.4 Results: at latest, from DD MM YYYY to DD MM YYYY ====
+
+
+== Preparation of the list of nominees for the [wiki:PSC] election 2020 ==
+
+'''Any community member is eligible to propose a new PSC member candidate. A motivation must be added why the proposed candidate may be a good choice for the PSC.'''
+
+To submit a PSC member nomination: 
+ * Confirm with the nominated person first.
+ * Send the nomination email to the CRO.
+   * The CRO will forward it to the [https://lists.osgeo.org/mailman/listinfo/grass-psc PSC mailing list] along with a copy to the [https://lists.osgeo.org/mailman/listinfo/grass-dev GRASS dev list] and the [https://lists.osgeo.org/mailman/listinfo/grass-user GRASS user list] - so that the community remains informed.
+   * The CRO will update the table of nominations below.
+
+~~Deadline: [http://www.timeanddate.com/worldclock/fixedtime.html?year=2020&month=06&day=16&hour=12&min=0&sec=0 Thursday, 16 June 2020, 12:00 UTC]~~ TBD
+
+The list of nominees:
+
+||'''Candidate's name'''||'''Country'''||By: '''(Nominator)''', link to announcement
+|| .. || .. || By ..
+|| .. || .. || By ..
+
+== Results ==
+
+TDB
+
+Voting result (ranking, name, number of votes):
+
+{{{
+1.  ...    NN
+2.  ...
+}}}
+
+
+The '''new GRASS GIS Project Steering Committee''' (PSC) is composed of **N** members (ranking, name, number of votes):
+
+{{{
+1.  ...    NN
+2.  ...
+}}}
+
+=== Details ===
+
+* Number of eligible voters: NNN
+* Cast votes: NNN
+
+==== Helios voting system ====
+
+  * Uploaded eligible voters file''' xxx bytes, at DD MM YYYY: done processing: NNN voters loaded
+  * Trustee fingerprint and Audit information
+
+
+==== Technicalities ====
+
+The entire election process is encrypted. The CRO, being
+the administrator of this "private" election, can only verify which of
+the invited members did vote.
+
+* The election URL: https://vote.heliosvoting.org/helios/e/GRASS-GIS-PSC-2020
+* Election Fingerprint: `xxxxxxxxxxx`
+
+===== Ballots =====
+
+Helios' voting system features "Audited Ballots". More information at:
+
+https://vote.heliosvoting.org/helios/elections/TODO/audited-ballots/
+
+
+===== Election tally =====
+
+Even more, anyone should be able to verify the election tally at "Helios
+Election Verifier":
+
+https://vote.heliosvoting.org/verifier/verify.html?election_url=/helios/elections/TODO
+
+
+===== Trustee =====
+
+Trustees are responsible for decrypting the election result. Each
+trustee generates a keypair and submits the public portion to Helios.
+When it's time to decrypt, each trustee needs to provide their secret
+key.
+
+For this election, however, the automatically selected, by the system,
+trustee was selected and no other persons where involved in this
+process.
+
+* Trustee #`1`: Helios Voting Administrator
+* Public Key Fingerprint: `xxxxxxxxxx`
+
+ 
+== Archived Material & Notes ==
+
+=== CRO ===
+
+* TDB
+
+=== Tentative schedule ===
+
+* ...
+
+=== Proposals ===
+
+* Missing in 2016, to be added to election procedure: candidacy period between nominations and voting
+
+=== Comments from 2016 ===
+
+==== Before the election ====
+
+On Fri, Jun 3, 2016 at 2:02 PM, Moritz Lennert wrote:
+> So, to summarize, my proposal would be:
+>
+> - Election of the entire PSC every three years
+> - All people with SVN access have the right to vote
+> - Elections are announced on grass-dev and grass-user with a clear
+> definition of procedure:
+>         - Anyone (or anyone with voting right ?) can nominate someone during
+> a period of a few (4?) weeks
+>         - Possibly: those who are already in the PSC and stand for elections
+> again do not need a nomination / can nominate themselves ?
+>         - Voting during 1 week
+>         - The ten candidates with the most votes make up the new PSC
+>
+> Moritz
+
+==== After the election ====
+
+nik at nikosalexandris.net Mon Aug 29 08:26:23 PDT 2016
+
+>There is this important question, asked by Micha Silver end of July (see https://lists.osgeo.org/pipermail/grass-user/2016-July/074529.html), "what we should expect from PSC members?"
+>
+>Some of the candidates went a bit deeper in presenting themselves. Others were less lengthy in their writing. All good.
+>
+>However, I propose herewith, for the next PSC election, the following: set as a requirement, for each candidate, to answer this very question as being asked from the community: "What should the community expect from your PSC membership?".
+