Re: [GRASS-PSC] Announcements to all lists

[Markus Neteler]

On Tue, Dec 15, 2020 at 5:17 PM Moritz Lennert
 wrote:
> Am 15. Dezember 2020 16:14:23 MEZ schrieb Markus Neteler :
> >On Tue, Dec 15, 2020 at 4:12 PM Hernán De Angelis
...
> >Importantly, I whitelisted the CRO email. Perhaps you have sent from
> >your gmail account?
>
> If you still have the same config, i.e. sender = your personal address and 
> reply-to = CRO address it will fail. You have to use the CRO address as 
> sender.

Meanwhile I have whitelisted also the personal email and the emails
went through.

> IIUC, you use Google Mail ? Then here are relevant instructions on how to do 
> that: https://support.google.com/mail/answer/22370?hl=en.
>
> Moritz

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

Re: [GRASS-PSC] Announcements to all lists

[Moritz Lennert]

Am 15. Dezember 2020 16:14:23 MEZ schrieb Markus Neteler :
>On Tue, Dec 15, 2020 at 4:12 PM Hernán De Angelis
> wrote:
>> On 2020-12-15 15:39, Markus Neteler wrote:
>> > On Tue, Dec 15, 2020 at 3:37 PM Chief Return Officer (CRO) - GRASS GIS
>> > election 2020  wrote:
>> > ...
>> >> I mailed this morning to all lists mentioned in
>> >>
>> >> https://grass.osgeo.org/about/community/
>> > Sorry - please do again - they have been silently "eaten" due to the
>> > huge spam load (no way for me to manually go through every day).
>> > Only grass-web arrived which I manually moderate.
>>
>> I re-mailed the announcement a few minutes ago to the dev, stats,
>> translations and announce lists. No signs that it passed yet.
>
>Mh, it should be immediate.
>
>Importantly, I whitelisted the CRO email. Perhaps you have sent from
>your gmail account?

If you still have the same config, i.e. sender = your personal address and 
reply-to = CRO address it will fail. You have to use the CRO address as sender.

IIUC, you use Google Mail ? Then here are relevant instructions on how to do 
that: https://support.google.com/mail/answer/22370?hl=en.

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

Re: [GRASS-PSC] Announcements to all lists

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

On 2020-12-15 16:14, Markus Neteler wrote:

On Tue, Dec 15, 2020 at 4:12 PM Hernán De Angelis
 wrote:

On 2020-12-15 15:39, Markus Neteler wrote:

On Tue, Dec 15, 2020 at 3:37 PM Chief Return Officer (CRO) - GRASS GIS
election 2020  wrote:
...

I mailed this morning to all lists mentioned in

https://grass.osgeo.org/about/community/

Sorry - please do again - they have been silently "eaten" due to the
huge spam load (no way for me to manually go through every day).
Only grass-web arrived which I manually moderate.

I re-mailed the announcement a few minutes ago to the dev, stats,
translations and announce lists. No signs that it passed yet.

Mh, it should be immediate.

Importantly, I whitelisted the CRO email. Perhaps you have sent from
your gmail account?
Shall I whitelist it as well?


Will try again in an hour or so if they do not show up by then.

/H.

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

Re: [GRASS-PSC] Announcements to all lists

[Markus Neteler]

On Tue, Dec 15, 2020 at 4:12 PM Hernán De Angelis
 wrote:
> On 2020-12-15 15:39, Markus Neteler wrote:
> > On Tue, Dec 15, 2020 at 3:37 PM Chief Return Officer (CRO) - GRASS GIS
> > election 2020  wrote:
> > ...
> >> I mailed this morning to all lists mentioned in
> >>
> >> https://grass.osgeo.org/about/community/
> > Sorry - please do again - they have been silently "eaten" due to the
> > huge spam load (no way for me to manually go through every day).
> > Only grass-web arrived which I manually moderate.
>
> I re-mailed the announcement a few minutes ago to the dev, stats,
> translations and announce lists. No signs that it passed yet.

Mh, it should be immediate.

Importantly, I whitelisted the CRO email. Perhaps you have sent from
your gmail account?
Shall I whitelist it as well?

> On the other hand, I already got an OSGEO and can start editing the Trac
> wiki, maybe later today.

Thanks!

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

Re: [GRASS-PSC] Announcements to all lists

[Hernán De Angelis]

On 2020-12-15 15:39, Markus Neteler wrote:

On Tue, Dec 15, 2020 at 3:37 PM Chief Return Officer (CRO) - GRASS GIS
election 2020  wrote:
...

I mailed this morning to all lists mentioned in

https://grass.osgeo.org/about/community/

Sorry - please do again - they have been silently "eaten" due to the
huge spam load (no way for me to manually go through every day).
Only grass-web arrived which I manually moderate.


I re-mailed the announcement a few minutes ago to the dev, stats, 
translations and announce lists. No signs that it passed yet.


On the other hand, I already got an OSGEO and can start editing the Trac 
wiki, maybe later today.


/H.

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

Re: [GRASS-PSC] Announcements to all lists

[Hernán De Angelis]

On 2020-12-15 15:39, Markus Neteler wrote:

On Tue, Dec 15, 2020 at 3:37 PM Chief Return Officer (CRO) - GRASS GIS
election 2020  wrote:
...

I mailed this morning to all lists mentioned in

https://grass.osgeo.org/about/community/

Sorry - please do again - they have been silently "eaten" due to the
huge spam load (no way for me to manually go through every day).
Only grass-web arrived which I manually moderate.


Fine, will do later today.

/H.

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

Re: [GRASS-PSC] Announcements to all lists

[Markus Neteler]

On Tue, Dec 15, 2020 at 3:37 PM Chief Return Officer (CRO) - GRASS GIS
election 2020  wrote:
...
> I mailed this morning to all lists mentioned in
>
> https://grass.osgeo.org/about/community/

Sorry - please do again - they have been silently "eaten" due to the
huge spam load (no way for me to manually go through every day).
Only grass-web arrived which I manually moderate.

> I believe I did not ommit the commit list. Will do in the future.

Fine.

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

Re: [GRASS-PSC] Announcements to all lists

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

On 2020-12-15 15:33, Markus Neteler wrote:

On Tue, Dec 15, 2020 at 3:31 PM Luca Delucchi  wrote:

On Tue, 15 Dec 2020 at 15:24, Markus Neteler  wrote:

Hi,


Hi,


I can easily whitelist "cro.gr...@osgeo.org".
I have done it now for
- grass-user
- grass-dev
- grass-announce
- grass-psc

Any other list needed?

website?
translations?

Right:

also done:
- grass-st...@lists.osgeo.org
- grass-translati...@lists.osgeo.org
- grass-...@lists.osgeo.org

(please do not send here: grass-com...@lists.osgeo.org)


Right, thanks. I mailed this morning to all lists mentioned in

https://grass.osgeo.org/about/community/

I believe I did not ommit the commit list. Will do in the future.

/H.

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

Re: [GRASS-PSC] Announcements to all lists

[Markus Neteler]

On Tue, Dec 15, 2020 at 3:31 PM Luca Delucchi  wrote:
>
> On Tue, 15 Dec 2020 at 15:24, Markus Neteler  wrote:
> >
> > Hi,
> >
>
> Hi,
>
> > I can easily whitelist "cro.gr...@osgeo.org".
> > I have done it now for
> > - grass-user
> > - grass-dev
> > - grass-announce
> > - grass-psc
> >
> > Any other list needed?
>
> website?
> translations?

Right:

also done:
- grass-st...@lists.osgeo.org
- grass-translati...@lists.osgeo.org
- grass-...@lists.osgeo.org

(please do not send here: grass-com...@lists.osgeo.org)

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] Announcements to all lists

[Luca Delucchi]

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

Hi,

> I can easily whitelist "cro.gr...@osgeo.org".
> I have done it now for
> - grass-user
> - grass-dev
> - grass-announce
> - grass-psc
>
> Any other list needed?

website?
translations?

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

[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] Announcements to all lists

[Moritz Lennert]

@MarkusN is there a way to either whitelist the address for all lists so that 
mails automatically are admitted ? Or to automatically register it as member of 
all lists (but with mail delivery from the lists deactivated) ?

Moritz

Am 15. Dezember 2020 10:22:28 MEZ schrieb "Chief Return Officer (CRO) - GRASS 
GIS election 2020" :
>It seems that messages sent from this account are not automatically 
>approved for various lists of which I am not a member. Should I become a 
>member of all lists? Or is this adress (cro.grass ...)  already 
>"blessed" for pushing messages in all related lists?
>
>/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]

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%7C6cef3730213149018
31055b3abf02c73%7C0%7C0%7C637436189351765565%7CUnknown%7CTWFpbGZsb3

Re: [GRASS-PSC] OSGEO account

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

Thanks for your response, Margherita.

I have not yet received any confirmation yet. The system does not 
recognize my adress either. I will have to try again.


/H.

On 2020-12-15 10:21, Margherita Di Leo wrote:

Hernan,

I don't see your account request in the open requests, perhaps someone 
has already approved it?


On Tue, Dec 15, 2020 at 10:08 AM Chief Return Officer (CRO) - GRASS 
GIS election 2020 > wrote:


Does anyone of you that is involved in OSGEO know how long can it
take
for OSGEO to proceess my "mantra" request?

/H.

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




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

[GRASS-PSC] Announcements to all lists

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

It seems that messages sent from this account are not automatically 
approved for various lists of which I am not a member. Should I become a 
member of all lists? Or is this adress (cro.grass ...)  already 
"blessed" for pushing messages in all related lists?


/H.

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

Re: [GRASS-PSC] OSGEO account

[Margherita Di Leo]

Hernan,

I don't see your account request in the open requests, perhaps someone has
already approved it?

On Tue, Dec 15, 2020 at 10:08 AM Chief Return Officer (CRO) - GRASS GIS
election 2020  wrote:

> Does anyone of you that is involved in OSGEO know how long can it take
> for OSGEO to proceess my "mantra" request?
>
> /H.
>
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
>


-- 
Margherita Di Leo
___
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]

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 in one of
these files, that they send a mail to the respective list informing us ?


I can do this at 

[GRASS-PSC] OSGEO account

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

Does anyone of you that is involved in OSGEO know how long can it take 
for OSGEO to proceess my "mantra" request?


/H.

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

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 
>> (> >) 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://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 

[GRASS-PSC] [GRASS GIS Elections 2020] Announcement and voters registry

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

Dear members of the GRASS community,

We are about to launch the 2020 election for members of the Project 
Steering Committee (PSC).


The nominating and voting process will be soon explained in detail in 
the Trac wiki (needs update, coming soon):


https://trac.osgeo.org/grass/wiki/PSC/Election2020

In the meanwhile, it may be of interest for the members of the community 
to check whether they are eligible to vote.


In this election, those who have the right to vote will be:

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

We are therefore considering the following lists as GRASS GIS electoral 
registry:


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

If someone finds that her/his name is not on any of these lists but it 
should, please send an e-mail to the corresponding list to inform the 
members of the PSC so the situation can be solved.



Hernán

Chief Return Officer (CRO)

GRASS GIS election 2020



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