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?
2. Now that we are talking about lists of names, at least in EU we have
to follow GDPR. We should add somewhere a note stating that names are
going to be stored and shown, and also describing how. Perhaps this is
already considered?
/H.
_______________________________________________
grass-psc mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-psc
