Great, thanks a lot !
I'll wait until tomorrow to see if anyone else from other time zones
wants to volunteer and cooperate with you. Then we can launch the process.
Moritz
On 10/12/20 12:48, Hernán De Angelis wrote:
Hi again Moritz,
Thank you for the information. I will gladly volunteer for the role.
It will be nice to give back to this community.
Best regards
Hernán
On 2020-12-10 12:10, Moritz Lennert wrote:
Hi Hernán,
Am 10.12.2020 09:25 schrieb Hernán De Angelis:
Hi Moritz
I can think of contributing as a CRO provided I can better understand
what the role is about and what is expected.
I see some info here:
https://trac.osgeo.org/grass/wiki/PSC/Election2020
Is there something else to read?
Actually no. We're a community that has worked very well on a fairly
informal level for years, so there is not much in terms of written
rules or laws, so this page is the closest we have to a voting procedure.
Basically the tasks are:
- Announce elections and election procedures
- Receive nominations and confirmation from candidates that they
accept to be nominated
- Fill out the list of nominees on the wiki page
- Collect some info from the candidates and put it on the wiki page
(see at the very end of the page the suggestion, i.e. ask each
candidate to respond to the question "What should the community
expect from your PSC membership?")
- organize the election (configure vote on
https://vote.heliosvoting.org/, launch vote, launch reminder, tally
votes)
- announce results
- deal with any complaints (I doubt that there will be any)
I hope this provides you with what you need to decide. If not, don't
hesitate to come back to me.
Moritz
On 2020-12-10 09:14, Moritz Lennert wrote:
Dear all,
As part of the effort to guarantee a solid and sustainable
governance of GRASS GIS development, and in accordance with OSGeo
guidelines, we have a Project Steering Committee (PSC) [1]. Although
most decisions are taken by consensus via the mailing lists or via
discussions in github issues, some decisions go through this
committee: annual budget, admission of new developers into the core
development team, and some fundamental decisions (recent example:
phasing out of a 32-bit version for MS Windows).
The last election for this committee was in 2016 and at the time we
decided that the PSC should be renewed approximately every 3 years.
We are already beyond this time frame and so a new election should
happen, soon. The general outline of the procedure has been drafted
[2].
The first step in that procedure is the nomination of one (or
several) Chief Return Officer(s) (CRO) who will oversee the election
process and who should not be a member of the current PSC, nor aim
at becoming a member of the new PSC.
Is anyone willing to play this role ? You can just respond directly
here on the list to display your interest.
In a second step, we will be looking for candidates for the new PSC.
For an overview of the (fairly low-noise) activity of the PSC, you
can browse through the archives of its public mailing list [3]. You
will see that it is not a job that requires a lot of work, but it is
an essential job nevertheless. Also: no need to be a developer to be
part of the PSC, users should also be represented.
On behalf of the current PSC,
Moritz
[1] https://trac.osgeo.org/grass/wiki/PSC
<https://trac.osgeo.org/grass/wiki/PSC>
[2] https://trac.osgeo.org/grass/wiki/PSC/Election2020
[3] https://lists.osgeo.org/pipermail/grass-psc/
_______________________________________________
grass-user mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-user
_______________________________________________
grass-psc mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-psc
