Hi,
We had exactly the same debate last time (see the threads starting at
[1] and [2]). Although in theory I see the issue, as I already said at
the time I do think that in practice our community is sufficiently small
and stable for this not to be a problem in reality.
But if someone feels otherwise and wants to propose an RFC [3] on
election procedures including a system with different time frames for
mandates, please feel free.
Moritz
[1] https://lists.osgeo.org/pipermail/grass-psc/2016-May/001477.html
[2] https://lists.osgeo.org/pipermail/grass-psc/2016-June/001488.html
[3] https://trac.osgeo.org/grass/wiki/RFC
On 15/12/20 10:15, Chief Return Officer (CRO) - GRASS GIS election 2020
wrote:
I should perhaps leave this to the more experienced members, but I
believe it is a good thing to strike a balance between continuity and
renewal.
/H.
On 2020-12-15 10:04, Stefan Blumentrath wrote:
Just a little suggestion to consider for the process. Maybe it is
worth thinking about not to put the entire PSC on election every time?
If e.g. only half of the PSC is put up for election every second or
third year (meaning for 4 to 6 years periods) that might secure
continuity. That is no concern I guess right now, but it could in
theory be an advantage to avoid a hypothetical scenario where the
entire PSC gets changed....
Cheers
Stefan
-----Original Message-----
From: grass-psc <[email protected]> On Behalf Of Chief
Return Officer (CRO) - GRASS GIS election 2020
Sent: tirsdag 15. desember 2020 09:49
To: Moritz Lennert <[email protected]>; Chief Return
Officer (CRO) - GRASS GIS election 2020 <[email protected]>;
Veronica Andreo <[email protected]>
Cc: GRASS-PSC <[email protected]>
Subject: Re: [GRASS-PSC] PSC elections
On 2020-12-14 23:57, Moritz Lennert wrote:
Am 14. Dezember 2020 13:54:35 MEZ schrieb "Chief Return Officer (CRO)
- GRASS GIS election 2020" <[email protected]>:
On 2020-12-14 12:45, Moritz Lennert wrote:
On 14/12/20 12:43, Moritz Lennert wrote:
On 14/12/20 09:44, Chief Return Officer (CRO) - GRASS GIS election
2020 wrote:
On 2020-12-13 23:12, Veronica Andreo wrote:
Hi everyone,
El dom, 13 dic 2020 a las 21:19, Moritz Lennert
(<[email protected]
<mailto:[email protected]>>) escribió:
Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler
<[email protected] <mailto:[email protected]>>:
>On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
><[email protected]
<mailto:[email protected]>> wrote:
>>
>> Hi again,
>>
>> In the wiki, eligible voters are defined as those with
svn
access. This is perhaps outdated?
>
>Yes, that's definitely outdated.
>
>> In 2020 it should perhaps be those who can merge a pull
request
in GitHub? Or should we choose another definition?
Only merge rights (i.e. write access to the grass
repository)
seems very restrictive in current github PR times.
Fully agreed! Last time, all of us in the contributors and
contributors_extra files were given voting rights. We could also
consider those in translators.csv. I don't remember if they were
considered last time. I believe they were not.
>I believe that we should also recognize other contributions
>(documentation, translation etc).
How to define this, though. In my eyes we should be as
inclusive
as reasonable.
Maybe we could say:
- All people with write access to any of the GRASS GIS
repositories (i.e for example also including add-ons and
website).
- All people that have already posted a pull request to
github
(possibly only those PR that have been merged)
- All people that have contributed to Transifex.
+1!
+1 to this too
A couple of related questions:
1. is there any easily accessible/searchable list over people who
have the right to vote? How it is supposed the CRO will check this?
The three files that Vero mentioned are all in the root of the
github
repository:
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
ithub.com%2FOSGeo%2Fgrass%2Fblob%2Fmaster%2Fcontributors.csv&da
ta=04%7C01%7C%7Cd7318f12a9ad47e509dc08d8a0d63ecb%7C6cef373021314901
831055b3abf02c73%7C0%7C0%7C637436189351755609%7CUnknown%7CTWFpbGZsb
3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%
3D%7C1000&sdata=pKJvagwBcTG2WHBfcvp8Pfsa6aLV7CvGArVyH7IL%2FZg%3
D&reserved=0
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
ithub.com%2FOSGeo%2Fgrass%2Fblob%2Fmaster%2Fcontributors_extra.csv&
amp;data=04%7C01%7C%7Cd7318f12a9ad47e509dc08d8a0d63ecb%7C6cef373021
314901831055b3abf02c73%7C0%7C0%7C637436189351765565%7CUnknown%7CTWF
pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC
I6Mn0%3D%7C1000&sdata=TXSRSjbH1fYlNEhZ%2BXam8DaJHut3x87OMCUGVCd
GVx0%3D&reserved=0
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
ithub.com%2FOSGeo%2Fgrass%2Fblob%2Fmaster%2Ftranslators.csv&dat
a=04%7C01%7C%7Cd7318f12a9ad47e509dc08d8a0d63ecb%7C6cef3730213149018
31055b3abf02c73%7C0%7C0%7C637436189351765565%7CUnknown%7CTWFpbGZsb3
d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
D%7C1000&sdata=0xfPIG0KqTdFfNT2BEEgrflaxwbyT7%2BOEMXUipJEZq0%3D
&reserved=0
I don't know if there are many contributors of pull requests via
github that are not in those files, same for translators that might
be active on Transifex, but not in the relevant list.
@MarkusN what is the status of these lists ?
For github PR contributors, maybe the tool MarkusN mentioned could
help getting a list from github.
Maybe we can start with an email to all mailing lists, informing
everyone that we consider these three files as our "electoral
registry" and that if anyone feels she or he should be in one of
these files, that they send a mail to the respective list informing
us ?
I can do this at once if no one opposes.
Non objection from my side.
OK. An no other complaints received. So I guess we can proceed then.
/H.
_______________________________________________
grass-psc mailing list
[email protected]
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Fgrass-psc&data=04%7C01%7C%7Cd7318f12a9ad47e509dc08d8a0d63ecb%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637436189351765565%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=IWk2NiXZVBNMlcZfaBefQOQLKxArXVPbi%2FYbkda4NG8%3D&reserved=0
_______________________________________________
grass-psc mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-psc
