[GRASS-PSC] PSC elections

[Moritz Lennert]

Am 14. Dezember 2020 13:54:35 MEZ schrieb "Chief Return Officer (CRO) - GRASS GIS election 2020" <variablestarlight at gmail.com>:
>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 
>>>>> (<mlennert at club.worldonline.be 
>>>>> <mailto:mlennert at club.worldonline.be>>) escribió:
>>>>>
>>>>>
>>>>>     Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler
>>>>>     <neteler at osgeo.org <mailto:neteler at osgeo.org>>:
>>>>>     >On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
>>>>>     ><variablestarlight at gmail.com
>>>>>     <mailto:variablestarlight at gmail.com>> 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://github.com/OSGeo/grass/blob/master/contributors.csv
>>> https://github.com/OSGeo/grass/blob/master/contributors_extra.csv
>>> https://github.com/OSGeo/grass/blob/master/translators.csv
>>>
>>> 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.

Moritz