Re: [GRASS-PSC] PSC elections

[Luca Delucchi]

On Wed, 13 Jan 2021 at 23:26, Markus Neteler  wrote:
>
> Hi Luca,
>
Hi Markus,

>
> Could you please update it?
>

done, some email addresses are missing, but I didn't find them.

> thanks
> Markus

-- 
ciao
Luca

www.lucadelu.org
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Chief Return Officer (CRO) - GRASS GIS election 2020]

On 2021-01-13 23:55, Markus Neteler wrote:

Dear CRO, all,

On Sun, Dec 13, 2020 at 8:36 PM Markus Neteler  wrote:

On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
 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?

I believe that we should also recognize other contributions
(documentation, translation etc).

Update:
Here an easy way to extract the contributors along with their email address:

git shortlog --summary --numbered --email

(those few with @users.noreply.github.com I can likely find out)

To be run in core, addons etc.

OK. Thanks for that. I have not yet sat down to compile all these lists. 
The LimeSurvey system seems to be very feature-rich. I need to look a 
bit deeper into that.


/H.

___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Markus Neteler]

Dear CRO, all,

On Sun, Dec 13, 2020 at 8:36 PM Markus Neteler  wrote:
>
> On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
>  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?
>
> I believe that we should also recognize other contributions
> (documentation, translation etc).

Update:
Here an easy way to extract the contributors along with their email address:

git shortlog --summary --numbered --email

(those few with @users.noreply.github.com I can likely find out)

To be run in core, addons etc.

cheers,
Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Markus Neteler]

Hi Luca,

On Tue, Dec 15, 2020 at 3:32 PM Luca Delucchi  wrote:
> On Tue, 15 Dec 2020 at 15:28, Markus Neteler  wrote:
>
> > while this one is less maintained due to the separate Transifex portal:
> > https://github.com/OSGeo/grass/blob/master/translators.csv
> >
>
> I can update this file in the next days

Could you please update it?

thanks
Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Luca Delucchi]

On Tue, 15 Dec 2020 at 15:28, Markus Neteler  wrote:
>
> Hi,
>

Hi,


> while this one is less maintained due to the separate Transifex portal:
> https://github.com/OSGeo/grass/blob/master/translators.csv
>

I can update this file in the next days

-- 
ciao
Luca

www.lucadelu.org
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Markus Neteler]

Hi,

On Mon, Dec 14, 2020 at 12:43 PM Moritz Lennert
 wrote:
> On 14/12/20 09:44, Chief Return Officer (CRO) - GRASS GIS election 2020
> > On 2020-12-13 23:12, Veronica Andreo wrote:
> >> El dom, 13 dic 2020 a las 21:19, Moritz Lennert
> > 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 ?

I keep these two up to date to my best knowledge:
https://github.com/OSGeo/grass/blob/master/contributors.csv
https://github.com/OSGeo/grass/blob/master/contributors_extra.csv

while this one is less maintained due to the separate Transifex portal:
https://github.com/OSGeo/grass/blob/master/translators.csv

> For github PR contributors, maybe the tool MarkusN mentioned could help
> getting a list from github.

Shall we try it?

> >
> > 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?
>
> We do not add anything to the three lists above, and they are already
> public, so I don't think we have to worry about that too much.
>
> Indepently of the election, in the context of GDPR we maybe have to send
> a mail to all mailing lists reminding people that these lists exist and
> that they can inform us if they want to be taken off. I'm really no GPDR
> expert, though.

I dunno: it is part of the procedure to be listed there (means: not a surprise).
If anyone wants to take over the management of the CSV lists
(with/-out the full GDPR package) I'd be quite happy :-)

Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Moritz Lennert]

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  On Behalf Of Chief 
Return Officer (CRO) - GRASS GIS election 2020

Sent: tirsdag 15. desember 2020 09:49
To: Moritz Lennert ; Chief Return 
Officer (CRO) - GRASS GIS election 2020 ; 
Veronica Andreo 

Cc: GRASS-PSC 
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" :

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
(mailto:mlenn...@club.worldonline.be>>) escribió:


      Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler
      mailto:nete...@osgeo.org>>:
      >On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
      >mailto:variablestarli...@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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
ithub.com%2FOSGeo%2Fgrass%2Fblob%2Fmaster%2Fcontributors.csvda
ta=04%7C01%7C%7Cd7318f12a9ad47e509dc08d8a0d63ecb%7C6cef373021314901
831055b3abf02c73%7C0%7C0%7C637436189351755609%7CUnknown%7CTWFpbGZsb
3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%
3D%7C1000sdata=pKJvagwBcTG2WHBfcvp8Pfsa6aLV7CvGArVyH7IL%2FZg%3
Dreserved=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%7C1000sdata=TXSRSjbH1fYlNEhZ%2BXam8DaJHut3x87OMCUGVCd
GVx0%3Dreserved=0
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
ithub.com%2FOSGeo%2Fgrass%2Fblob%2Fmaster%2Ftranslators.csvdat
a=04%7C01%7C%7Cd7318f12a9ad47e509dc08d8a0d63ecb%7C6c

Re: [GRASS-PSC] PSC elections

[Chief Return Officer (CRO) - GRASS GIS election 2020]

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  On Behalf Of Chief Return 
Officer (CRO) - GRASS GIS election 2020
Sent: tirsdag 15. desember 2020 09:49
To: Moritz Lennert ; Chief Return Officer (CRO) - GRASS GIS 
election 2020 ; Veronica Andreo 
Cc: GRASS-PSC 
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" :

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
(mailto:mlenn...@club.worldonline.be>>) escribió:


      Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler
      mailto:nete...@osgeo.org>>:
      >On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
      >mailto:variablestarli...@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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
ithub.com%2FOSGeo%2Fgrass%2Fblob%2Fmaster%2Fcontributors.csvda
ta=04%7C01%7C%7Cd7318f12a9ad47e509dc08d8a0d63ecb%7C6cef373021314901
831055b3abf02c73%7C0%7C0%7C637436189351755609%7CUnknown%7CTWFpbGZsb
3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%
3D%7C1000sdata=pKJvagwBcTG2WHBfcvp8Pfsa6aLV7CvGArVyH7IL%2FZg%3
Dreserved=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%7C1000sdata=TXSRSjbH1fYlNEhZ%2BXam8DaJHut3x87OMCUGVCd
GVx0%3Dreserved=0
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
ithub.com%2FOSGeo%2Fgrass%2Fblob%2Fmaster%2Ftranslators.csvdat
a=04%7C01%7C%7Cd7318f12a9ad47e509dc08d8a0d63ecb%7C6cef3730213149018
31055b3abf02c73%7C0%7C0%7C637436189351765565%7CUnknown%7CTWFpbGZsb3
d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
D%7C1000sdata=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 

Re: [GRASS-PSC] PSC elections

[Stefan Blumentrath]

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  On Behalf Of Chief Return 
Officer (CRO) - GRASS GIS election 2020
Sent: tirsdag 15. desember 2020 09:49
To: Moritz Lennert ; Chief Return Officer (CRO) - 
GRASS GIS election 2020 ; Veronica Andreo 

Cc: GRASS-PSC 
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" :
>> 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 
>>>>>> (>>>>> <mailto:mlenn...@club.worldonline.be>>) escribió:
>>>>>>
>>>>>>
>>>>>>      Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler
>>>>>>      mailto:nete...@osgeo.org>>:
>>>>>>      >On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
>>>>>>      >>>>>>      <mailto:variablestarli...@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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
>>>> ithub.com%2FOSGeo%2Fgrass%2Fblob%2Fmaster%2Fcontributors.csvda
>>>> ta=04%7C01%7C%7Cd7318f12a9ad47e509dc08d8a0d63ecb%7C6cef373021314901
>>>> 831055b3abf02c73%7C0%7C0%7C637436189351755609%7CUnknown%7CTWFpbGZsb
>>>> 3d8eyJWIjoiMC4wLjAwMDAiLCJQI

Re: [GRASS-PSC] PSC elections

[Chief Return Officer (CRO) - GRASS GIS election 2020]

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" :

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
(mailto:mlenn...@club.worldonline.be>>) escribió:


     Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler
     mailto:nete...@osgeo.org>>:
     >On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
     >mailto:variablestarli...@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.


OK. An no other complaints received. So I guess we can proceed then.

/H.


___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Moritz Lennert]

Am 14. Dezember 2020 13:54:35 MEZ schrieb "Chief Return Officer (CRO) - GRASS 
GIS election 2020" :
>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 
> ( >) escribió:
>
>
>     Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler
>     mailto:nete...@osgeo.org>>:
>     >On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
>     >     > 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
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Chief Return Officer (CRO) - GRASS GIS election 2020]

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 
(>) escribió:



    Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler
    mailto:nete...@osgeo.org>>:
    >On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
    >mailto:variablestarli...@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.

/H.

PS. this email should have been sent one hour ago, but I was affected by 
the google global crash of today. No it seems to work fine.


___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Moritz Lennert]

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 
(>) escribió:



    Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler
    mailto:nete...@osgeo.org>>:
    >On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
    >mailto:variablestarli...@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 ?


Moritz
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Moritz Lennert]

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 
(mailto:mlenn...@club.worldonline.be>>) 
escribió:



Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler
mailto:nete...@osgeo.org>>:
>On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
>mailto:variablestarli...@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.




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?


We do not add anything to the three lists above, and they are already 
public, so I don't think we have to worry about that too much.


Indepently of the election, in the context of GDPR we maybe have to send 
a mail to all mailing lists reminding people that these lists exist and 
that they can inform us if they want to be taken off. I'm really no GPDR 
expert, though.


Moritz
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Chief Return Officer (CRO) - GRASS GIS election 2020]

On 2020-12-13 23:12, Veronica Andreo wrote:

Hi everyone,

El dom, 13 dic 2020 a las 21:19, Moritz Lennert 
(mailto:mlenn...@club.worldonline.be>>) 
escribió:



Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler
mailto:nete...@osgeo.org>>:
>On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
>mailto:variablestarli...@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?


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
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Veronica Andreo]

Hi everyone,

El dom, 13 dic 2020 a las 21:19, Moritz Lennert (<
mlenn...@club.worldonline.be>) escribió:

>
> Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler <
> nete...@osgeo.org>:
> >On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
> > 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!

I've been searching in Transifex, and found this:
https://www.transifex.com/grass-gis/teams/. But, I'm not sure which number
really represents those that have actually translated strings and most
importantly how to easily get such a list.

What about those Google Code-In students that have contributed with
screenshots and examples to manual pages, as well as those contributing
tests?

cheers,
Vero
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Moritz Lennert]

Am 13. Dezember 2020 20:36:05 MEZ schrieb Markus Neteler :
>On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
> 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.

>
>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.

How does that sound?




>
>Does anyone know this tool for the identification of contributors (I
>never tried)
>https://allcontributors.org/

Sounds interesting, but probably only for github, or ? So not Transifex.

Moritz
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Markus Neteler]

On Sun, Dec 13, 2020 at 7:38 PM Hernán De Angelis
 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?

I believe that we should also recognize other contributions
(documentation, translation etc).

Does anyone know this tool for the identification of contributors (I
never tried)
https://allcontributors.org/

?

Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Hernán De Angelis]

Hi again,

In the wiki, eligible voters are defined as those with svn access. This 
is perhaps outdated? In 2020 it should perhaps be those who can merge a 
pull request in GitHub? Or should we choose another definition?


/H.

On 2020-12-13 19:28, Markus Neteler wrote:

Dear all,

Moritz Lennert > schrieb am So., 13. Dez. 2020, 
19:25:


...

In 2016 [1] we had a four week nomination period of which the last
week was used to give candidates the opportunity to reevaluate if
they really want to stand for elections. Then a one week period
for the vote. So depending on when you can announce, this will
mean mid-December to mid-January for nomination and then a week
end of January for the vote.


We also need to define, perhaps in a better way than in 2016, who's 
eligible to vote.


Markus




[1] https://trac.osgeo.org/grass/wiki/PSC/Election2016

___
grass-psc mailing list
grass-psc@lists.osgeo.org 
https://lists.osgeo.org/mailman/listinfo/grass-psc


___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Hernán De Angelis]

Hi Moritz,

Fine, a request for an OSGEO UserId is on its way. I have no idea how 
long this will take. Hope not long.


Moritz, your preliminary schedule proposal sounds fine to me. I can 
start editing the wiki as soon I get an UserId.


/H.

On 2020-12-13 19:24, Moritz Lennert wrote:

Hi Hernán,

Am 13. Dezember 2020 18:41:02 MEZ schrieb "Hernán De Angelis" 
:

Dear Nikos,

Thank you for your message and considerations. I believe I understand
the basis of this process.

It seems that we will need to update the 2020 Election wiki
 before we start.
How do we proceed with that?

If you don't have one already, you need an OSGeo User ID to log in:

https://www.osgeo.org/community/getting-started-osgeo/osgeo_userid/

While waiting for that, you should begin by defining the calendar (also based 
on your possible constraints).

In 2016 [1] we had a four week nomination period of which the last week was 
used to give candidates the opportunity to reevaluate if they really want to 
stand for elections. Then a one week period for the vote. So depending on when 
you can announce, this will mean mid-December to mid-January for nomination and 
then a week end of January for the vote.

Moritz


[1] https://trac.osgeo.org/grass/wiki/PSC/Election2016

___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Markus Neteler]

Dear all,

Moritz Lennert  schrieb am So., 13. Dez.
2020, 19:25:

> ...
>
> In 2016 [1] we had a four week nomination period of which the last week
> was used to give candidates the opportunity to reevaluate if they really
> want to stand for elections. Then a one week period for the vote. So
> depending on when you can announce, this will mean mid-December to
> mid-January for nomination and then a week end of January for the vote.
>

We also need to define, perhaps in a better way than in 2016, who's
eligible to vote.

Markus



>
> [1] https://trac.osgeo.org/grass/wiki/PSC/Election2016
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
>
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Moritz Lennert]

Hi Hernán,

Am 13. Dezember 2020 18:41:02 MEZ schrieb "Hernán De Angelis" 
:
>Dear Nikos,
>
>Thank you for your message and considerations. I believe I understand 
>the basis of this process.
>
>It seems that we will need to update the 2020 Election wiki 
> before we start. 
>How do we proceed with that?

If you don't have one already, you need an OSGeo User ID to log in:

https://www.osgeo.org/community/getting-started-osgeo/osgeo_userid/

While waiting for that, you should begin by defining the calendar (also based 
on your possible constraints).

In 2016 [1] we had a four week nomination period of which the last week was 
used to give candidates the opportunity to reevaluate if they really want to 
stand for elections. Then a one week period for the vote. So depending on when 
you can announce, this will mean mid-December to mid-January for nomination and 
then a week end of January for the vote.

Moritz


[1] https://trac.osgeo.org/grass/wiki/PSC/Election2016
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Hernán De Angelis]

Dear Nikos,

Thank you for your message and considerations. I believe I understand 
the basis of this process.


It seems that we will need to update the 2020 Election wiki 
 before we start. 
How do we proceed with that?


Best

Hernán


On 2020-12-13 17:42, n...@nikosalexandris.net wrote:

Dear Hernán,

Congratulations for taking over this important role.
I think Moritz already shared the link(s) to notes of the last election.

Allow me please to share the following thoughts.

Elections are a corner-stone for any project and they should be given 
the attention they deserve. 'GRASS GIS' is a somewhat compact group 
and this helps often to get things done. Nevertheless, giving value 
and transparency to the elections, and the PSC itself, can only 
support the project's growth.


I would:

- try to inform and activate the community for participation.
- repeat and clarify the rules to the community with short messages, 
obviously without becoming invasive. --  We all forget and some will 
post, for example, their nomination directly to the list and not to 
the CRO.
- invite community members to explain why they nominate someone for 
the PSC
- invite nominees for 'self-defense': why does someone want to be a 
member of the PSC?


Wishes for a fruitful election procedure.
Kind regards, Nikos
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[nik]

Dear Hernán,

Congratulations for taking over this important role.
I think Moritz already shared the link(s) to notes of the last election.

Allow me please to share the following thoughts.

Elections are a corner-stone for any project and they should be given 
the attention they deserve. 'GRASS GIS' is a somewhat compact group and 
this helps often to get things done. Nevertheless, giving value and 
transparency to the elections, and the PSC itself, can only support the 
project's growth.


I would:

- try to inform and activate the community for participation.
- repeat and clarify the rules to the community with short messages, 
obviously without becoming invasive. --  We all forget and some will 
post, for example, their nomination directly to the list and not to the 
CRO.
- invite community members to explain why they nominate someone for the 
PSC
- invite nominees for 'self-defense': why does someone want to be a 
member of the PSC?


Wishes for a fruitful election procedure.
Kind regards, Nikos
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Markus Neteler]

On Fri, Dec 11, 2020 at 11:08 AM Moritz Lennert
 wrote:
>
> Dear Hernán,
>
> Thanks for accepting the role as CRO ! We will obviously support you in 
> whatever ways necessary.

Thanks, Hernán!

> The first step would now be to define a calendar and to update the wiki page.
>
> @MarkusN, do we have a dedicated email address for the CRO ?

Now yes: 
(https://trac.osgeo.org/osgeo/ticket/2540)

This is just an email reflector (alias), not a mailbox!
It currently points to Hernán's email address, test email sent.

> @Nikos, as you were the CRO at the last election, maybe you have some advice 
> for Hernán ?

Hi Nikos, your insights are welcome.

Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections

[Hernán De Angelis]

Thank you Moritz,

I have now subscribed to the psc list as well.

/H.

On 2020-12-11 11:08, Moritz Lennert wrote:

Dear Hernán,

Thanks for accepting the role as CRO ! We will obviously support you in 
whatever ways necessary.

The first step would now be to define a calendar and to update the wiki page.

@MarkusN, do we have a dedicated email address for the CRO ?

@Nikos, as you were the CRO at the last election, maybe you have some advice 
for Hernán ?

Moritz

___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] PSC elections

[Moritz Lennert]

Dear Hernán,

Thanks for accepting the role as CRO ! We will obviously support you in 
whatever ways necessary.

The first step would now be to define a calendar and to update the wiki page.

@MarkusN, do we have a dedicated email address for the CRO ?

@Nikos, as you were the CRO at the last election, maybe you have some advice 
for Hernán ?

Moritz
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections in 2020

[Helena Mitasova]

Moritz, 

the proposed email looks good. Preferably CRO should not be a PSC member (but 
could be a former member)
I wish the process was much simpler, but I don’t have any good ideas about how 
to simplify it,

Helena
  
> On Dec 8, 2020, at 9:03 AM, Moritz Lennert  
> wrote:
> 
> On 7/12/20 21:28, Markus Neteler wrote:
>> Dear PSC,
>> 
>> Almost a year has passed...
>> 
>> On Wed, Dec 11, 2019 at 12:08 AM Markus Neteler  wrote:
>>> Hi PSC,
>>> 
>>> I have drafted a page for the needed PSC elections:
>>> https://trac.osgeo.org/grass/wiki/PSC/Election2020
>>> 
>>> All details yet to be defined.
>> I would like to re-suggest discussing the next PSC election.
> 
> +1
> 
> First step would probably be to find a CRO. Doesn't have to part of the 
> current PSC, or ? So we should ask on the -dev and probably also the -user 
> list for candidates. Any objections to me sending the following mail to both 
> lists ?
> 
> Moritz
> 
> 
> 
> 
> 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 [1]. Although most decisions are taken by 
> consensus via the developers mailing list 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). For an 
> overview of the (fairly low-noise) activity of the PSC, you can browse 
> through the archives of its public mailing list [2]. 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.
> 
> 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 [3]. The first step in that 
> procedure is the nomination of one (or several) Chief Return Officers who 
> will oversee the election process.
> 
> Is anyone willing to play this role ? You can just respond directly here on 
> the list to display your interest.
> 
> The current PSC
> 
> ***
> 
> [1] https://trac.osgeo.org/grass/wiki/PSC 
> 
> 
> [2] https://lists.osgeo.org/pipermail/grass-psc/ 
> 
> 
> [3] https://trac.osgeo.org/grass/wiki/PSC/Election2020
> 
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc

Helena Mitasova
Professor at the Department of Marine, 
Earth, and Atmospheric Sciences
Associate director and faculty fellow at the Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu

"All electronic mail messages in connection with State business which are sent 
to or received by this account are subject to the NC Public Records Law and may 
be disclosed to third parties.” 

___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections in 2020

[Moritz Lennert]

On 7/12/20 21:28, Markus Neteler wrote:

Dear PSC,

Almost a year has passed...

On Wed, Dec 11, 2019 at 12:08 AM Markus Neteler  wrote:

Hi PSC,

I have drafted a page for the needed PSC elections:
https://trac.osgeo.org/grass/wiki/PSC/Election2020

All details yet to be defined.

I would like to re-suggest discussing the next PSC election.


+1

First step would probably be to find a CRO. Doesn't have to part of the 
current PSC, or ? So we should ask on the -dev and probably also the 
-user list for candidates. Any objections to me sending the following 
mail to both lists ?


Moritz




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 [1]. Although most decisions are taken by 
consensus via the developers mailing list 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). For an overview of the (fairly low-noise) activity of 
the PSC, you can browse through the archives of its public mailing list 
[2]. 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.


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 [3]. The 
first step in that procedure is the nomination of one (or several) Chief 
Return Officers who will oversee the election process.


Is anyone willing to play this role ? You can just respond directly here 
on the list to display your interest.


The current PSC

***

[1] https://trac.osgeo.org/grass/wiki/PSC 



[2] https://lists.osgeo.org/pipermail/grass-psc/ 



[3] https://trac.osgeo.org/grass/wiki/PSC/Election2020

___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC elections in 2020

[Markus Neteler]

Dear PSC,

Almost a year has passed...

On Wed, Dec 11, 2019 at 12:08 AM Markus Neteler  wrote:
>
> Hi PSC,
>
> I have drafted a page for the needed PSC elections:
> https://trac.osgeo.org/grass/wiki/PSC/Election2020
>
> All details yet to be defined.

I would like to re-suggest discussing the next PSC election.

Best,
Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] PSC elections in 2020

[Markus Neteler]

Hi PSC,

I have drafted a page for the needed PSC elections:
https://trac.osgeo.org/grass/wiki/PSC/Election2020

All details yet to be defined.

Best
Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc