<html style="direction: ltr;">
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body smarttemplateinserted="true" bgcolor="#FFFFFF" text="#000000">
<div id="smartTemplate4-template">
<div id="my_message" style="color:blue; "> Congrads to the members
of the new PSC. <br>
<p> The community as a whole can rest assured that further
development of GRASS will stay on track.<br>
</p>
</div>
</div>
<div id="smartTemplate4-quoteHeader">------ Original Message ------
Subject: [GRASS-user] Results of GRASS-GIS' PSC-2016 Election
Date: Mon, 29 Aug 2016 17:26:23 +0200
To: Grass-psc, Grass-user, Grass-dev
From: Nikos Alexandris</div>
<blockquote
cite="mid:20160829152623.GH31777@mail.nikosalexandris.net"
type="cite">Dear GRASS GIS community,
<br>
<br>
the new Project Steering Committee is composed by the following
nine
<br>
members:
<br>
<br>
1 Markus Neteler 62
<br>
2 Helena Mitasova 53
<br>
3 Martin Landa 52
<br>
4 Anna Petrasova 45
<br>
5 Moritz Lennert 41
<br>
6 Margherita Di Leo 39
<br>
7 Michael Barton 35
<br>
8 Peter Löwe 33
<br>
9 Vaclav Petras 31
<br>
<br>
Congratulations!
<br>
<br>
<br>
A warm Thank You for their candidacy, and dedication to the
project, goes
<br>
to:
<br>
<br>
- Helmut Kurdnovsky 30
<br>
- Yann Chemin 29
<br>
- Veronica Andreo 28
<br>
- Micha Silver 20
<br>
<br>
<br>
To keep track and for the sake of completeness, all relevant
<br>
communications will be published in one wiki-page (in trac).
<br>
<br>
<br>
<br>
Details
<br>
<br>
* The election URL:
<a class="moz-txt-link-freetext" href="https://vote.heliosvoting.org/helios/e/GRASS-GIS-PSC-2016">https://vote.heliosvoting.org/helios/e/GRASS-GIS-PSC-2016</a> *
Election Fingerprint: es9DDU1oPIxtyV9DE/cl402ctbm5PwaFhmLrruzsAJU
<br>
<br>
Remember, the entire election process was/is encrypted. The CRO,
being
<br>
the administrator of this "private" election, could only verify
which of
<br>
the invited members did vote. That and nothing more.
<br>
<br>
<br>
*Ballots*
<br>
<br>
Helios' voting system features "Audited Ballots". More information
at:
<br>
<br>
<a class="moz-txt-link-freetext" href="https://vote.heliosvoting.org/helios/elections/397c5ce0-67c2-11e6-8e87-3e719e3f8c36/audited-ballots/">https://vote.heliosvoting.org/helios/elections/397c5ce0-67c2-11e6-8e87-3e719e3f8c36/audited-ballots/</a>.
<br>
<br>
<br>
*Election tally*
<br>
<br>
Even more, anyone should be able to verify the election tally at
"Helios
<br>
Election Verifier":
<br>
<br>
<a class="moz-txt-link-freetext" href="https://vote.heliosvoting.org/verifier/verify.html?election_url=/helios/elections/397c5ce0-67c2-11e6-8e87-3e719e3f8c36">https://vote.heliosvoting.org/verifier/verify.html?election_url=/helios/elections/397c5ce0-67c2-11e6-8e87-3e719e3f8c36</a>.
<br>
<br>
<br>
*Trustee*
<br>
<br>
The trustee for this election was:
<br>
<br>
Trustee #1: Helios Voting Administrator
<br>
Public Key Fingerprint:
0mYM9DB3TVWlbURGBXiMnCb12Vsf4OJoFXBODOPl9os
<br>
<br>
Trustees are responsible for decrypting the election result. Each
<br>
trustee generates a keypair and submits the public portion to
Helios.
<br>
When it's time to decrypt, each trustee needs to provide their
secret
<br>
key.
<br>
<br>
For this election, however, the automcatically selected, by the
system,
<br>
trustee was selected and no other persons where involved in this
<br>
process.
<br>
<br>
<br>
*Broken Links?*
<br>
<br>
If any of the links do not lead anywhere, please contact the CRO
<br>
publicly, in example by responding to this post.
<br>
<br>
Voters who casted a ballot, will receive another message sent via
<br>
Helios' directly.
<br>
<br>
For more, there is a FAQ: <a class="moz-txt-link-freetext" href="https://vote.heliosvoting.org/faq">https://vote.heliosvoting.org/faq</a>
<br>
<br>
<br>
<br>
Final words
<br>
<br>
As a CRO, I tried to serve this role as best possible. Looking
back on
<br>
the last few weeks, and having various off-list discussions, while
at
<br>
Bonn last week, I identify and reflect on mistakes and things I
could
<br>
have done better.
<br>
<br>
In time, I will try to collect some of the experiences and compose
a
<br>
wiki-page (in trac). However, I'd like to stress the following:
I feel
<br>
and think that I did not insist as much as I should, to assist in
<br>
profiling better the candidates.
<br>
<br>
There is this important question, asked by Micha Silver end of
July (see
<br>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/pipermail/grass-user/2016-July/074529.html">https://lists.osgeo.org/pipermail/grass-user/2016-July/074529.html</a>),
<br>
"what we should expect from PSC members?"
<br>
<br>
Some of the candidates went a bit deeper in presenting themselves.
<br>
Others were less lengthy in their writing. All good.
<br>
<br>
However, I propose herewith, for the next PSC election, the
following: set as a
<br>
requirement, for each candidate, to answer this very question as
being
<br>
asked from the community: "What should the community expect from
your
<br>
PSC membership?".
<br>
<br>
<br>
Thank you.
<br>
GRASS-GIS' CRO
<br>
<br>
As Nikos, thank you to the previous PSC for accepting me as the
CRO this
<br>
year.
<br>
_______________________________________________
<br>
grass-user mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/grass-user">http://lists.osgeo.org/mailman/listinfo/grass-user</a><br>
</blockquote>
<br>
</body>
</html>