| 1 | __[[TOC]]__ |
| 2 | |
| 3 | = PSC Election 2020 = |
| 4 | |
| 5 | **-- DRAFT --** |
| 6 | |
| 7 | == Call for election == |
| 8 | |
| 9 | The PSC election 2020 starts on **DD MM YYYY** and ends on **DD MM YYYY**. |
| 10 | The new committee will be formed by **N** members. |
| 11 | This is in accordance with the current PSC chair and the original planning when constituting the PSC. |
| 12 | |
| 13 | |
| 14 | === 1. The process=== |
| 15 | |
| 16 | The election process is split essentially in two phases: 1) the Nomination |
| 17 | and 2) the Voting. Final actions are announcing the results and officially |
| 18 | forming the new PSC, formed by **N** members. |
| 19 | |
| 20 | |
| 21 | ==== 1.1 Nominations ==== |
| 22 | |
| 23 | During the Nomination phase, '''any''' member of the GRASS-GIS community, |
| 24 | can nominate '''any''' community member for being a candidate for the PSC. |
| 25 | |
| 26 | To set a nomination in motion, an e-mail should be directed to the CRO |
| 27 | including '''name''', '''contact email''' and shortly '''why''' a person is recommended as |
| 28 | a PSC member. The CRO will then contact the recommended person asking for |
| 29 | confirmation. The nominated person has to accept the candidacy for the PSC. |
| 30 | |
| 31 | In short, a nomination and its acceptance '''are required to be sent directly to |
| 32 | the CRO''', in private. Following, it is the CRO's task to officially announce a |
| 33 | nomination. |
| 34 | |
| 35 | '''Note''', current PSC members will be asked if they wish to stand as a |
| 36 | candidate for the upcoming election. |
| 37 | |
| 38 | |
| 39 | ==== 1.2 Voting ==== |
| 40 | |
| 41 | The CRO will ensure to invite all eligible voters. |
| 42 | |
| 43 | During the Voting period, eligible voters, being community members '''with SVN write access'''|in the contributors file **TODO**, can vote their preferred |
| 44 | candidate(s) via an on-line tool which will protect privacy. |
| 45 | |
| 46 | Each voter can vote one time. However, there is no limit as to how many, among |
| 47 | the candidates, a voter can select. |
| 48 | |
| 49 | |
| 50 | === 2. Time frame === |
| 51 | |
| 52 | * announcement of elections: DD MM YYYY (incl. CRO) |
| 53 | * nomination period: DD MM YYYY to DD MM YYYY |
| 54 | * presentation of the candidates: DD MM YYYY to DD MM YYYY |
| 55 | * elections: DD MM YYYY to DD MM YYYY |
| 56 | * announcement of the newly elected PSC: DD MM YYYY |
| 57 | |
| 58 | ==== 2.1 Nomination Period ==== |
| 59 | |
| 60 | The nomination starts on DD MM YYYY at 12:00 UTC, runs strictly |
| 61 | for 3 weeks and ends on DD MM YYYY. Following this period, |
| 62 | there will be a one week of no-action to have time to reflect and decide. |
| 63 | |
| 64 | You are kindly asked to refrain from canceling an already announced nomination |
| 65 | or support and request for a new nomination. Unless there are serious reasons |
| 66 | to cancel a nomination, modification of the list of nominees will not be |
| 67 | possible after the end of the 3rd week. |
| 68 | |
| 69 | |
| 70 | ==== 2.2 Voting Period ==== |
| 71 | |
| 72 | The voting period will run from DD MM YYYY at 12:00 UTC up until DD MM YYYY. |
| 73 | |
| 74 | ==== 2.3 Results ==== |
| 75 | |
| 76 | Votes will be counted and the top **N** voted candidates will fill the seats |
| 77 | to form the new PSC. In case of a vote tie, the CRO will randomise the |
| 78 | selection between the tied candidates for a PSC seat. |
| 79 | |
| 80 | Results to be announced, at latest, on DD MM YYYY. |
| 81 | |
| 82 | Afterwards, the newly formed PSC will elect the chair person, being one of the |
| 83 | new members. |
| 84 | |
| 85 | |
| 86 | === 3. Overview === |
| 87 | |
| 88 | ==== 3.1 Nomination (I) ==== |
| 89 | |
| 90 | - from DD MM YYYY to DD MM YYYY |
| 91 | - e-mails directed to the CRO by: |
| 92 | - a community member to nominate a candidate |
| 93 | - the nominee to confirm acceptance of candidacy |
| 94 | |
| 95 | ==== 3.2 Nomination (II) ==== |
| 96 | |
| 97 | - from DD MM YYYY to DD MM YYYY |
| 98 | - re-think, evaluate, decide for candidate(s) |
| 99 | - email directed to the CRO by a candidate for canceling candidacy |
| 100 | (possible '''only''' for important reasons) |
| 101 | |
| 102 | |
| 103 | ==== 3.3 Voting: from DD MM YYYY to DD MM YYYY ==== |
| 104 | |
| 105 | - eligible to vote are ~~all subscribers to either the |
| 106 | https://lists.osgeo.org/mailman/listinfo/grass-user or the |
| 107 | https://lists.osgeo.org/mailman/listinfo/grass-dev list~~ |
| 108 | - 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 |
| 109 | - privacy/anonymity guaranteed by using https://vote.heliosvoting.org, an on-line voting system |
| 110 | - ~~system currently under consideration/evaluation is https://vote.heliosvoting.org~~ |
| 111 | - voters will be invited via email |
| 112 | |
| 113 | ==== 3.4 Results: at latest, from DD MM YYYY to DD MM YYYY ==== |
| 114 | |
| 115 | |
| 116 | == Preparation of the list of nominees for the [wiki:PSC] election 2020 == |
| 117 | |
| 118 | '''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.''' |
| 119 | |
| 120 | To submit a PSC member nomination: |
| 121 | * Confirm with the nominated person first. |
| 122 | * Send the nomination email to the CRO. |
| 123 | * 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. |
| 124 | * The CRO will update the table of nominations below. |
| 125 | |
| 126 | ~~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 |
| 127 | |
| 128 | The list of nominees: |
| 129 | |
| 130 | ||'''Candidate's name'''||'''Country'''||By: '''(Nominator)''', link to announcement |
| 131 | || .. || .. || By .. |
| 132 | || .. || .. || By .. |
| 133 | |
| 134 | == Results == |
| 135 | |
| 136 | TDB |
| 137 | |
| 138 | Voting result (ranking, name, number of votes): |
| 139 | |
| 140 | {{{ |
| 141 | 1. ... NN |
| 142 | 2. ... |
| 143 | }}} |
| 144 | |
| 145 | |
| 146 | The '''new GRASS GIS Project Steering Committee''' (PSC) is composed of **N** members (ranking, name, number of votes): |
| 147 | |
| 148 | {{{ |
| 149 | 1. ... NN |
| 150 | 2. ... |
| 151 | }}} |
| 152 | |
| 153 | === Details === |
| 154 | |
| 155 | * Number of eligible voters: NNN |
| 156 | * Cast votes: NNN |
| 157 | |
| 158 | ==== Helios voting system ==== |
| 159 | |
| 160 | * Uploaded eligible voters file''' xxx bytes, at DD MM YYYY: done processing: NNN voters loaded |
| 161 | * Trustee fingerprint and Audit information |
| 162 | |
| 163 | |
| 164 | ==== Technicalities ==== |
| 165 | |
| 166 | The entire election process is encrypted. The CRO, being |
| 167 | the administrator of this "private" election, can only verify which of |
| 168 | the invited members did vote. |
| 169 | |
| 170 | * The election URL: https://vote.heliosvoting.org/helios/e/GRASS-GIS-PSC-2020 |
| 171 | * Election Fingerprint: `xxxxxxxxxxx` |
| 172 | |
| 173 | ===== Ballots ===== |
| 174 | |
| 175 | Helios' voting system features "Audited Ballots". More information at: |
| 176 | |
| 177 | https://vote.heliosvoting.org/helios/elections/TODO/audited-ballots/ |
| 178 | |
| 179 | |
| 180 | ===== Election tally ===== |
| 181 | |
| 182 | Even more, anyone should be able to verify the election tally at "Helios |
| 183 | Election Verifier": |
| 184 | |
| 185 | https://vote.heliosvoting.org/verifier/verify.html?election_url=/helios/elections/TODO |
| 186 | |
| 187 | |
| 188 | ===== Trustee ===== |
| 189 | |
| 190 | Trustees are responsible for decrypting the election result. Each |
| 191 | trustee generates a keypair and submits the public portion to Helios. |
| 192 | When it's time to decrypt, each trustee needs to provide their secret |
| 193 | key. |
| 194 | |
| 195 | For this election, however, the automatically selected, by the system, |
| 196 | trustee was selected and no other persons where involved in this |
| 197 | process. |
| 198 | |
| 199 | * Trustee #`1`: Helios Voting Administrator |
| 200 | * Public Key Fingerprint: `xxxxxxxxxx` |
| 201 | |
| 202 | |
| 203 | == Archived Material & Notes == |
| 204 | |
| 205 | === CRO === |
| 206 | |
| 207 | * TDB |
| 208 | |
| 209 | === Tentative schedule === |
| 210 | |
| 211 | * ... |
| 212 | |
| 213 | === Proposals === |
| 214 | |
| 215 | * Missing in 2016, to be added to election procedure: candidacy period between nominations and voting |
| 216 | |
| 217 | === Comments from 2016 === |
| 218 | |
| 219 | ==== Before the election ==== |
| 220 | |
| 221 | On Fri, Jun 3, 2016 at 2:02 PM, Moritz Lennert wrote: |
| 222 | > So, to summarize, my proposal would be: |
| 223 | > |
| 224 | > - Election of the entire PSC every three years |
| 225 | > - All people with SVN access have the right to vote |
| 226 | > - Elections are announced on grass-dev and grass-user with a clear |
| 227 | > definition of procedure: |
| 228 | > - Anyone (or anyone with voting right ?) can nominate someone during |
| 229 | > a period of a few (4?) weeks |
| 230 | > - Possibly: those who are already in the PSC and stand for elections |
| 231 | > again do not need a nomination / can nominate themselves ? |
| 232 | > - Voting during 1 week |
| 233 | > - The ten candidates with the most votes make up the new PSC |
| 234 | > |
| 235 | > Moritz |
| 236 | |
| 237 | ==== After the election ==== |
| 238 | |
| 239 | nik at nikosalexandris.net Mon Aug 29 08:26:23 PDT 2016 |
| 240 | |
| 241 | >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?" |
| 242 | > |
| 243 | >Some of the candidates went a bit deeper in presenting themselves. Others were less lengthy in their writing. All good. |
| 244 | > |
| 245 | >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?". |
| 246 | |