Re: [GRASS-PSC] [Motion] Approve Linda's final report and issue the 2nd payment

[Markus Neteler via grass-psc]

nks to GitHub PRs and screenshots of the improved History Browser 
> pane can be found at [7] and [1].
>
>
> [1] 
> https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation#ScreenshotsofHistoryBrowserimprovements
>
> [2] https://github.com/OSGeo/grass/pull/3622
>
> [3] https://github.com/OSGeo/grass/pull/3421
>
> [4] https://github.com/OSGeo/grass/pull/3679
>
> [5] https://github.com/OSGeo/grass/pull/3234
>
> [6] https://github.com/OSGeo/grass/issues/3698
>
> [7] 
> https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation#FinalReport
>
> Have a nice week.
>
> Linda
> ___
> grass-dev mailing list
> grass-...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
> --
> Dra. Verónica Andreo
> Investigadora Adjunta de CONICET
> Instituto Gulich (CONAE - UNC)
> Centro Espacial Teófilo Tabanera (CETT)
> Falda del Cañete - Córdoba, Argentina
> +54 3547 40 int. 1153
> https://veroandreo.gitlab.io/
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc



-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC meeting minutes - February 9, 2024

[Markus Neteler via grass-psc]

On Tue, Feb 13, 2024 at 6:50 PM Veronica Andreo via grass-psc
 wrote:
>
> Dear all,
>
> Here are the PSC meeting minutes of our last meeting:
> https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20240209
>
> Comments, suggestions and contributions are more than welcome, I might have 
> missed something as I was off for some minutes :)

Thanks for writing up the minutes. I have added the "GRASS Wiki
authentication" solved bit.

An update from the last board meeting, you may have seen it:

https://wiki.osgeo.org/wiki/Board_Meeting_2024-02-06#OSGeo_Budget_2024
"OSGeo Projects: 28k $ to be approved. Projects that have not
requested a budget will not get a default amount this year. The board
will consider specific funding requests if needed. For the projects
that asked for a budget, the limit is 2.5k $ this year."

Best
Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Proposing Linda Karlovska as a new core developer

[Markus Neteler via grass-psc]

Great, congratulations, Linda and a big welcome!

Markus

On Fri, Jan 26, 2024 at 2:56 PM Linda Karlovská via grass-psc
 wrote:
>
> Thanks! I am happy to join the core team.:-)
>
> Linda
> -- Původní e-mail --
> Od: Martin Landa 
> Komu: GRASS PSC list 
> Kopie: Linda Kladivova 
> Datum: 26. 1. 2024 14:46:51
> Předmět: Re: [GRASS-PSC] Proposing Linda Karlovska as a new core developer
>
> Dear Linda,
>
> Results:
>
> Anna Petrasova: +1
> Helena Mitasova: +1
> Helmut Kudrnovsky: +1
> Huidae Cho: +1
> Markus Neteler: +1
> Martin Landa: +1
> Michael Barton: +1
> Vaclav Petras: +1
> Veronica Andreo: +1
>
> I hereby declare this motion as passed.
>
> Congratulations and welcome! [1]
>
> Regards, Martin
>
> [1] https://github.com/orgs/OSGeo/teams/grass-write/members
>
> --
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.cz/mentors/landa
>
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc



-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org/blog - blog & freelancing
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [Motion] Proposing Linda Karlovska as a new core developer

[Markus Neteler via grass-psc]

+1 Markus

Martin Landa via grass-psc  schrieb am Mi., 24.
Jan. 2024, 20:17:

> Dear PSC,
>
> st 24. 1. 2024 v 18:29 odesílatel  napsal:
>
>> yes, I have read legal aspects of code contributions and I will follow
>> them.
>>
>> I am happy to get this opportunity.🙂
>>
>
> Linda has accepted "RFC 2: Legal aspects of code contributions".
>
> Motion: accept Linda Karlovska (https://github.com/lindakladivova) as a
> core developer.
>
> I start with my +1.
>
> Martin
> --
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.cz/mentors/landa
> ___
> 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] [OSGeo-Discuss] Mailing lists to discourse migration

[Markus Neteler via grass-psc]

On Sat, Dec 30, 2023 at 10:50 AM Luca Delucchi via grass-psc
 wrote:
> For what I can see with the discourse instance of OpenStreetMap where we 
> created a category for Italian
> discussion there are only pros to have discourse instead mailman since:
> - people used to use mailing list can continue to answer via email
> - people used to write via forum con use this way
> - archive is searchable

(my answer copied also here from osgeo-discuss list)

Just to add to the options we (theoretically) have:

With an upgrade from mailman-2 to mailman-3 we could also have a
searchable archive. See for example:
https://lists.fedoraproject.org/archives/
which (not surprisingly) looks much more modern than the old mailman-2 on OSGeo.

> For my little usage I don't see any cons to move from mailman to Discourse, 
> however as Jody said every community can choose their own tool to communicate

Let me suggest to avid too much fragmentation. This will not help to
get people more engaged.

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

Re: [GRASS-PSC] [Motion] Approve Linda's student grant project and issue first payment

[Markus Neteler via grass-psc]

+1 Markus

On Thu, Dec 21, 2023 at 3:44 PM Veronica Andreo via grass-psc
 wrote:
>
> Dear all,
>
> Linda has presented a new project to be funded with GRASS student grants. In 
> this occasion she plans to continue working on the GUI history browser panel. 
> Have a look at the project here: 
> https://docs.google.com/document/d/18jt_8H9_KbyVWGGb6TEbCkMbGcExFe9aJ10kgfZQJ2c/edit?usp=sharing
>
> I hereby propose to approve Linda Karlovská's application for the GRASS 
> student grant and  issue the first payment as described here: 
> https://grasswiki.osgeo.org/wiki/Student_Grants.
>
> I start with my +1!
>
> Cheers,
> Vero
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc



-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Fw: Aw: Re: [Motion] Proposing Edouard Choinière as a new core developer

[Markus Neteler via grass-psc]

Dear Edouard,

On Mon, Dec 18, 2023 at 6:33 PM Veronica Andreo via grass-psc <
grass-psc@lists.osgeo.org> wrote:
>
> Dear all,
>
> Thanks Markus for the motion and thanks everyone for voting!
>
> Results:
> Anna Petrasova: +1
> Helena Mitasova: +1
> Helmut Kudrnovsky: +1
> Huidae Cho: +1
> Markus Neteler: +1
> Martin Landa: +1
> Michael Barton: +1
> Vaclav Petras: +1
> Veronica Andreo: +1
>
> I hereby declare this motion as passed. Welcome Edouard! :)

Congratulations and welcome!

> Markus, Vashek, Martin, would any of you grant Edouard the github
permissions, please? Thanks!!

Sure:
[image: image.png]
Added :-)

> In a private thread, Edouard suggested having some sort of tour/guideline
on how the project handles issues, PRs and such. Shall we coordinate a call
perhaps?

Maybe a good occasion to note down our procedures.

Best
Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] [Motion] Proposing Edouard Choinière as a new core developer

[Markus Neteler via grass-psc]

Dear PSC,

Edouard has acepted "RFC 2: Legal aspects of code contributions" [2], see
https://lists.osgeo.org/pipermail/grass-psc/2023-December/002784.html

Motion: accept Edouard Choinière (https://github.com/echoix) as a core
developer.

I start with my +1.

Markus

On Tue, Dec 12, 2023 at 3:01 PM Markus Neteler  wrote:
>
> Dear PSC,
>
> Let me propose Edouard Choinière (https://github.com/echoix) to be
> accepted as a core developer.
>
> Edouard has contributed relevant improvements and fixes to various
> parts of the source code:
>
> GRASS GIS core:
> - accepted PRs:
>   https://github.com/OSGeo/grass/pulls?q=is%3Apr+author%3Aechoix+is%3Aclosed
> - currently proposed PRs (open):
>   https://github.com/OSGeo/grass/pulls/echoix
>
> GRASS GIS addons:
> - accepted PRs:
>   
> https://github.com/OSGeo/grass-addons/pulls?q=is%3Apr+author%3Aechoix+is%3Aclosed
> - currently proposed PR (open):
>   https://github.com/OSGeo/grass-addons/pulls/echoix
>
> GRASS GIS web-site:
> - accepted PRs:
>   
> https://github.com/OSGeo/grass-website/pulls?q=is%3Apr+author%3Aechoix+is%3Aclosed
>
> I have asked him off-list and he would be happy to join the core team
> with write access to the main repository.
>
> Edouard, please state here, as a reply that you have read and will
> adhere to the legal aspects of code contributions (document "RFC 2:
> Legal aspects of code contributions" [2]).
>
> According to RFC 1 [1] all PSC members will then need to vote in
> separate motion.
>
> Best,
> Markus
>
> [1] 
> https://github.com/OSGeo/grass/blob/main/doc/development/rfc/PSC_guidelines.md#operation-of-the-psc
> [2] 
> https://github.com/OSGeo/grass/blob/main/doc/development/rfc/legal_aspects_of_code_contributions.md
>
> --
> Markus Neteler, PhD
> https://www.mundialis.de - free data with free software
> https://grass.osgeo.org
> https://neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [Motion] Appoint Vaclav Petras as new treasurer

[Markus Neteler via grass-psc]

On Wed, Dec 6, 2023 at 5:07 AM Vaclav Petras via grass-psc
 wrote:
>
> Thank you, Helena, and thank you, all! I'll be keeping an eye on possible 
> improvements so that it is easy for the next person to pick up the treasurer 
> job!
>
> Vaclav
>
>
> On Tue, 5 Dec 2023 at 06:54, Veronica Andreo via grass-psc 
>  wrote:
>>
>> Hi everyone,
>>
>> Thanks Vashek for volunteering for this role. I agree with Helena though, so 
>> I'll do my best to help out.

Do we need a handover? Or all clear what to do in this role?

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

[GRASS-PSC] Proposing Edouard Choinière as a new core developer

[Markus Neteler via grass-psc]

Dear PSC,

Let me propose Edouard Choinière (https://github.com/echoix) to be
accepted as a core developer.

Edouard has contributed relevant improvements and fixes to various
parts of the source code:

GRASS GIS core:
- accepted PRs:
  https://github.com/OSGeo/grass/pulls?q=is%3Apr+author%3Aechoix+is%3Aclosed
- currently proposed PRs (open):
  https://github.com/OSGeo/grass/pulls/echoix

GRASS GIS addons:
- accepted PRs:
  
https://github.com/OSGeo/grass-addons/pulls?q=is%3Apr+author%3Aechoix+is%3Aclosed
- currently proposed PR (open):
  https://github.com/OSGeo/grass-addons/pulls/echoix

GRASS GIS web-site:
- accepted PRs:
  
https://github.com/OSGeo/grass-website/pulls?q=is%3Apr+author%3Aechoix+is%3Aclosed

I have asked him off-list and he would be happy to join the core team
with write access to the main repository.

Edouard, please state here, as a reply that you have read and will
adhere to the legal aspects of code contributions (document "RFC 2:
Legal aspects of code contributions" [2]).

According to RFC 1 [1] all PSC members will then need to vote in
separate motion.

Best,
Markus

[1] 
https://github.com/OSGeo/grass/blob/main/doc/development/rfc/PSC_guidelines.md#operation-of-the-psc
[2] 
https://github.com/OSGeo/grass/blob/main/doc/development/rfc/legal_aspects_of_code_contributions.md

-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [Motion] Approve OSGeo Code Sprint 2023 reimbursements

[Markus Neteler via grass-psc]

Dear Vashek, all,

On Tue, Dec 5, 2023 at 2:11 PM Martin Landa via grass-psc
 wrote:
>
> Dear Vero, Vashek,
>
> út 5. 12. 2023 v 12:30 odesílatel Veronica Andreo via grass-psc 
>  napsal:
>>
>> I hereby declare this motion as passed.
>> Vashek, would you send the request to OSGeo treasurer, please?
>
>
>  Thanks for taking care of this. Martn

Thanks also from my side, all settled now.

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

Re: [GRASS-PSC] [Motion] Appoint Vaclav Petras as new treasurer

[Markus Neteler via grass-psc]

+1, Markus


Veronica Andreo via grass-psc  schrieb am Fr.,
1. Dez. 2023, 18:47:

> Dear all,
>
> This motion is to appoint Vaclav Petras as the new treasurer of the GRASS
> GIS project. He volunteered to replace Markus in the role after Markus
> communicated he preferred not to continue.
>
> I start with my +1
>
> Thanks everyone for your time!
>
> --
> Dra. Verónica Andreo
> Investigadora Adjunta de CONICET
> Instituto Gulich (CONAE - UNC)
> Centro Espacial Teófilo Tabanera (CETT)
> Falda del Cañete - Córdoba, Argentina
> +54 3547 40 int. 1153
> https://veroandreo.gitlab.io/
> ___
> 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] [Motion] Approve OSGeo Code Sprint 2023 reimbursements

[Markus Neteler via grass-psc]

+0 (since I am involved), Markus

On Fri, Dec 1, 2023 at 9:39 AM Martin Landa via grass-psc
 wrote:
>
> Dear PSC,
>
> Based on the GRASS PSC meeting [0] I asked Angelos. Here is his answer:
>
> """
> Usually, projects are taking PSC decisions to use their OSGeo budget to
> cover costs for joining the code sprint.
> The only exception is the ZOO Project that submitted a special request
> to the board because they recently graduated.
> """
>
> So, I hereby propose to approve reimbursements for OSGeo Code Sprint 2023 
> held in Vienna [1].
>
> Reimbursements cover travel and accommodation expenses. See details in [2] 
> including all bills.
>
> Namely:
>
> * Linda Karlovska: 133.38 EUR
> * Martin Landa: 324.83 EUR
> * Markus Neteler: 231.27 EUR
>
> Linda and I are asking for full reimbursement.
> Markus is asking for partial reimbursement since he was also attending BiDS.
>
> I will start with +0 since I am also asking for funding.
>
> Thanks for voting in advance, best regards, Martin
>
> [0] https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20231110
> [1] https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023
> [2] 
> https://docs.google.com/spreadsheets/d/1PYFJIwq_M8jm3rrGyUWOwZ5QQTOmKvyBuIiIFRLLqRY/edit?usp=sharing
>
> --
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.cz/mentors/landa
> ___
> 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

[GRASS-PSC] Next PSC meeting

[Markus Neteler via grass-psc]

Deall all,

Due to the ESA Big Data from Space (BIDS) 2023 conference and OSGeo
sprint (Vienna) I am unable to attend our next meeting.

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

Re: [GRASS-PSC] OSGeo Community Sprint 2023

[Markus Neteler via grass-psc]

Dear all,

On Wed, Oct 25, 2023 at 9:09 AM Martin Landa  wrote:
>
> Dear Vero, all,
>
>> In any case, perhaps you can provide further details? Is it just you asking 
>> for support or how many? Do you have an estimate?
>
>
> I just aware of Markus, me and Linda planning to come to Vienna code sprint. 
> My expenses should be around 330 EUR (three nights in Vienna + train ticket 
> from Prague). Linda is planning to stay for two days, so around 140 EUR. 
> Markus, can you please provide your expectations?

Since I will also participate in the ESA BIDS conf, some partial
support would be great, so let me suggest 250 EUR.

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

Re: [GRASS-PSC] OSGeo Community Sprint 2023

[Markus Neteler via grass-psc]

Dear all,

On Tue, Oct 24, 2023 at 2:03 PM Veronica Andreo via grass-psc
 wrote:
>
> Hi Martin,
>
> Cool! We do still have some funds AFAIU. Our treasurer will confirm :)

This needs to be checked, also how we want to "feed" the student grants.

> In any case, perhaps you can provide further details?

See also here:
https://lists.osgeo.org/pipermail/grass-dev/2023-October/096080.html

> Is it just you asking for support or how many? Do you have an estimate?

I will also be in Vienna, recently booked privately (so far).

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

Re: [GRASS-PSC] Preservation of Spearfish data set on Zenodo

[Markus Neteler]

On Wed, Aug 9, 2023 at 3:27 PM Vaclav Petras  wrote:
> On Wed, 9 Aug 2023 at 09:02, Peter Löwe  wrote:
...
>> For GRASS 5.x there are three distinct versions for the Spearfish dataset 
>> according to https://grass.osgeo.org/sampledata/
>>
>> spearfish_grass60data-0.1.tar.gz
>> spearfish_grass60data-0.3.tar.gz
>> spearfish_grass60data.tar.gz
>>
>> Both archives "0.1" and "0.3" have the same filesize, while "grass60data" is 
>> slightly smaller.
>>
>> Should all three versions be preserved and versioned by DOI ?
>
> Seems like pre-releases, while now we do have DOIs for RCs, there is no need 
> in general to have DOI for a version
> meant for testing only. Back then, the 0.1 and 0.3 might have been around for 
> a long time (I don't know), but from
> today's perspective, that's all forgotten. 6.0 is a long time ago (no date on 
> our Trac website [1] and a broken link).
>
> [1] https://trac.osgeo.org/grass/wiki/Release

Took a bit but I have now added all missing release dates + fixed the
broken links (GRASS 4, 5, 6).

Enjoy,
Markus


-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Kind reminder: PSC meeting this Friday Aug 11 at 15 UTC

[Markus Neteler]

Hi,

On Mon, Aug 7, 2023 at 1:01 PM Veronica Andreo  wrote:
>
> Dear all,
>
> This is a kind reminder of our quarterly PSC meeting this Friday August 11 at 
> 15 UTC (Local times here:
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023&month=8&day=11&hour=15&min=0&sec=0&p1=207&p2=51&p3=48&p4=25&p5=197).
>
> Topics are being collected at: 
> https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20230811. Please, 
> add/edit/comment :)

I have added some material and two questions :)

Markus

PS: I can stay only at most for an hour.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Virtual toast for GRASS 40th birthday?

[Markus Neteler]

Hi,

Just filled in the doodle below.
I'll be travelling back to Bonn by train that day but hope to be there on time.

Cheers
Markus

On Mon, Jul 10, 2023 at 2:00 PM Veronica Andreo  wrote:
>
> Dear all,
>
> Would you be willing to join a virtual toast to celebrate GRASS GIS 40th 
> birthday on July 29th? I know it's Saturday, but perhaps that's a good thing 
> ;)
>
> I checked suitable times with world clock 
> (https://www.timeanddate.com/worldclock/meetingtime.html?iso=20230729&p1=485&p2=207&p3=37&p4=25&p5=204&p6=197)
>  and created a doodle to vote:
>
> https://doodle.com/meeting/participate/id/aKQzrjnd
>
> Looking forward to hearing from you!
> Vero
> --
> Dra. Verónica Andreo
> Investigadora Asistente de CONICET
> Instituto Gulich (CONAE - UNC)
> Centro Espacial Teófilo Tabanera (CETT)
> Falda del Cañete - Córdoba, Argentina
> +54 3547 40 int. 1153
> https://veroandreo.gitlab.io/
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc



-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Add PSC members to OpenCollective site under "contributors"?

[Markus Neteler]

On Thu, May 25, 2023 at 9:37 PM Huidae Cho  wrote:
>
> Hi Markus,
>
> Just created my OpenCollective account. It's the same email address 
> gras...@gmail.com.

Thanks, also added as well.
So, the majority of the PSC is now present (scroll down):
https://opencollective.com/osgeo/projects/grass

Markus

> Thanks,
> Huidae
>
> On Mon, May 22, 2023 at 12:10 AM Markus Neteler  wrote:
>>
>> Dear PSC team,
>>
>> On Fri, May 12, 2023 at 8:43 PM Markus Neteler  wrote:
>> >
>> > Hi PSC,
>> >
>> > In the today's PSC video call we discussed the idea of having more
>> > people listed under  "Core Contributors" in OpenCollective (see
>> > https://opencollective.com/osgeo/projects/grass, at bottom).
>> > An idea is to invlte the PSC members (you!) here.
>> >
>> > There are different roles in the system. Here a suggestion for the roles:
>> >
>> > - Core Contributor --> PSC members (also selected others?)
>> > - Admin --> PSC chair, treasurer
>> > - Accountant --> PSC chair, treasurer
>> >
>> > What do you think? To make it easy I could simply invite you through
>> > the OpenCollective admin interface and you either accept or not the
>> > invitation.
>> > Extra work for your: nothing :)
>>
>> I have invited those of you who are already registered at OpenCollective.
>>
>> These PSC members I could not find in the system, please consider to
>> register (https://opencollective.com/osgeo/projects/grass):
>>
>> - Michael Barton
>> - Helmut Kudrnovsky
>> - Martin Landa
>> - Huidae Cho
>> - Anna Petrasova
>>
>> and then let me know your handle (private email is fine).
>>
>> Best,
>> Markus
>> ___
>> 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] Add PSC members to OpenCollective site under "contributors"?

[Markus Neteler]

Dear PSC team,

On Fri, May 12, 2023 at 8:43 PM Markus Neteler  wrote:
>
> Hi PSC,
>
> In the today's PSC video call we discussed the idea of having more
> people listed under  "Core Contributors" in OpenCollective (see
> https://opencollective.com/osgeo/projects/grass, at bottom).
> An idea is to invlte the PSC members (you!) here.
>
> There are different roles in the system. Here a suggestion for the roles:
>
> - Core Contributor --> PSC members (also selected others?)
> - Admin --> PSC chair, treasurer
> - Accountant --> PSC chair, treasurer
>
> What do you think? To make it easy I could simply invite you through
> the OpenCollective admin interface and you either accept or not the
> invitation.
> Extra work for your: nothing :)

I have invited those of you who are already registered at OpenCollective.

These PSC members I could not find in the system, please consider to
register (https://opencollective.com/osgeo/projects/grass):

- Michael Barton
- Helmut Kudrnovsky
- Martin Landa
- Huidae Cho
- Anna Petrasova

and then let me know your handle (private email is fine).

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

Re: [GRASS-PSC] RFC: Version Numbering

[Markus Neteler]

On Fri, May 12, 2023 at 11:17 PM Vaclav Petras  wrote:
>
> Dear PSC and all,
>
> I finalized the RFC for Version Numbering which is available in PR 2357:
>
> https://github.com/OSGeo/grass/pull/2357
>
> Use Files changed > Display the rich diff to view the RFC itself.
>
> PSC members, please approve or reject this RFC (-1, 0, +1).

+1

Markus

> Everyone, this is also a standard PR which brings changes to the source code, 
> please review, comment, suggest as usual.
>
> About version numbering: Software needs releases, releases need identifiers, 
> identifiers need a system.
>
> About RFCs: An RFC is a request for comments document which, when approved, 
> becomes a document which tells contributors how things are done. RFCs are now 
> in Markdown and are part of the source code.
>
> Best,
> Vaclav
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc



-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [Motion] Approve and adopt RFC about Python Language Support

[Markus Neteler]

+1

Markus

On Mon, May 15, 2023 at 9:27 PM Veronica Andreo  wrote:
>
> Dear all,
>
> Following the discussions in grass-dev quite some time ago and during PSC 
> meetings [0][1][2], I propose we approve and adopt the "RFC: Python Language 
> Support" currently living at https://github.com/OSGeo/grass/pull/2816. We can 
> then merge the PR.
>
> I start with my +1
>
> Thanks everyone for your time!
> Vero
>
> [0] https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20220211
> [1] https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20230210
> [2] https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20230512
>
> --
> Dra. Verónica Andreo
> Investigadora Asistente de CONICET
> Instituto Gulich (CONAE - UNC)
> Centro Espacial Teófilo Tabanera (CETT)
> Falda del Cañete - Córdoba, Argentina
> +54 3547 40 int. 1153
> https://veroandreo.gitlab.io/
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc



-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] Add PSC members to OpenCollective site under "contributors"?

[Markus Neteler]

Hi PSC,

In the today's PSC video call we discussed the idea of having more
people listed under  "Core Contributors" in OpenCollective (see
https://opencollective.com/osgeo/projects/grass, at bottom).
An idea is to invlte the PSC members (you!) here.

There are different roles in the system. Here a suggestion for the roles:

- Core Contributor --> PSC members (also selected others?)
- Admin --> PSC chair, treasurer
- Accountant --> PSC chair, treasurer

What do you think? To make it easy I could simply invite you through
the OpenCollective admin interface and you either accept or not the
invitation.
Extra work for your: nothing :)

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

Re: [GRASS-PSC] Kind reminder: PSC meeting this Friday May 12 at 15 UTC

[Markus Neteler]

On Fri, May 12, 2023 at 5:02 PM Michael Barton  wrote:
>
> We're on Google meet right? I have 2 different calendar invitations.

Please drop the Google meet series and keep the NCSU Zoom series.

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

Re: [GRASS-PSC] DOI for GRASS reference data sets

[Markus Neteler]

On Mon, Mar 27, 2023 at 10:16 AM Peter Löwe  wrote:
>
> Hi Markus, Vaclav, all,
>
> who were the original authors of the Spearfish dataset in 1993 (3 decades 
> ago!) ?

David A. Hastings wrote in "The Geographic Information Systems: GRASS
HOWTO" (Nov. 1997) the following description on p. 10:

"The Spearfish data base covers two 7.5 minute topographic sheets in
the northern Black Hills
of South Dakota, USA. It is in the Universal Transverse Mercator
Projection. It was
originally created by Larry Batten (now of the Environmental Systems
Research Institute's
office in Boulder, Colorado) while he was with the U. S. Geological
Survey's EROS Data
Center in South Dakota. The data base was enhanced by USA/CERL and cooperators."

So: Larry Batten , USGS EROS Data Center in South Dakota and USA/CERL
and cooperators.

Here the PDF
https://tldp.org/HOWTO/pdf/GIS-GRASS.pdf

but it is also at bottom of this page:
https://tldp.org/HOWTO/GIS-GRASS/index.html

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

Re: [GRASS-PSC] DOI for GRASS reference data sets

[Markus Neteler]

Hi Peter,

On Mon, Mar 27, 2023 at 3:41 AM Vaclav Petras  wrote:
> On Sun, 26 Mar 2023 at 10:22, Peter Löwe  wrote:
>>
>> Hello PSC,
>>
>> I would like to suggest to register persistent DOI for GRASS GIS related 
>> reference data sets such as Spearfish and North Carolina by preserving them 
>> in the Open Access repository Zenodo (www.zenodo.org).
>
>
> Good idea. I already considered it and I think it is quite appropriate. 
> Please, go ahead.

Happy to assist here (we can do preparations off-list):

- Spearfish:
  https://grass.osgeo.org/download/data/#SpearFishDataset
  --> Original documentation from 1993:
https://grass.osgeo.org/sampledata/spearDB.pdf

- North Carolina: see e.g.
  https://grassbook.org/datasets/datasets-1st-edition/
  https://grassbook.org/datasets/datasets-2nd-edition/
  https://grassbook.org/datasets/datasets-3rd-edition/
  There are different versions available starting from 2002 (GRASS GIS
5, 6, 7) which IMHO should all be tracked.

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

Re: [GRASS-PSC] GRASS DOI

[Markus Neteler]

Hi all,

Given the rainy day here I have drafted a CITATION.cff for GRASS GIS 8.x:

https://github.com/OSGeo/grass/pull/2904

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

Re: [GRASS-PSC] [Motion] Approve Linda's student grant final report and make the 2nd payment

[Markus Neteler]

+1

Markus

Veronica Andreo  schrieb am Mo., 6. März 2023, 14:14:

> Dear PSC,
>
> Linda has just completed her project for the student grant and submitted
> the final report (I FWD it here in case you missed it).
>
> I hereby propose to approve her final report and issue the second payment.
> Big thanks to Linda and her mentors for your work and commitment! Thanks as
> well to those testing and providing feedback along the process! Great work
> Linda!! Congratulations!
>
> I start with my +1 !!
>
> Vero
>
>
> -- Forwarded message -
> De: Linda Kladivová 
> Date: dom, 5 mar 2023 a las 19:12
> Subject: [GRASS-dev] Final report for Mini project 2023: Improving
> Single-Window GUI user experience
> To: , 
>
> Hello everyone,
>
> I am sending my final Mini Project report.
>
> First, sorry for the huge delay. By the end of January, all PRs were
> almost finished but there were still some minor lacks that needed more time
> to address. Mainly the undocking functionality needed to ripen a bit. At
> the same time and later (till the end of February) I was also finishing
> preparations for my doctoral professional debate so It was quite a hectic
> period.
>
> The next rows include a brief version of the final report. The full
> version with permanent links on GitHub PRs and with screenshots of
> Single-Window GUI improvements can be found in the project wiki [1].
>
> *Abstract:*
> This project follows ideas for Single-Window GUI improvements mentioned in
> the last-year Mini-project final report (please see
> 
> [2]).
>
> The core part of the project is devoted to undocking map display
> functionality. This ability is essential to users who prefer the well-known
> Multi-Window GUI arrangement. The other part focuses on improving the
> layout of the Console pane. Related to the Console pane issue, the
> toggleable Log file button in the Console pane is replaced by the simple
> Export history button which can store the whole history of executed
> commands. The project also verifies if workspaces work well in
> Single-Window and addresses saving the current user layout to a workspace
> file. The workspace file also remembers and loads undocked map displays.
>
>
> *The state of the art BEFORE the start of the Mini project:*
>
>- The Single-Window GUI does not allow rearrangement to Multi-Window
>GUI.
>- The widget with buttons managing the Command prompt is partly hidden
>after the GRASS launch.
>- The Single-Window arrangement is not stored within the workspace.
>
> *The state of the art AFTER Mini project:*
> Starting with GRASS 8.4 we can come across several Single-Window
> improvements that were implemented as part of this project. First, there is
> the new possibility to create a Multi-Window interface by undocking map
> displays. Moreover, we can store a new arrangement within workspace files.
> Last but not least, the Console layout better fits the Single-Window
> interface.
>
> *Next Steps:*
> Possible improvements for Single-Window GUI:
>
>- Each user should be able to choose a convenient arrangement of
>widgets. Creating, saving, and selecting perspectives could be part of a
>new tab menu.
>- It is necessary to change the rendering of the 3D View panel. Now
>the 3D View pane is added as another panel under the Display tab - very
>problematic in terms of space.
>- Modify the appearance for the dark mode. Some parts are ugly and
>illegible (names of AuiNotebook tabs, names of panes, ugly gradients, 
> etc.).
>
> Permanent links and screenshots can be found at [3] and [4].
>
> [1]
> https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/ImprovingSingleWindowUX
>
> [2]
> https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/RedesigningStatusbar#FinalReport
>
> [3]
> https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/ImprovingSingleWindowUX#FinalReport
>
> [4]
> https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/ImprovingSingleWindowUX#ScreenshotsofSingle-WindowGUIimprovements
>
> Have a nice week.
> Linda
> ___
> grass-dev mailing list
> grass-...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
> ___
> 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] Stepping down

[Markus Neteler]

Dear Moritz,

On Wed, Feb 8, 2023 at 10:12 PM Moritz Lennert
 wrote:
>
> Hi !
>
> The next PSC meeting is coming up and I will probably again not have the 
> opportunity to attend as I am in Bamako and normally in a meeting at that 
> time.
>
> As mentioned in a separate thread a while ago, I think it would be better if 
> I stepped down from the board and left the place for someone more active. 
> This will be with a big tear in my eye, but even though in my current work we 
> use GRASS GIS, I just didn't have the time to spend any time on project 
> governance anymore. And now I'm going into a new professional direction that 
> will take me further away from GRASS (and GIS in general).
>
> I hope to still be able to follow the life of the community and see you all 
> at one occasion or another.

Thank you a lot for serving on PSC for so many years! Your experience
and dedication have been so helpful to bring forward this project.
Please keep connected to the GRASS GIS community, as much as time permits :-)

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

Re: [GRASS-PSC] [OSGeo-Discuss] OSGeo Budget 2023

[Markus Neteler]

Hi PSC,

here an idea: our software documentation and Wiki pages are getting
older, lacking examples, screenshots, overviews and so on.
In the Wikis, redundant material should be streamlined.

I see two possibilities:
- participate in the recently announced Google season of docs
(https://developers.google.com/season-of-docs/docs/timeline)
- offer a documentation related mini grant, ideally financed by OSGeo
(then it would be relevant for today's budget submission)

What do you think?

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

Re: [GRASS-PSC] [OSGeo-Discuss] OSGeo Budget 2023

[Markus Neteler]

Hi PSC,

The deadline is today.
I'm traveling for most of the day, with intermittent internet access.

Will you, Vero, submit your request?

Best
Markus


Markus Neteler  schrieb am Mi., 4. Jan. 2023, 20:07:

> Hi PSC,
>
> The deadline for the 2023 budget proposal for the OSGeo board is
> January 20, see below.
>
> Markus
>
> -- Forwarded message -
> From: Angelos Tzotsos via Discuss 
> Date: Sun, Jan 1, 2023 at 12:49 PM
> Subject: [OSGeo-Discuss] OSGeo Budget 2023
> To: OSGeo Discussions 
>
> Dear OSGeo project members and committees,
>
> Over the previous years, OSGeo has been proud to support a growing
> number of project events, such as code sprints, developer meetings and
> user conferences.
>
> OSGeo continues to execute the annual budget, and is reaching out to all
> committees (including Project Steering Committees), to help plan our
> budget for 2023.
>
> In 2022, the Board assigned an initial amount of 500 USD to all
> graduated projects who have reported to the Board the activities of the
> last 12 months (e.g. during the AGM or directly to a Board meeting) and
> have sent a budget request.
>
> Given the success of FOSS4G 2022 we are in the position to support our
> projects again as before. For 2023, the Board is planning to continue to
> offer a budget to all graduated projects with the exact amount to be
> determined.
>
> To help navigate the uncertainties ahead in 2023, the Board is planning
> to have a budget meeting within January 2023 to review 2022
> expenditures, sponsorship and make financial decisions for the 2023 budget.
>
> Projects with a more specific plan (to pursue a clear goal) are welcome
> to send a more detailed request for approval (see detailed budget
> requests from 2022 e.g.
> https://wiki.osgeo.org/wiki/GeoServer_Budget_2022) A good idea is to
> focus on OSGeo participation, for example attending the AGM or a code
> sprint. Also, keep in mind OSGeo goals as an organization.
>
> Please add your project info to the budget draft at:
>
> https://wiki.osgeo.org/wiki/OSGeo_Budget_2023
> <https://wiki.osgeo.org/wiki/OSGeo_Budget_2023>
>
> Project budget requests should be submitted ideally by 20 January 2023
> in advance of our next Board meeting.
>
> Thank you and Happy New Year!
> On behalf of the OSGeo Board,
> Angelos
>
> --
> Angelos Tzotsos, PhD
> President
> Open Source Geospatial Foundation
> http://users.ntua.gr/tzotsos
>
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [Motion] Appoint Markus Neteler as new treasurer

[Markus Neteler]

Dear PSC,

On Thu, Jan 19, 2023 at 2:16 PM Veronica Andreo  wrote:
>
> Dear all,
>
> Thanks for your votes and thanks again Markus for volunteering!
>
> Results:
>
> Michael +1
> Helena +1
> Vaclav +1
> Moritz +1
> Huidae +1
> Anna +1
> Martin +1
> Vero +1
> Markus 0
>
> I declare this motion as passed.
> Markus and Moritz, let's discuss/plan what to do with GRASS money in paypal.
>
> Thanks again!
> Vero

Many thanks for giving your trust!

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

Re: [GRASS-PSC] [Motion] Appoint Markus Neteler as new treasurer

[Markus Neteler]

On Sat, Jan 14, 2023 at 3:23 PM Veronica Andreo  wrote:
>
> Dear all,
>
> This motion is to appoint Markus Neteler as the new treasurer of the GRASS 
> GIS project. He volunteered to replace Moritz in the role after Moritz 
> communicated he preferred not to continue.
>
> I start with my +1
>
> Thanks everyone for your time!
>
> Vero

Since I am involved I'll abstain from voting.

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

Re: [GRASS-PSC] [OSGeo-Discuss] OSGeo Budget 2023

[Markus Neteler]

Hi PSC,

On Wed, Jan 4, 2023 at 8:07 PM Markus Neteler  wrote:
>
> Hi PSC,
>
> The deadline for the 2023 budget proposal for the OSGeo board is
> January 20, see below.

Thanks to Vero we have a new Wiki page
(https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2023) and also the
related ODS file updated in our PSC nextcloud.osgeo.org account.

Concerning the budget, I would like to bring forward the following idea:

Weblate (our translation tool,
https://weblate.osgeo.org/projects/grass-gis/) offers a plugin for
machine translation, e.g. using DeepL.
Given the amount of untranslated messages I'd suggest that we give it
a try. Certainly, these messages need to be validated but I can image
that the speed is way higher than doing it all manually.

Proposal: identify a small sub-budget to play around with machine
translations in Weblate, using one of the related machine translation
APIs (https://docs.weblate.org/en/latest/admin/machine.html).

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

[GRASS-PSC] Fwd: [OSGeo-Discuss] OSGeo Budget 2023

[Markus Neteler]

Hi PSC,

The deadline for the 2023 budget proposal for the OSGeo board is
January 20, see below.

Markus

-- Forwarded message -
From: Angelos Tzotsos via Discuss 
Date: Sun, Jan 1, 2023 at 12:49 PM
Subject: [OSGeo-Discuss] OSGeo Budget 2023
To: OSGeo Discussions 

Dear OSGeo project members and committees,

Over the previous years, OSGeo has been proud to support a growing
number of project events, such as code sprints, developer meetings and
user conferences.

OSGeo continues to execute the annual budget, and is reaching out to all
committees (including Project Steering Committees), to help plan our
budget for 2023.

In 2022, the Board assigned an initial amount of 500 USD to all
graduated projects who have reported to the Board the activities of the
last 12 months (e.g. during the AGM or directly to a Board meeting) and
have sent a budget request.

Given the success of FOSS4G 2022 we are in the position to support our
projects again as before. For 2023, the Board is planning to continue to
offer a budget to all graduated projects with the exact amount to be
determined.

To help navigate the uncertainties ahead in 2023, the Board is planning
to have a budget meeting within January 2023 to review 2022
expenditures, sponsorship and make financial decisions for the 2023 budget.

Projects with a more specific plan (to pursue a clear goal) are welcome
to send a more detailed request for approval (see detailed budget
requests from 2022 e.g.
https://wiki.osgeo.org/wiki/GeoServer_Budget_2022) A good idea is to
focus on OSGeo participation, for example attending the AGM or a code
sprint. Also, keep in mind OSGeo goals as an organization.

Please add your project info to the budget draft at:

https://wiki.osgeo.org/wiki/OSGeo_Budget_2023


Project budget requests should be submitted ideally by 20 January 2023
in advance of our next Board meeting.

Thank you and Happy New Year!
On behalf of the OSGeo Board,
Angelos

--
Angelos Tzotsos, PhD
President
Open Source Geospatial Foundation
http://users.ntua.gr/tzotsos
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] PSC Meeting minutes - May 13th, 2022

[Markus Neteler]

On Fri, Nov 11, 2022 at 5:51 PM Markus Neteler  wrote:
> Hi Moritz,
>
> On Tue, May 17, 2022 at 10:01 AM Moritz Lennert
>  wrote:
> ...
> > I would also like to ask if anyone else would like to take over the role of 
> > treasurer. It's not a very time-consuming job,
> > but I need to reduce my mental load.
>
> Some time has passed and the PSC should consider your request :-)
>
> Any volunteers?

Alright... since I wrote the reply above I now volunteer :-) Maybe
there are more candidates?

I suppose that this needs a formal PSC motion and decision.

> > An important issue is to consolidate the reorganization of our accounts 
> > (currently we have money left
> > in the €-based PayPal money pool linked to my personal PayPal account

IMHO this account should be urgently emptied.

> >  and a $-based account at
> > Opencollective), knowing that we have interactions in both currencies.
> >
> > Moritz

And also this table needs to be updated:
https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2022

Markus


-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [Motion] Reimbursement for stickers for GIS Week at NC State

[Markus Neteler]

+1 Markus


Vaclav Petras  schrieb am Fr., 11. Nov. 2022, 20:55:

> Dear PSC,
>
> I'm asking for reimbursement for stickers and magnets from stickermule.com
> I got for GIS Week at NC State University. The amounts I ordered take
> advantage of the better prices for higher quantities. I will use the rest
> for smaller opportunities I have for giving out promotional materials
> (workshops, conferences, colleagues). I'm asking for reimbursement of
> 343.74 USD. The itemized list follows. I'll share the invoice privately.
>
> 1.51"x2" Die Cut, 200pcs, $87
> 2.27"x3" Large die cut stickers, 200pcs, $117
> 3"x3" Rounded Magnet with Trees, 100pcs, $110
> 2.5" x 2.5" Square stickers with license, 200pcs, $101
> Quantity discount $94.50
> Sales tax $23.24
> Total after discount with tax: $343.74
>
> The designs are in the grass-promo repo [1].
>
> I'll start the voting with +0.
>
> Thank you,
> Vaclav
>
> [1] https://github.com/OSGeo/grass-promo/pull/1/files
> ___
> 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] [Motion] Approve Linda's proposal for GRASS mini grant

[Markus Neteler]

+1 Markus


Anna Petrášová  schrieb am Fr., 11. Nov. 2022, 20:27:

> Dear all,
>
> As previously discussed, I hereby propose that we approve and accept Linda
> Kladivova's application for the GRASS mini grant for students and that we
> issue the first payment as described here:
> https://grasswiki.osgeo.org/wiki/Student_Grants.
>
> Linda's proposal is to continue working on the Single window to improver
> user experience.
>
> +1 from me!
>
> Thanks,
> Anna
> ___
> 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 Meeting minutes - May 13th, 2022

[Markus Neteler]

Hi Moritz,

On Tue, May 17, 2022 at 10:01 AM Moritz Lennert
 wrote:
...
> I would also like to ask if anyone else would like to take over the role of 
> treasurer. It's not a very time-consuming job,
> but I need to reduce my mental load.

Some time has passed and the PSC should consider your request :-)

Any volunteers?

> An important issue is to consolidate the reorganization of our accounts 
> (currently we have money left
> in the €-based PayPal money pool linked to my personal PayPal account and a 
> $-based account at
> Opencollective), knowing that we have interactions in both currencies.
>
> Moritz

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

Re: [GRASS-PSC] GRASS DOI

[Markus Neteler]

Hi PSC,

On Sun, Feb 6, 2022 at 9:55 PM Markus Neteler  wrote:
> On Thu, Jan 13, 2022 at 4:26 PM Vaclav Petras  wrote:
> >
> > All right, that is yes for ORCiD IDs.
> >
> > Next question: Are we putting them to contributors.csv as a new column or 
> > doing something else?
>
> In pull request
> https://github.com/OSGeo/grass/pull/2177
> I have added a new orcid column (https://orcid.org/) to the file.
>
> I have also made a quick round of searches to identify some ORCIDs.
> Please review.

Still valid :-)

> > In case we create another file (CITATION.cff or .zenodo.json) with a list 
> > of names from GitHub, it seems we have two different lists of authors.
> > Or is that what we want? A list of all authors/contributors including the 
> > very historical ones and another shorter list of people which is used
> > for citation. How do you qualify for the list? You get to the top N 
> > committers on GitHub?
>
> Perhaps something like
> - list from https://github.com/OSGeo/grass/graphs/contributors
> - order by commits
> - consider the last 12 months.

What do you think? IMHO the CITATION.cff / .zenodo.json could change
from release to release since the contributors per release are
changing.

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

Re: [GRASS-PSC] Fwd: Call for ideas to post in social media

[Markus Neteler]

On Sat, Apr 16, 2022 at 6:29 PM Veronica Andreo  wrote:
>
> Dear all,
>
> I'm re-calling for help with crafting weekly twitter threads. I thank those 
> of you that contributed nice ideas. However, if you are knowledgeable in a 
> topic, I'd really appreciate it if you could provide content for your idea. 
> In that way, it'll be correct once published and we optimize our time. 
> Currently, there's one ready for next week kindly pointed out by Anna and 
> contributed by Stefan and that's about it...
>
> https://trac.osgeo.org/grass/wiki/PSC/Marketing#Upcomingpostsmayberecycledandpostedagain

I have added as an idea, to showcase selected GRASS GIS commands
(those which have a (nice) screenshot in the manual, for easier
publishing).
See the addition change here:
https://trac.osgeo.org/grass/wiki/PSC/Marketing?action=diff&version=63

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

Re: [GRASS-PSC] [Motion] Approve Caitlin's student grant final report and issue the second payment

[Markus Neteler]

te of the art AFTER the Mini Project:*
>>>>> 1. New TimeSeriesMap class that creates ipywidget time sliders of
>>>>> space time datasets (see attached timeseriesmap.png) and a notebook
>>>>> documenting it's usage [1]
>>>>> 2. Improved GRASS-folium integration allowing rasters and vectors to
>>>>> be added to existing folium maps (see attached grass-folium.png) and
>>>>> updated notebook demonstrating its usage [2]
>>>>> 3. Updated class names:
>>>>>
>>>>>- GrassRenderer -> Map
>>>>>- Grass3dRenderer -> Map3D
>>>>>- InteractiveMap
>>>>>- TimeSeries -> TimeSeriesMap
>>>>>
>>>>> 4. Thanks to Vaclav Petras, we also have a manual page for
>>>>> grass.jupyter [3]
>>>>> 5. I didn't end up working to integrate GRASS and Pandas. It seems
>>>>> that it is quite straightforward to display vector attributes in
>>>>> nicely-formatted Pandas tables. For example:
>>>>>
>>>>> >>> import pandas as pd
>>>>>
>>>>> >>> import sqlite3
>>>>> >>> sql_path = gs.read_command("db.databases",
>>>>> driver="sqlite").replace('\n', '')
>>>>> >>> con = sqlite3.connect(sql_path)
>>>>> >>> sql_stat="SELECT * FROM field"
>>>>> >>> df = pd.read_sql_query(sql_stat, con)
>>>>>
>>>>> >>> con.close()
>>>>> >>> df
>>>>>
>>>>> There are other outputs that would be nice to display in nice Pandas
>>>>> tables, like text output from r.univar, r.stats, or t.vect.list. However,
>>>>> this is difficult since there is no standard output that is easily
>>>>> parse-able to pandas. I think the best way would be to create a standard
>>>>> json or csv output for all modules that return text. Then, it would be
>>>>> simple to take any module output and convert to a nice-looking Pandas 
>>>>> table.
>>>>>
>>>>> *Next Steps:*
>>>>> 1. Bug: InteractiveMap does not honor use_region=True for vectors.
>>>>> 2. Bug: InteractiveMap for Jupyter does not handle not existing data
>>>>> properly (https://github.com/OSGeo/grass/issues/2302
>>>>> <https://urldefense.com/v3/__https://github.com/OSGeo/grass/issues/2302__;!!IKRxdwAv5BmarQ!O6p_95e3SKYK5mKOIkmws-FQ3JJ3WRTZefvkke9v6p7LEJ21bU3fwxtja0adUtsw5WY$>
>>>>> )
>>>>> 3. InteractiveMap: add legend options for rasters, support simpleCRS
>>>>> for faster rendering, ToolTip integration for vector attributes
>>>>> 4. Continue Pandas integration by adding standard json or csv output
>>>>> to modules that return text
>>>>> 5. ... And many others! I think there's still lots of ways we can
>>>>> improve and expand the integration of GRASS and Jupyter. Ideas welcome.
>>>>>
>>>>> You can find an archive of all my weekly reports at [4] and follow
>>>>> next steps for grass.jupyter on our project page on GitHub [5]. Thank you
>>>>> again to Vaclav Petras and Anna Petrasova for their guidance and
>>>>> contributions to grass.jupyter. And, another thank you to Vero Andreo,
>>>>> Stefan Blumentrath and Markus Neteler for their feedback and testing!
>>>>>
>>>>> Best,
>>>>> Caitlin
>>>>>
>>>>> [1]
>>>>> https://mybinder.org/v2/gh/OSGeo/grass/main?urlpath=lab%2Ftree%2Fdoc%2Fnotebooks%2Ftemporal.ipynb
>>>>> <https://urldefense.com/v3/__https://mybinder.org/v2/gh/OSGeo/grass/main?urlpath=lab*2Ftree*2Fdoc*2Fnotebooks*2Ftemporal.ipynb__;JSUlJQ!!IKRxdwAv5BmarQ!O6p_95e3SKYK5mKOIkmws-FQ3JJ3WRTZefvkke9v6p7LEJ21bU3fwxtja0adprRiMPc$>
>>>>> [2]
>>>>> https://mybinder.org/v2/gh/OSGeo/grass/main?urlpath=lab%2Ftree%2Fdoc%2Fnotebooks%2Fgrass_jupyter.ipynb
>>>>> <https://urldefense.com/v3/__https://mybinder.org/v2/gh/OSGeo/grass/main?urlpath=lab*2Ftree*2Fdoc*2Fnotebooks*2Fgrass_jupyter.ipynb__;JSUlJQ!!IKRxdwAv5BmarQ!O6p_95e3SKYK5mKOIkmws-FQ3JJ3WRTZefvkke9v6p7LEJ21bU3fwxtja0adRk6yl2Q$>
>>>>> [3]
>>>>> https://grass.osgeo.org/grass81/manuals/libpython/grass.jupyter.html
>>>>> <https://urldefense.com/v3/__https://grass.osgeo.org/grass81/manuals/

Re: [GRASS-PSC] [Motion] Approve Linda's student grant final report and issue the second payment

[Markus Neteler]

+1 Markus
Thanks Linda and mentors!

On Thu, Mar 3, 2022 at 11:30 PM Veronica Andreo  wrote:
>
> Dear PSC,
>
> Linda has just completed her project for the student grant and submitted the 
> final report (I FWD it here in case you missed it).
>
> I hereby propose to approve her final report and issue the second half of the 
> payment. Big thanks to Linda and her mentors for your work and commitment!
>
> I start with my +1 !!
>
> Vero
>
> -- Forwarded message -
> De: Linda Kladivová 
> Date: mié, 2 mar 2022 a las 19:19
> Subject: [GRASS-dev] Final report for Mini project 2022: Redesigning a map 
> display status bar combo box into a new settings dialog
> To: , 
>
> Hello everyone,
>
>
> I am sending my final Mini Project report. The more detailed version with 
> permanent links on GitHub PRs and with several screenshots can be found at 
> the project wiki [1].
>
> Abstract:
>
> Especially for Single-Window GUI, the Map Display status bar needs to be 
> lightened up a bit since in the case of opening more Map Display notebook 
> pages the check box on the right side of the status bar gets shrunk. The 
> solution is to remove the combo box in the status bar occupying too much 
> space and implement a new Map Display settings dialog accessible from the top 
> map display toolbar.
>
> The state of the art BEFORE the start of Mini Project:
>
> At this moment, the status bar at the bottom of the Map Display window 
> consists of the text/widget section, the combo box, the mask and the check 
> box. For the Single-Window GUI, the number of widgets must be reduced so that 
> the check box on the right side of the status bar is not shrunk.
>
> The state of the art AFTER Mini Project:
>
> The new Map Display settings dialog is introduced. The main task of this 
> dialog is to manage General Map Display settings and Statusbar settings. It 
> implies that the status bar combobox is not needed anymore because we can 
> find all Map Display settings including status bar customization in the new 
> dialog.
>
>
> Next Steps:
> Other possible improvements related to status bar stuff could be:
>
> Moving Projection page from GUI settings to the Map Display status bar 
> settings
> Adding context menu for status bar customization
> Adding EPSG code label of current location to the main status bar
> Merging „Go to coordinates X, Y“ and „Coordinates“ item into one widget
>
> Permanent links and screenshots can be found at [2] and [3].
>
> [1] https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/RedesigningStatusbar
>
> [2] 
> https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/RedesigningStatusbar#FinalReport
>
> [3] 
> https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/RedesigningStatusbar#BrandnewScreenshotsofMapDisplaySettingsdialog
>
> Have a nice week,
>
> Linda
> ___
> grass-dev mailing list
> grass-...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc



-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] difficult to get GRASS source code package

[Markus Neteler]

On Mon, Feb 14, 2022 at 5:08 PM Michael Barton  wrote:
>
> This sounds a bit weird, but with some recent changes to the GRASS website, 
> it has become more difficult to find and download a current stable release.
>
> I went to find a tar/zip package of GRASS 8.0.0 source code to build and 
> could not find one from the web site. The links all lead only to the GitHub 
> repository.

I agree that it is missing from
https://grass.osgeo.org/download/

In my view (I expressed that also in the past) we should link a zip
file/tarball directly on that page. Just pointing to GH isn't enough
and we even have the tarballs on the server:

https://grass.osgeo.org/grass80/source/

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

Re: [GRASS-PSC] GRASS DOI

[Markus Neteler]

On Thu, Jan 13, 2022 at 4:26 PM Vaclav Petras  wrote:
>
> All right, that is yes for ORCiD IDs.
>
> Next question: Are we putting them to contributors.csv as a new column or 
> doing something else?

In pull request
https://github.com/OSGeo/grass/pull/2177
I have added a new orcid column (https://orcid.org/) to the file.

I have also made a quick round of searches to identify some ORCIDs.
Please review.

> In case we create another file (CITATION.cff or .zenodo.json) with a list of 
> names from GitHub, it seems we have two different lists of authors. Or is 
> that what we want? A list of all authors/contributors including the very 
> historical ones and another shorter list of people which is used for 
> citation. How do you qualify for the list? You get to the top N committers on 
> GitHub?

Perhaps something like
- list from https://github.com/OSGeo/grass/graphs/contributors
- order by commits
- consider the last 12 months.

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

Re: [GRASS-PSC] Budget 2022

[Markus Neteler]

Dear PSC,

On Fri, Jan 7, 2022 at 2:02 AM Veronica Andreo  wrote:
>
> Dear all,
>
> It is that time of the year :) We need to submit our budget by Jan 20, 2022.
>
> I have already created the relevant page (1)
...
> (1) https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2022

I have looked at the latest version and updated a few comments.
To me it looks fine.

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

Re: [GRASS-PSC] GRASS DOI

[Markus Neteler]

On Tue, Jan 4, 2022 at 4:39 PM Vaclav Petras  wrote:
>
> Dear Helena and all,
>
> Yes, it is auto-generated by Zenodo. It was the first step - to get a DOI 
> (main one and one for each release). Now we need to decide what is right for 
> the authors list.
>
> The current one looks messy. That is true. However, is it wrong? Or, in what 
> way is it wrong?
>
> GitHub handles might be appropriate when that's all people choose to reveal 
> on GitHub, although it looks wrong in academia. However, looking at the list, 
> it is likely that some people just never came around to adding their name to 
> GitHub (while having it in the source code). Some others have just part of 
> their name, all-caps name, and yet some others have their name in two 
> languages.
>
> Author order is derived from GitHub > Insights > Contributors [1] which is 
> mostly good from a software maintenance perspective (recency and line 
> volume). How well it represents the order of contributors in terms of credit 
> is a question related to the whole "academic credit for software" debate. The 
> whole auto-generated list can be in this case replaced by a CITATION.cff file 
> which Zenodo will now pick up and use.
>
> Action item 1: Add or improve your name on GitHub. Use whatever you would use 
> when authoring a paper or a book. This name may also show in your commits. 
> See also what `git config --get user.name` gives you.
>
> Action item 2: See where you are in the list or if you are even there. 
> Discuss on the grass-dev mailing list or complain to me privately how to 
> better represent your contribution.
>
> I would be happy to discuss other ideas people have. Just let me know, e.g., 
> on grass-dev.

FYI: GDAL started just today to generate a Zenodo entry. Even took the
top 16 commiters [3] according to GitHub and created a .zenodo.json
file to control authorship:

https://github.com/OSGeo/gdal/pull/5101/files

Perhaps interesting for us as well.

Best,
Markus

[3] Even's email on the matter:
https://lists.osgeo.org/pipermail/gdal-dev/2022-January/055236.html

> Best,
> Vaclav
>
> [1] https://github.com/OSGeo/grass/graphs/contributors
> [2] https://doi.org/10.5281/zenodo.5176030
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [Motion] Approve Caitlin's proposal for GRASS mini grant

[Markus Neteler]

+1 Markus

On Thu, Dec 30, 2021 at 12:12 AM Veronica Andreo  wrote:
>
> Dear all,
>
> I hereby propose to approve and accept Caitlin Haedrich's application for a 
> GRASS mini grant and to issue the first payment as described here: 
> https://grasswiki.osgeo.org/wiki/Student_Grants.
>
> Caitlin was a GSoC 2021 student and her proposal for this 2 months mini grant 
> is to continue working on the GRASS-Jupyter integration, more specifically on 
> Space-Time Dataset Visualization and Improved Interactive Maps for 
> grass.jupyter. The proposal was sent privately as described in the wiki above 
> (for future mini grants calls we should consider moving to a public place, 
> i.e., grass wiki, trac wiki, github, etc.).
>
> I will start with my +1!
>
> Thanks in advance,
> Vero
>
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc



-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Fwd: Re: [Motion] Approve Linda's proposal for GRASS mini grant

[Markus Neteler]

On Fri, Dec 17, 2021 at 8:33 PM Markus Neteler  wrote:
> Moritz Lennert :
>>
>> Yes, and I don't think that applications arriving in my private mail is a 
>> durable solution. I never proposed being the recipient of these 
>> applications. I rather proposed to create a specific address.
>
> I could create an email reflector, e.g.

grass-gr...@osgeo.org

suggestion: this could go to all PSC members
What do you think?

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

Re: [GRASS-PSC] Fwd: Re: [Motion] Approve Linda's proposal for GRASS mini grant

[Markus Neteler]

Moritz Lennert :

> Yes, and I don't think that applications arriving in my private mail is a
> durable solution. I never proposed being the recipient of these
> applications. I rather proposed to create a specific address.
>


I could create an email reflector, e.g.

grass-gr...@osgeo.org

or similar (suggestions welcome) but I'd need a real address to which this
reflector shall point to...


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

Re: [GRASS-PSC] [Motion] Approve Linda's proposal for GRASS mini grant

[Markus Neteler]

+1
Markus

On Tue, Dec 14, 2021 at 12:33 PM Huidae Cho  wrote:
>
> +1
>
> Huidae
>
> On Tue, Dec 14, 2021 at 3:01 AM Veronica Andreo  wrote:
>>
>> Dear all,
>>
>> As previously discussed, I hereby propose that we approve and accept Linda 
>> Kladivova's application for the first GRASS mini grant for students and that 
>> we issue the first payment as described here: 
>> https://grasswiki.osgeo.org/wiki/Student_Grants.
>>
>> Linda's proposal is to continue working on the Single window and redesign 
>> the map display status bar combo box into a new settings dialog to reach a 
>> fully working single window GUI mode.
>>
>> I will start with my +1!
>>
>> Thanks in advance,
>> Vero
>> ___
>> grass-psc mailing list
>> grass-psc@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-psc
>
>
>
> --
> Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大
> GRASS GIS Developer
> https://idea.isnew.info/
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc



-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] Indeed FOSS Contributor Fund

[Markus Neteler]

Hi PSC,

Maybe of interest to us (via Brian and board list).

Best,
Markus



-- Forwarded message -
Von: Brian M Hamlin via Board 
Date: Sa., 4. Dez. 2021, 20:01
Subject: Re: [Board] OSGeo budget 2021
To: ...
Cc: , osgeo-board List 

OSGeo "budget-related" ?  (see the subject line)

  http://opensource.indeedeng.io/FOSS-Contributor-Fund/##
<--

"best from the West"

  --Brian M Hamlin/  MAPLABS  /  Berkeley, Calif.
___
Board mailing list
bo...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/board
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] First draft of call for student grants

[Markus Neteler]

Hi all,

Some comments inline:

On Tue, Nov 16, 2021 at 1:37 PM Huidae Cho  wrote:

> On Tue, Nov 16, 2021 at 5:40 AM Moritz Lennert <
> mlenn...@club.worldonline.be> wrote:
>
>> Thanks, Vero, for your feedback (and Vaclav for the direct change) !
>>
>
I took liberty to add some links (what "PSC" and "PR" is may be not that
obvious...).

Here are some comments/replies.
>>
>> Am 15.11.2021 21:35 schrieb Veronica Andreo:
>> > This is great Moritz! Thanks for taking the lead on this and drafting
>> > the call!
>>
>
Thanks a lot!

> Here are my comments/questions:
>> > - _"be eligible to work in the country in which they reside" -->
>> > _maybe this is related to them having a tax number or bank account, no
>> > idea.
>>
>> I think it is more linked to the fact that GSoC pays for a student job,
>> no ? Or is it also considered a grant ?
>>
>
> GSoC is considered an independent (contract?) job according to their FAQ
> [1]?
>
> [1]
> https://developers.google.com/open-source/gsoc/faq#is_gsoc_considered_an_internship_a_job_or_any_form_of_employment
>
> Since our grants are also "service"-based payments, probably, we should
> use the same category for tax purposes?
>
> Another idea is to use the money for "competitions" where students submit
> their "completed" work and we pick a couple of their projects for monetary
> rewards. Not sure about tax implications in this case. It's more of a prize
> than a pay.
>

Grant vs award vs job probably also depends on where the bank account
resides fiscally.
Now that we are on https://opencollective.com/grass this may matter/help.

[...]


> I think we need different requirements for different categories. Software
> development needs core developers or at least add-on devs depending on the
> repository, I think.
> * Software development
> * Improvement of the manual documentation
> * Educational resources including workshop manuals, user guides, Jupyter
> notebooks
> * etc.
>

I'd agree here.


[...]

> > - In the how to apply section: email with proof of eligibility should
>> > be sent to some of us privately I think for data privacy reasons (?).
>>
>> Yes, that's why I put XYZ as the address. Maybe we can create an
>> @osgeo.org address for this ?
>>
>
> Sounds good.
>

I can do that (it would be an email reflector to XYZ then:
grass-[grants|awards]@osgeo.org --> some...@from.our.team.something


> Would be nice to ask them to introduce themselves to the community
>> > too, no? Probably once accepted.
>>
>> Yes, but not sure this needs to be in the grant procedure description.
>>
>
> I think it's a good idea to promote this grant program. It can be
> considered a letter of interest. Maybe emails with a prefix like "[STUDENT
> GRANTS]".
>

Sounds good.

[...]


>
>> > - Final report: the report in the wiki seems fine to me, could also be
>> > the trac wiki where all the GSoC reports live too.
>>
>> I agree, but this raises the more fundamental question whether in the
>> long run we want to continue with two wikis, especially with the trac
>> wiki, knowing that we do not use trac for anything else anymore.
>>
>
> I agree. We should somehow consolidate the two wikis.
>

I also agree.

Markus


> El lun, 15 nov 2021 a las 13:07, Moritz Lennert
> > () escribió:
> >
> >> Dear all,
> >>
> >> Following the discussions at today's PSC I've written a first draft
> >> of a
> >> call for student grants:
> >> https://grasswiki.osgeo.org/wiki/Student_Grants [1].
> >>
> >> Several points still need clarification (see comments in
> >> [brackets]).
> >> Feel free to edit as you see necessary.
> >>
> >> If we really want to go forward with this still before Christmas,
> >> then
> >> we need to have the final version ready by end of next week the
> >> latest.
> >>
> >> Enjoy your weekend !
> >> Moritz
> >>
> >> ___
> >> grass-psc mailing list
> >> grass-psc@lists.osgeo.org
> >> https://lists.osgeo.org/mailman/listinfo/grass-psc [2]
> >
> >
> > Links:
> > --
> > [1] https://grasswiki.osgeo.org/wiki/Student_Grants
> > [2] 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

[GRASS-PSC] PSC meeting minutes (May 11, 2021)

[Markus Neteler]

Dear all,

(sorry for rare cross-posting)

Please have a look at the  PSC meeting minutes  of our recent meeting
on May 11, 2021:
https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210511

Topics covered:
- GRASS GIS 8 release schedule
- GRASS GIS 7.8.6 release schedule
- Management of addons
- Reorganizing addons repo
- Sponsoring
- RFC C/C++ version
- Draft RFC Python version support
- Current request on grass-web to make i.segment a stand-alone software
- Marketing / presence in social media
- Upcoming conferences
- GSoC 2021

Best,
Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Accounting and organization of sponsorship

[Markus Neteler]

Hi,

Luca Delucchi  schrieb am Do., 25. März 2021, 07:10:

> Hi all,
>
> On Tue, 16 Mar 2021 at 20:13, Veronica Andreo 
> wrote:
> >
> > I was inspecting a bit which other organizations are there, and I found
> many well known companies and NGOs (See for example:
> https://opencollective.com/babel). Furthermore, it seems it also allows
> for recurring contributions with different categories.
> >
>
> I just discovered that OpenLayers is already in OpenCollective, maybe
> we can contact them
> https://opencollective.com/openlayers



I had done this already weeks ago but didn't receive an answer.

We may try again, though!

Markus


> >
> > Cheers,
> > Vero
> >
>
>
> --
> ciao
> Luca
>
> www.lucadelu.org
> ___
> 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] [motion] Language standard support for C and C++ in GRASS GIS

[Markus Neteler]

On Mon, Mar 22, 2021 at 8:57 PM Veronica Andreo  wrote:
> Dear PSC,
>
> There has been a very active discussion regarding minimum requirements of 
> programming languages standards for GRASS 8, which eventually lead to an RFC. 
> Thanks Nicklas for your work in writing the first draft and all those who 
> contributed their knowledge and opinions into the discussion!
>
> This motion is to vote for RFC 7 
> (https://trac.osgeo.org/grass/wiki/RFC/7_LanguageStandardsSupport) that sets 
> the language standard support for C and C++ in GRASS GIS.
>
> Motion:
> I hereby start with a +1
>
> Best,
> Vero

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

Re: [GRASS-PSC] [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

[Markus Neteler]

Hi,

On Tue, Mar 16, 2021 at 8:30 PM Veronica Andreo  wrote:
>
> Hi everyone
>
> Thanks for all the feedback.
>
> In practical terms then, shall we:
> - remove all python references from the Language Standards draft RFC [0] and 
> vote only for C/C++, while creating a separate RFC for the minimum python 
> version?
> - add a formula that sets on which pace the minimum supported python version 
> will change to the Language Standards draft RFC [0] and vote for everything 
> altogether?

For Python support, it is worth looking at the GDAL RFC 77 which
includes useful tables and links:
- https://gdal.org/development/rfc/rfc77_drop_python2_support.html

esp.:
- 
https://endoflife.date/python#:~:text=The%20support%20for%20Python%202.7,dropping%20support%20for%20Python%202.7

Useful is also
- https://repology.org/project/python/versions

With respect to the pace of periodic review and updating of the
language standards support I believe that we need that at the pace of
sub-major releases (e.g., 7.8 -> 7.9). Just look back at the major
releases (https://grass.osgeo.org/about/history/releases/) we observe
quite some time span:

- (2021) GRASS GIS 8.0.0
- 2015 GRASS GIS 7.0.0
- 2005 GRASS GIS 6.0.0
- 2002 GRASS GIS 5.0.0
- 1991 GRASS 4.0
- 1988 GRASS 3.0
- 1987 GRASS 2.0
- 1984 GRASS 1.0

Hence sub-major releases might be the way to go.

Markus

> [0] https://trac.osgeo.org/grass/wiki/RFC/7_LanguageStandardsSupport
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

[Markus Neteler]

Hi all,

On Tue, Mar 2, 2021 at 8:15 AM Nicklas Larsson via grass-dev
 wrote:
>
> Good, Anna, you brought up this question on regular update of Python version 
> support. I deliberately left that part out of the draft for setting/updating 
> language standards, as I would argue it deserves a RFC on its own.

I agree to both:

- we need to find a formula with our release rhythm and the oldest
still supported Python version,
- and yes, please let's separate this out into a different discussion
(RFC if needed).

I.e., one C/C++ RFC and one Python RFC.

> A RFC should't be updatable, but may be overridden, partly or completely, 
> with a new RFC. Adopting adherence to a new C or C++ standard will most 
> likely be a quite rare business and should be dealt with a new RFC.

I agree to that, as it would become a moving target otherwise.

> The discussed approach, following the Python versions life-cycle, could 
> possibly look a little different, however the forms and modes for this should 
> be established likewise with a RFC.
>
> If we agree now, to set Python 3.6 as a minimum, we have roughly six months 
> to work out such a procedure. I’m glad to assist to this in, say around, 
> October, in time for the 3.6 retirement.

Let me suggest to separate Python out into another discussion.
The pace of C/++ standards and that of Python versions are quite
different and not easy to handle in a single RFC.

Just my 0.02 cents,

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

[GRASS-PSC] Fwd: [OSGeo-Discuss] Fwd: [Season of Docs - Announcements] The 2021 Season of Docs application for organizations is open!

[Markus Neteler]

FYI - maybe a way to improve our docs!


-- Forwarded message -
From: Cameron Shorter 
Date: Wed, Feb 17, 2021 at 11:49 AM
Subject: [OSGeo-Discuss] Fwd: [Season of Docs - Announcements] The 2021
Season of Docs application for organizations is open!
To: OSGeo Discussions 


Hi OSGeo folks,
Is anyone in OSGeo interested in applying for a Google Season of Docs grant?
OSGeo did get sponsored in 2019, but didn't apply in 2020.
If someone wants to pursue it you might want to look back through our
previous ideas list:
https://wiki.osgeo.org/wiki/Season_of_Docs_Ideas_2019
I'm happy to chat with anyone who might be interested in acting as a mentor
for this program. (I won't be involved in an OSGeo bid this year, but I can
share what I learned from doing it before.)


-- Forwarded message -
From: Season of Docs - Announce 
Date: Wed, 10 Feb 2021 at 05:09
Subject: [Season of Docs - Announcements] The 2021 Season of Docs
application for organizations is open!
To: Season of Docs - Announce 


We’re delighted to announce Season of Docs
 2021!

In 2021 the Season of Docs program will continue to support better
documentation in open source and provide opportunities for skilled
technical writers to gain open source experience. In addition, building on
what we’ve learned from the successful 2019 and 2021 projects, we’re
expanding our focus to include learning about effective metrics for
evaluating open source documentation.
What are the 2021 program changes?

Season of Docs 2021 will allow open source organizations to apply for a
grant, based on their documentation needs. If selected, open source
organizations will use their grant to hire a technical writer directly to
complete their documentation project. Organizations will have up to six
months to complete their documentation project. Keep reading for more
information about the organization application or visit the Season of Docs
site .

Technical writers interested in working with accepted open source
organizations will be able to share their contact information via the Season
of Docs GitHub repository , or
submit proposals directly to the organizations, and will not need to submit
a formal application through Season of Docs.

Participating organizations will help broaden our understanding of
effective documentation practices and metrics in open source by submitting
a final case study upon completion of the program. The project case study
will outline the problem the documentation project was intended to solve,
what metrics were used to judge the effectiveness of the documentation, and
what the organization learned for the future. All the project case studies
will be published on the Season of Docs site at the end of the program.
Organization Applications

Organization applications are now open! The deadline to apply is March 26,
2021 at 18:00 UTC.

To apply, first read the guidelines for creating an organization application

on the Season of Docs website.

Take a look at the examples of project ideas
, then
create a project proposal based on your open source project’s actual
documentation needs. Your goal is to attract technical writers to your
organization, making them feel comfortable about approaching the
organization and excited about what they can achieve.

Organizations can submit their applications here: http://goo.gle/3qVxArQ
.
Organization applications close on March 26 at 18:00 UTC.

Technical writers interested in participating in the 2021 Season of Docs
should read our guide for technical writers
 on
the Season of Docs website.

Please do tweet and blog about Season of Docs if you’d like to share the
news. We want as many people to know about it as possible. We’ve provided
logos that you can download and some example content on the press page
.

If you have any questions about the program, please email us at
season-of-d...@google.com.

We’re looking forward to another productive year of the Season of Docs
program!

Best regards,

Kassandra Dhillon, Erin McKean, and the Season of Docs team

-- 
You received this message because you are subscribed to the Google Groups
"Season of Docs - Announce" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to season-of-docs-announce+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/season-of-docs-announce/9a569457-fcfb-4383-9827-57bc037bc846n%40googlegroups.com

Re: [GRASS-PSC] question about online voting system

[Markus Neteler]

On Mon, Feb 15, 2021 at 9:25 PM Michael Barton  wrote:
>
> Thanks Markus.
>
> I had thought it was LimeSurvey, but when we initially checked the site says 
> that the free version is limited to only 25 recipients. So I guess that OSGeo 
> is using the Community Edition (which I found after some digging).

The technical stuff is known by OSGeo SAC:
https://wiki.osgeo.org/wiki/SAC_Service_Status#limesurvey
(the link therein points to a password protected page to which I have access)

Checking it I ended up after some search here (seems LimeSurvey has
restructured their site without redirects):
https://account.limesurvey.org/de/lts-releases-download

About any limit I don't know, maybe other SAC members do.

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

Re: [GRASS-PSC] question about online voting system

[Markus Neteler]

Michael,

In OSGeo we have the https://limesurvey.osgeo.org/ server doing the job
(https://en.wikipedia.org/wiki/LimeSurvey).

HTH
Markus

On Mon, Feb 15, 2021 at 7:00 PM Michael Barton  wrote:
>
> Markus,
>
> I wanted to find out more about the online voting system GRASS used for it s 
> recent PSC elections. At CoMSES.Net we used Survey Monkey but are bumping up 
> against the limit for free use. What did GRASS use? It seemed like it worked 
> well.
>
> Thanks
> Michael
> _
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Director, Network for Computational Modeling in Social & Ecological Sciences
> Associate Director, School of Complex Adaptive Systems
> Professor, School of Human Evolution & Social Change
> Arizona State University
> Tempe, AZ  85287-2402
> USA
>
> voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
> www: http://shesc.asu.edu, https://complexity.asu.edu, 
> http://www.public.asu.edu/~cmbarton
>


-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

[Markus Neteler]

On Thu, Feb 11, 2021 at 9:14 PM Michael Barton  wrote:
>
> For some reason, I'm not seeing the new RFC at 
> https://trac.osgeo.org/grass/wiki/RFC

It still needs to be written :-)

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

Re: [GRASS-PSC] [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

[Markus Neteler]

On Thu, Feb 11, 2021 at 1:29 PM Nicklas Larsson via grass-dev
 wrote:
>
> Moritz,
>
> I'd be honoured!
> I will put it on GRASS Wiki [1] if you don't have another suggestion and 
> notify here when done.

Excellent!

BTW: a similar discussion just about to start:

"What are going to be the set of compilers that are supported and how old?"
https://github.com/OSGeo/shapelib/issues/23

That issue contains links to related documents (GDAL etc., maybe of
interest here, too).

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

Re: [GRASS-PSC] Proposed mail: Support GRASS GIS financially !

[Markus Neteler]

Hi,

Looks fine with the changes, thanks!

Markus

On Thu, Feb 4, 2021 at 5:53 PM Huidae Cho  wrote:
>
> Moritz,
>
> Yes, that link should work. The table of contents looks better than four 
> individual links.
>
> Huidae
>
>
> On Thu, Feb 4, 2021 at 11:48 AM Moritz Lennert  
> wrote:
>>
>> On 4/02/21 14:38, Huidae Cho wrote:
>> > Hi Moritz,
>> >
>> > It looks good and I agree with Vero. I just have one more comment. Why
>> > don't we add direct links to companies, associations, and institutions?
>> > Since the individual list is long, which is great, that single link kind
>> > of gave me an impression that it's only for individuals? I just had to
>> > scroll down to find other entities, which, I assume, can contribute more
>> > significant amounts. It'll also help potential individual sponsors see
>> > that GRASS also has received/is receiving corporate sponsorship, and
>> > feel the significance of the project.
>> >
>> > Other than that, +1 from me.
>> >
>> > Best,
>> > Huidae
>> >
>> > On Thu, Feb 4, 2021 at 7:42 AM Veronica Andreo > > <mailto:veroand...@gmail.com>> wrote:
>> >
>> > Hi Moritz
>> >
>> > Thanks for this initiative! I really like it!
>> >
>> > Only minor things:
>> > - Since we sign as PSC, then I'd replace "I" at the beginning with "we"
>> > - remove the word "some" from points 2 and 4
>> >
>> > For the rest, I have no objections at all :)
>> > +1 from my side
>> >
>> > Cheers,
>> > Vero
>> >
>>
>> Thanks Vero, Huidae and Jeff for all your corrections !
>>
>> Concerning the link, it should actually have been
>>
>> https://grasswiki.osgeo.org/wiki/Sponsors
>>
>> Is that better ?
>>
>> Moritz
>
>
>
> --
> Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大
> GRASS GIS Developer
> https://idea.isnew.info
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc



-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS-announce] [GRASS GIS Elections 2020] Voting phase closed, presentation of results

[Markus Neteler]

Dear GRASS community,

First of all, thanks for the confidence, I feel honored to continue to
be part of the PSC.
And of course a big thank-you to our Chief Return Officer (CRO),
Hernán De Angelis, for running the election!

The new PSC shall gather soon in a first meeting and decide the new
PSC chairperson.
We shall also write an announcement for the GRASS GIS web site about
the result of the PSC election.

Best,
Markus

PS: Trac page: https://trac.osgeo.org/grass/wiki/PSC/Election2020#Results

On Mon, Jan 25, 2021 at 1:30 PM Chief Return Officer (CRO) - GRASS GIS
election 2020  wrote:
>
> Dear members of the GRASS GIS community,
>
> The voting phase of the GRASS GIS Election 2020 is now finished. Out of 245 
> registered voters, 98 completed the survey. The results are shown below and 
> are now available in the Trac Wiki.
>
> Voting result (ranking, name, number of votes):
>
>  1. Markus Neteler 95
>  2. Anna Petrášová88
>  3. Helena Mitasova   86
>  4. Martin Landa83
>  5. Verónica Andreo  76
>  6. Moritz Lennert 74
>  7. Vaclav Petras  68
>  8. Michael Barton58
>  9. Huidae Cho  56
> 10. Helmut Kudrnovsky 55
> 11. Peter Löwe  52
> 12. Māris Nartišs   47
> 13. Stefan Blumentrath 44
>
>
> The new PSC is then composed of the following 9 members:
>
>  1. Markus Neteler 95
>  2. Anna Petrášová88
>  3. Helena Mitasova  86
>  4. Martin Landa83
>  5. Verónica Andreo   76
>  6. Moritz Lennert  74
>  7. Vaclav Petras   68
>  8. Michael Barton 58
>  9. Huidae Cho  56
>
>
> Regards,
>
>
> Hernán
>
> Chief Return Officer (CRO)
>
> ___
> grass-announce mailing list
> grass-annou...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-announce
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Request for write access to GRASS addons repository

[Markus Neteler]

Dear Guido,

On Thu, Jan 21, 2021 at 8:21 AM Guido Riembauer  wrote:
>
> Dear GRASS project steering committee,
>
> I would like to ask for write access to the GRASS addons repository,
> having read and accepted the Legal aspects of code contributions (RFC2).
> I suggest Markus Neteler, who is also my supervisor at mundialis, to be
> my mentor for this purpose. My GitHub username is griembauer, I am
> mainly proficient in Python and could gather some experience in writing
> GRASS addons especially for remote sensing and image analysis.
>
> Thank you very much,
>
> Guido Riembauer

Welcome to GRASS GIS Addons - I have sent an invitation via GitHub to
you (please accept it to activate your account) and added your record
to "grass-addons/contributors.csv" (change [1]).

Here some hints: Please, prior to submission, check your code and
manual contributions against the rules defined in the document
Submitting (and its subsections):

https://trac.osgeo.org/grass/wiki/Submitting
--> Submitting rules

and please also take a look at
https://github.com/OSGeo/grass/blob/master/CONTRIBUTING.md

This ensures a smooth integration into the standard GRASS code base
and avoids portability problems.

The "What's next" we addressed here:
https://trac.osgeo.org/grass/wiki/HowToContribute#Thenwhat

Looking forward to your future contributions!

Happy coding,
Markus

[1] 
https://github.com/OSGeo/grass-addons/commit/9383b955eac9a5cf9abb319bbceb6b3b732bf20b

--
Markus Neteler
GRASS GIS PSC Chair
https://grass.osgeo.org
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS GIS PSC Elections 2020] Invitation to vote, reminder

[Markus Neteler]

On Mon, Jan 18, 2021 at 2:23 PM Ondřej Pešek  wrote:
> po 18. 1. 2021 v 13:19 odesílatel Moritz Lennert 
>  napsal:
...
>> Could it be that the list of voters that you uploaded into the system 
>> contains duplicates ?

Yes and partially hard to catch.

> All my invitations differed in the person to whom they were addressed. All of 
> them were me, though: Ondřej, Ondrej, ondrej, pesekon2. Maybe this info could 
> be helpful.
> I'm happy that my four personalities have finally found some friends, but I'm 
> more used to the fact that I'm the only one who actually talks with them.

I suggest that we clean up and keep the list as predefined for the
next election. And then only  add new voters who joined the community
after 12/2020.

Markus

PS: got many, used one invitation only.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] 2021 GRASS GIS budget request

[Markus Neteler]

Dear OSGeo Board,

The PSC has drafted the following budget request:
https://wiki.osgeo.org/wiki/GRASS_GIS_Budget_2021

with a focus on microgrants for bugfixing and documentation and (with
some home) for in-person sprints.

If you have any questions, please let us know.

Regards,
Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [Board] [OSGeo-Discuss] OSGeo Budget 2021

[Markus Neteler]

PSC,

First of all, thanks to Moritz for his support with cleaning up the budget.

I have slightly expanded the description herein:
https://wiki.osgeo.org/wiki/GRASS_GIS_Budget_2021

Please check - by today I have to send this request as an email to the
OSGeo board list.

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

Re: [GRASS-PSC] [Board] [OSGeo-Discuss] OSGeo Budget 2021

[Markus Neteler]

On Thu, Jan 14, 2021 at 9:30 AM Moritz Lennert
 wrote:
> On 13/01/21 23:37, Markus Neteler wrote:
...
> > I created a ODS table in the nextcloud of OSGeo for both 2020 and 2021:
> > https://nextcloud.osgeo.org/s/dKXfqq4QkMmSkB5
...
> > https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2021
> >
> > and OSGeo request put here:
> > https://wiki.osgeo.org/wiki/OSGeo_Budget_2021#OSGeo_Projects
> >
> > Please speak up if anyone disagrees.
>
> There's a bit of a mix-up between accounts (past income) and budget
> (planned income).

OK, thanks for the clarification (below).

> - The total amount of money we carry over from 2020 (aka "Surplus 2020")
> is 1902,18€, which is the sum of the 1413,27€ currently in the bank
> account and the 488,91€ currently in the PayPal money pool.
>
> - In 2020 we only got 290€ in donations into that money pool.

(OT: seems we need to advertise it better)

> - So in the budget 2021 we need to decide what our target for donations
> is. As a reminder, in 2019 we managed to collect over 1000€ in donations
> but that was linked to specific drive for the web site. As OSGeo paid
> for the website, we still have most of that money left (minus some that
> was spent for sprints). I would think that if we are more proactive for
> donations we should be able to at double last year's amount and so we
> could put in a target of at least 500€ in the 2021 budget.
>
> - This is a budget, and so it also contains some elements of hope. I
> think we should foresee money for in-person sprints, which might become
> possible again in the second semester of 2021. If we can't do them,
> we'll save that money, but we should at least budget the option. In
> 2019, the main sprint cost about 1000€ with roughly half for travelling
> and half for other costs, a second smaller sprint was about 500€. So I
> added that. If we are able to organise these sprints, we still would end
> up with a surplus at the end of the year, even if we do not collect any
> donations, so I think we can take the "risk" of budgeting them.
>
> This also allows to show that we do not only rely on OSGeo for the
> funding, but use our own money as well.

Yes, fully agreed.

> I've gone ahead to change both the file in Nextcloud and the wiki (do we
> really need both ? can't we just link from the wiki to a read-only
> version of the Nextcloud file ?), but please feel free to revert if you
> disagree.

Thanks for the update.
And yes, just linking from the wiki to a read-only version of the
Nextcloud table is preferred (filling in Wiki tables isn't that much
of fun).

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

[GRASS-PSC] Statement Markus Neteler

[Markus Neteler]

First of all, thanks for the nomination.

After starting to use GRASS GIS as a student in 1993, in early 1998 I
saw the need to set up a "European GRASS site" at the University of
Hannover, which quickly developed into an international development
team. Since 1998 I have maintained the various site installations
(Hannover, Trento; then USA, mainly together with Martin Landa),
fortunately today based on hugo. While in1998 I was still doing the
source code management manually (the "patch by email" system, so to
speak), then at the end of 1999 we switched first to CVS, then SVN and
now finally to git/GitHub. I'm very happy about the git migration, as
we are increasingly seeing new developers and more contributions. I
also find the (automated) code quality tests great.

My project activities include presenting at conferences, some
teaching, code sprint participation, bug fixing, user support,
infrastructure management, co-maintaining the Twitter account, release
management, project funding, etc. As before in my research group in
Italy, also in my company mundialis we stick to open source software
and donate in-kind development hours to OSGeo (i.e. developer hours
leading to code contributions: new GRASS GIS addons, fixes and
continuation and extension of actinia, originally developed by Sören
Gebbert). I am co-founder of GRASS GIS e.V. (today FOSSGIS), GFOSS.it
and OSGeo.

I believe that the new PSC could benefit from different members taking
on roles to better handle the tasks at hand, (see also the old page:
https://trac.osgeo.org/grass/wiki/PSC/Roles)

With my diverse interests, I would be interested in sharing my
experience in project management (but not necessarily as the
chairperson!), contact with business, infrastructure management, and
financial matters. For sure I am happy to support new faces in the
PSC, being elected or not. I would be happy to see as much as possible
implemented from the PSC agenda, perhaps with frequent meetings to
keep the pace. And more outreach and marketing, to highlight the
powerful software and its beautiful community I enjoy for decades!

Best wishes,

Markus

--
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
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] [Board] [OSGeo-Discuss] OSGeo Budget 2021

[Markus Neteler]

On Wed, Jan 13, 2021 at 11:30 AM Luca Delucchi  wrote:
> On Wed, 13 Jan 2021 at 10:19, Markus Neteler  wrote:
...
> > Then we can use similar figures and leave out physical meetings.
> >
> But also other expenses are related to physical meetings, probably
> this year will be difficult to meet again.
> This year I would ask less money to OSGeo, also because there was no
> money back from FOSS4G 2020 and this year is still a question marker

Yes, agreed.

Today Vero and I went through the budget of 2020 and cleaned it up.

I created a ODS table in the nextcloud of OSGeo for both 2020 and 2021:
https://nextcloud.osgeo.org/s/dKXfqq4QkMmSkB5

> > Of course I'd be grateful to receive suggestions and ideas.
> >
> In the case could organize something like microgrants for translation,
> documentation or communication?

Great idea: added to the draft budget.

See
https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2021

and OSGeo request put here:
https://wiki.osgeo.org/wiki/OSGeo_Budget_2021#OSGeo_Projects

Please speak up if anyone disagrees.

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] [Board] [OSGeo-Discuss] OSGeo Budget 2021

[Markus Neteler]

PSC,

The budget meeting on 18 January 2021, so  I'd rather proceed with
drafting the budget:

https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2021

I would need an overview of what is leftover from 2020 (Martin, Moritz?).
Then we can use similar figures and leave out physical meetings.

Of course I'd be grateful to receive suggestions and ideas.

Markus

On Wed, Dec 30, 2020 at 12:19 AM Michael Barton  wrote:
>
> Any suggestions? I suspect that in-person events will still be risky for at 
> least the first half of 2021.
>
> Michael
> __
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Director, Network for Computational Modeling in Social & Ecological Sciences
> Associate Director, School of Complex Adaptive Systems
> Professor, School of Human Evolution & Social Change
> Arizona State University
> Tempe, AZ  85287-2402
> USA

On Tue, Dec 29, 2020 at 10:08 PM Markus Neteler  wrote:
>
> Dear PSC,
>
> Budget time :-)
> Please take a look at Angelos' email.
>
> thanks
> Markus
>
> PS: I have created an (empty) draft:
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2021
>
> -- Forwarded message -
> From: Angelos Tzotsos 
> Date: Tue, Dec 29, 2020 at 10:35 AM
> Subject: [Board] [OSGeo-Discuss] OSGeo Budget 2021
> To: OSGeo Discussions 
> Cc: OSGeo Board , proje...@lists.osgeo.org
> 
>
>
> Dear OSGeo project members and committees,
>
> Over the previous years, OSGeo has been proud to support a growing
> number of project events, such as community/code sprints, developer
> meetings, and user conferences. As a result of the COVID-19 pandemic,
> most OSGeo events in 2020 were held as virtual events.
>
> OSGeo is reaching out to all committees, including Project Steering
> Committees, to help plan our budget for 2021.
>
> In 2020, the Board assigned an initial amount of 2000 USD to all
> graduated projects who have reported to the Board the last 12 months
> (e.g. during the AGM or directly to a Board meeting). This year the
> Board is planning to continue to offer a budget to all graduated
> projects with the exact amount to be determined.
>
> Due to cancellation of events in 2020, we are not in a position to
> allocate and spend as much as we did in previous years.
>
> To help navigate the uncertainties ahead in 2021, the Board is planning
> to have a budget meeting on 18 January 2021 to review 2020 expenditures,
> sponsorship, and make financial decisions for the 2021 budget.
>
> Please send your detailed requests for approval (see detailed budget
> requests from 2020 e.g.
> https://wiki.osgeo.org/wiki/GeoServer_Budget_2020
> <https://wiki.osgeo.org/wiki/GeoServer_Budget_2020>)
>
> We would like to ask you to help us with budget proposals to assist your
> project. This will help us set aside a realistic amount of funding.
>
> Please add your project info to the budget draft at:
>
> https://wiki.osgeo.org/wiki/OSGeo_Budget_2021
> <https://wiki.osgeo.org/wiki/OSGeo_Budget_2021>
>
> ideally by 17 January 2021 in advance of our next Board meeting.
>
> When making a budget request please keep in mind the vision and goals of
> our Foundation, along with any obligations you wish to meet.
>
> Thank you.
>
> On behalf of the OSGeo Board,
>
> Angelos
>
>
> --
> Angelos Tzotsos, PhD
> President
> Open Source Geospatial Foundation
> http://users.ntua.gr/tzotsos
>
> ___
> Board mailing list
> bo...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/board
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] Fwd: [Board] [OSGeo-Discuss] OSGeo Budget 2021

[Markus Neteler]

Dear PSC,

Budget time :-)
Please take a look at Angelos' email.

thanks
Markus

PS: I have created an (empty) draft:
https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2021

-- Forwarded message -
From: Angelos Tzotsos 
Date: Tue, Dec 29, 2020 at 10:35 AM
Subject: [Board] [OSGeo-Discuss] OSGeo Budget 2021
To: OSGeo Discussions 
Cc: OSGeo Board , proje...@lists.osgeo.org



Dear OSGeo project members and committees,

Over the previous years, OSGeo has been proud to support a growing
number of project events, such as community/code sprints, developer
meetings, and user conferences. As a result of the COVID-19 pandemic,
most OSGeo events in 2020 were held as virtual events.

OSGeo is reaching out to all committees, including Project Steering
Committees, to help plan our budget for 2021.

In 2020, the Board assigned an initial amount of 2000 USD to all
graduated projects who have reported to the Board the last 12 months
(e.g. during the AGM or directly to a Board meeting). This year the
Board is planning to continue to offer a budget to all graduated
projects with the exact amount to be determined.

Due to cancellation of events in 2020, we are not in a position to
allocate and spend as much as we did in previous years.

To help navigate the uncertainties ahead in 2021, the Board is planning
to have a budget meeting on 18 January 2021 to review 2020 expenditures,
sponsorship, and make financial decisions for the 2021 budget.

Please send your detailed requests for approval (see detailed budget
requests from 2020 e.g.
https://wiki.osgeo.org/wiki/GeoServer_Budget_2020
)

We would like to ask you to help us with budget proposals to assist your
project. This will help us set aside a realistic amount of funding.

Please add your project info to the budget draft at:

https://wiki.osgeo.org/wiki/OSGeo_Budget_2021


ideally by 17 January 2021 in advance of our next Board meeting.

When making a budget request please keep in mind the vision and goals of
our Foundation, along with any obligations you wish to meet.

Thank you.

On behalf of the OSGeo Board,

Angelos


--
Angelos Tzotsos, PhD
President
Open Source Geospatial Foundation
http://users.ntua.gr/tzotsos

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

Re: [GRASS-PSC] Proposing Nicklas Larsson as a new core developer

[Markus Neteler]

On Wed, Dec 23, 2020 at 10:19 PM Nicklas Larsson  wrote:
>
> Dear PSC, Markus,
>
> I'm deeply honoured and really delighted for your confidence.
>
> I have read and accept the "RFC 2: Legal aspects of code contributions".
>
> Best,
> Nicklas

Great!

I have now activated your "nilason" account in GitHub for full access
to GRASS GIS core/addons/promo/web and added you to the
'contributors.csv' file.

Best,
Markus


--
Markus Neteler
GRASS GIS PSC Chair
http://grass.osgeo.org
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Proposing Nicklas Larsson as a new core developer

[Markus Neteler]

Dear PSC, Nicklas,

On Wed, Dec 16, 2020 at 3:19 PM Markus Neteler  wrote:
>
> Dear PSC,
>
> Let me propose Nicklas Larsson (https://github.com/nilason) to be
> accepted as a new core developer.
>
> Nicklas has impressively contributed to various parts of the source code:
>
> - in "core": as of today 40 accepted/approved pull requests in the
> main repo [1],
> - in "addons": as of today 1 accepted pull requests in addons [2],
> - and he offers support, especially for the packaging on Mac.
>
> I have asked him off-list and he would be happy to join the core team
> with write access to the main repository.
>
> According to RFC1 [1] all PSC members need to vote on this proposal.

The result:

Moritz Lennert +1
Michael Barton +1
Anna Petrasova +1
Helena Mitasova +1
Margherita Di Leo +1
Vaclav Petras +1
Martin Landa +1
Peter Loewe +1
Markus Neteler +1

I declare the motion passed.

Congratulations, Nicklas!

The next step, before activating the write access, is the acceptance of RFC2:
Nicklas, please state (in an email as a reply) that you have read and
will adhere to the legal aspects of code contributions (document "RFC
2: Legal aspects of code contributions" [4]).

Thanks,
Markus

[4] https://trac.osgeo.org/grass/wiki/RFC/2_LegalAspectsOfCodeContributions

--
Markus Neteler
GRASS GIS PSC Chair
http://grass.osgeo.org


> [1] 
> https://github.com/OSGeo/grass/pulls?q=is%3Apr+is%3Aclosed+author%3Anilason
> [2] 
> https://github.com/OSGeo/grass-addons/pulls?q=is%3Apr+is%3Aclosed+author%3Anilason
> [3] https://trac.osgeo.org/grass/wiki/RFC/1_ProjectSteeringCommitteeGuidelines
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS GIS Elections 2020] Current members of the PSC willing to stand up for reelection?

[Markus Neteler]

On Tue, Dec 22, 2020 at 12:34 PM Chief Return Officer (CRO) - GRASS
GIS election 2020  wrote:
> On 2020-12-22 12:08, Markus Neteler wrote:
> > On Tue, Dec 22, 2020 at 10:28 AM Moritz Lennert
...
> >> But I agree with Hernán that we should have discussed this earlier.
> > Still it is not too late, say, "nothing lost".
>
> Marcus, what do you say on this?

What I tried to say is that we might quickly modify our procedure to
Helli's suggestion as no PSC member had answered yet (hence, no
conflict arises so far).

> What do other PSC members say? Shall
> the PSC make a consensus on these proposals? In that case it would be
> nice to have the matter resolved rather sooner than later.

Definitely.

@PSC: do you agree to change our procedure to

"GRASS GIS PSC members are to be nominated for re-election in the same
way by the community as possible new candidates"

?

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

Re: [GRASS-PSC] [GRASS GIS Elections 2020] Current members of the PSC willing to stand up for reelection?

[Markus Neteler]

PSC, all,

On Tue, Dec 22, 2020 at 10:28 AM Moritz Lennert
 wrote:
> Am 22. Dezember 2020 09:24:17 MEZ schrieb "Chief Return Officer (CRO) - GRASS 
> GIS election 2020" :
> >On 2020-12-21 22:20, Helmut Kudrnovsky wrote:
> >> wouldn't it be more transparent if current GRASS GIS PSC members are
> >> nominated for re-election in the same way by the community as possible new
> >> candidates?
> >>
> >>
> >Thanks for your input, Helmut. The election wiki is not very clear about
> >this, it only states that "current PSC members will be asked if they
> >wish to stand as a candidate for the upcoming election" without any
> >further clarification. This is definitely a grey area worth developing.
> >I agree your proposal is a good idea, but it is possibly not my role to
> >decide on this. Also it is possibly late as we we have already launched
> >the nominations.
> >
> >I believe this is something the PSC can decide:
> >
> >1. should current PSC members have the right to stand up for reelection
> >without explicit nomination? (current line of action)
> >
> >or
> >
> >2. should current PSC members have to be nominated in the same way as
> >any other member of the community? (we could start right now as no PSC
> >members have yet stand up)
>
> I agree with Helmut and would plead for 2).

I also agree with Helmut and would plead for 2).

> But I agree with Hernán that we should have discussed this earlier.

Still it is not too late, say, "nothing lost".

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

Re: [GRASS-PSC] GRASS GIS Election 2020 Trac Wiki ready

[Markus Neteler]

On Thu, Dec 17, 2020 at 3:00 PM Chief Return Officer (CRO) - GRASS GIS
election 2020  wrote:
>
> I have now prepared the Trac Wiki as far as it can be done at this
> stage. I have even indicated that past some point the wiki is going to
> be updated as the election proceeds.

Thanks for the updates.

> Please, have a look and write back in case you disagree or find eventual
> typos or problems:
>
> https://trac.osgeo.org/grass/wiki/PSC/Election2020
>

We may detail out this point
- "presentation of the candidates"

... perhaps each proposed candidate shall write a few lines about what
they want to achieve in the PSC?

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

Re: [GRASS-PSC] Proposing Tomas Zigo as a new core developer

[Markus Neteler]

Dear Tomas,

On Sun, Nov 29, 2020 at 11:34 PM Markus Neteler  wrote:
...
> I declare the motion passed.
>
> Congratulations Tomáš!
>
> I have activated your "tmszi" account in GitHub for full access to
> GRASS GIS core/addons/promo/web and added you to the
> 'contributors.csv' file.

While it is coming late in the process I'd like one missing formality
from your side:

Please state here, in an email reply that you have read and will
adhere to the legal aspects of code contributions (document "RFC 2:
Legal aspects of code contributions",
https://trac.osgeo.org/grass/wiki/RFC/2_LegalAspectsOfCodeContributions).

Thanks,
Markus

--
Markus Neteler
GRASS GIS PSC Chair
http://grass.osgeo.org
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] 2020 Election wiki - request for comments on details

[Markus Neteler]

On Thu, Dec 17, 2020 at 1:04 PM Moritz Lennert
 wrote:
> On 17/12/20 10:43, Chief Return Officer (CRO) - GRASS GIS election 2020
...
> >> Which tool? How does this work?
...
> I think you can launch the nomination period on the 21. Heliosvoting
> should work. Just log in with your Google account and click "create an
> election".

ok cool.

> For the OSGeo Limesurvey, on https://limesurvey.osgeo.org/ it says
> "Please contact OSGeo CRO ( c...@osgeo.org ) for further assistance.", so
> you could probably just do that.

I had done this yesterday with cro.grass in CC, but no answer so far.
I also asked in IRC to no avail.
So, if Heliosvoting works then maybe we could go for it.

> Personally I like the idea of keeping things within the OSGeo ecosystem,
> and so would privilege that solution, but we shouldn't make this too
> much of an issue.

We can still wait for an answer. As you prefer...

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

Re: [GRASS-PSC] 2020 Election wiki - request for comments on details

[Markus Neteler]

On Wed, Dec 16, 2020 at 7:28 PM Chief Return Officer (CRO) - GRASS GIS
election 2020  wrote:
>
> Comments appreciated, so we can move forward with this. See below.

Comments inline below:

> Thanks
>
> /H.
>
> On 2020-12-16 09:18, Chief Return Officer (CRO) - GRASS GIS election 2020 
> wrote:
>
> Good morning,
>
> I am now set to edit the trac wiki and start defining the process. At this 
> stage I would like us to reach a consensus
> regarding critical parts of the process. This is preliminary, please comment 
> and suggest other options as you consider necessary.
>

To avoid confusion with ASCII emails, here the clean version:

- Number of PSC members to be elected: 9
- Election duration: 2020-12-21 - 2021-01-28
   - Nomination period: 2020-12-21 - 2021-01-11
   - Reflection week: 2021-01-11 - 2021-01-18
   - Voting period: 2021-01-18 - 2021-01-25
   - Latest possible announcement of new PSC: 2021-02-01

> Are these dates reasonable?

To me it sounds reasonable.


> Eligible voters:
>
> - have already posted a pull request to github **(possibly only those PR that 
> have been merged)**

I understood that in addition we want the translators.
- have contributed to Transifex

> Note the second criterion, what about PR:s being merged or not?
>
> Opinions on this?

"PR still open" would be fine for me because it shows interest, an
active contribution and maybe tackles complicated stuff which cannot
be merged quickly.

> From the current wiki drat: Election tool?
>
>  During the Voting period, eligible voters, can vote their preferred
>  candidate(s) via an on-line tool which will protect privacy.
>
> Which tool? How does this work?
>
> O see that https://vote.heliosvoting.org/ was used in 2016. Is this being 
> used in 2020 too? How?

Nikos knows about heliosvoting.
But as Moritz suggests, perhaps we may use
https://limesurvey.osgeo.org - I can try to find out.

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

[GRASS-PSC] Proposing Nicklas Larsson as a new core developer

[Markus Neteler]

Dear PSC,

Let me propose Nicklas Larsson (https://github.com/nilason) to be
accepted as a new core developer.

Nicklas has impressively contributed to various parts of the source code:

- in "core": as of today 40 accepted/approved pull requests in the
main repo [1],
- in "addons": as of today 1 accepted pull requests in addons [2],
- and he offers support, especially for the packaging on Mac.

I have asked him off-list and he would be happy to join the core team
with write access to the main repository.

According to RFC1 [1] all PSC members need to vote on this proposal.

Best,
Markus


[1] https://github.com/OSGeo/grass/pulls?q=is%3Apr+is%3Aclosed+author%3Anilason
[2] 
https://github.com/OSGeo/grass-addons/pulls?q=is%3Apr+is%3Aclosed+author%3Anilason
[3] https://trac.osgeo.org/grass/wiki/RFC/1_ProjectSteeringCommitteeGuidelines
___
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 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

[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

[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

[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

[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

[Markus Neteler]

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?

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]

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

[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

[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] Stepping down

[Markus Neteler]

Dear Margherita,

On Mon, Dec 7, 2020 at 11:50 AM Margherita Di Leo  wrote:
>
> Dear PSC,
>
> I'm currently not currently contributing to the project, also because my work 
> pattern has somehow taken me
> in a different direction. So I'm stepping down from PSC and leaving the slot 
> to more active contributors.
> I'll stick around to this amazing community anyway.
>
> Best of luck
> Cheers,
>
> --
> Margherita Di Leo

Thanks for your email.
As a matter of fact we never defined the "stepping down" procedure -
it is yet an open issue on the
https://trac.osgeo.org/grass/wiki/PSC/Agenda

For example, the terms of the Geoserver PSC
(http://docs.geoserver.org/latest/en/developer/policies/psc.html)
define
- Future PSC members
- Stepping Down
- Dissolution of PSC

... maybe we could learn from them.

I'd appreciate it if you are willing to stay till we have decided the
procedure (could be fast & easy given existing examples in the OSGeo
community).

Please let us know,

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

Re: [GRASS-PSC] Proposing Tomas Zigo as a new core developer

[Markus Neteler]

Dear PSC, Tomáš,

On Fri, Nov 20, 2020 at 11:17 PM Markus Neteler  wrote:
>
> Dear PSC,
>
> Let me propose Tomáš Zigo (https://github.com/tmszi) to be accepted as
> a core developer.
>
> Tomáš has impressively contributed to various parts of the source code:
>
> - in "core": as of today 132 accepted pull requests in the main repo [1],
> - in "addons": as of today 132 accepted pull requests in addons [2],
> - and he offered many more comments on other pull requests and as well
> as in the mailing list.
>
> I have asked him off-list and he would be happy to join the core team
> with write access to the main repository.
>
> According to RFC1 [1] all PSC members need to vote in a separate motion.
>
> Best,
> Markus
>
>
> [1] https://github.com/OSGeo/grass/pulls?q=is%3Apr+is%3Aclosed+author%3Atmszi
> [2] 
> https://github.com/OSGeo/grass-addons/pulls?q=is%3Apr+is%3Aclosed+author%3Atmszi
> [3] https://trac.osgeo.org/grass/wiki/RFC/1_ProjectSteeringCommitteeGuidelines


The result:

Moritz Lennert +1
Michael Barton +1
Anna Petrasova +1
Helena Mitasova +1
Margherita Di Leo +1
Vaclav Petras +1
Martin Landa +1
Peter Loewe +1
Markus Neteler +1

I declare the motion passed.

Congratulations Tomáš!

I have activated your "tmszi" account in GitHub for full access to
GRASS GIS core/addons/promo/web and added you to the
'contributors.csv' file.

Best,
Markus

--
Markus Neteler
GRASS GIS PSC Chair
http://grass.osgeo.org
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] Proposing Tomas Zigo as a new core developer

[Markus Neteler]

Dear PSC,

Let me propose Tomáš Zigo (https://github.com/tmszi) to be accepted as
a core developer.

Tomáš has impressively contributed to various parts of the source code:

- in "core": as of today 132 accepted pull requests in the main repo [1],
- in "addons": as of today 132 accepted pull requests in addons [2],
- and he offered many more comments on other pull requests and as well
as in the mailing list.

I have asked him off-list and he would be happy to join the core team
with write access to the main repository.

According to RFC1 [1] all PSC members need to vote in a separate motion.

Best,
Markus


[1] https://github.com/OSGeo/grass/pulls?q=is%3Apr+is%3Aclosed+author%3Atmszi
[2] 
https://github.com/OSGeo/grass-addons/pulls?q=is%3Apr+is%3Aclosed+author%3Atmszi
[3] https://trac.osgeo.org/grass/wiki/RFC/1_ProjectSteeringCommitteeGuidelines
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Contribution in AddOns

[Markus Neteler]

Hi Allan,

On Mon, Nov 9, 2020 at 9:41 AM Allan Sims  wrote:
>
> Dears,
>
> I read and accept RFC2.
>
> I need and therefore going to develop frontend for python modules "keras" and 
> "tensorflow" to analyze raster images in GRASS.
>
> Thus, I'd like to have write access for grass-addons repository and develop 
> addons r.keras.*
>
> My GitHUB username is xyzallan.
>
> Regards,
> Allan Sims

Welcome to GRASS GIS Addons - I have sent an invitation via GitHub to
you (please accept it to activate your account) and added your record
(change [1]) to
"grass-addons/contributors.csv" .

Here some hints: Please, prior to submission, check your code and
manual contributions against the rules defined in the document
Submitting (and its subsections):

https://trac.osgeo.org/grass/wiki/Submitting
--> Submitting rules

and please also take a look at
https://github.com/OSGeo/grass/blob/master/CONTRIBUTING.md

This ensures a smooth integration into the standard GRASS code base
and avoids portability problems.

The "What's next" we addressed here:
https://trac.osgeo.org/grass/wiki/HowToContribute#Thenwhat

Looking forward to your contributions!

Happy coding,
Markus

[1] 
https://github.com/OSGeo/grass-addons/commit/f99a34bdc693a5d0d43d3623e436352713174401

--
Markus Neteler
GRASS GIS PSC Chair
http://grass.osgeo.org
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc