Re: [GRASS-PSC] Kind reminder: PSC meeting on Friday Aug 9 at 15:00 UTC

[Helmut Kudrnovsky via grass-psc]

Hi Vero,

thanks for the reminder.

Unfortunately, I'll be out for field work; not sure, if internet connect will 
work.

please ping me after the PSC meeting if voting or action is needed.

best
Helli 
 
--
Gesendet: Montag, 05. August 2024 um 16:00 Uhr
Von: "Veronica Andreo via grass-psc" 
An: "GRASS-PSC" 
Betreff: [GRASS-PSC] Kind reminder: PSC meeting on Friday Aug 9 at 15:00 UTC

Dear all,

This is a kind reminder of our quarterly PSC meeting next friday August 9th at 
15 UTC (Check local 
times[https://www.timeanddate.com/worldclock/meetingdetails.html?year=2024&month=8&day=9&hour=15&min=0&sec=0&p1=207&p2=51&p3=48&p4=25&p5=197]).

Topics for the agenda are being collected at: 
https://grasswiki.osgeo.org/wiki/PSC_Meeting_2024-08-09[https://grasswiki.osgeo.org/wiki/PSC_Meeting_2024-08-09].
 Please, add/remove/edit/comment :)

Also, please have a look at the last meeting minutes [0, 1] and check if there 
was any action point to be completed. 
 
Thanks in advance! See you soon!
Vero
 
[0] 
https://grasswiki.osgeo.org/wiki/PSC_Meeting_2024-05-10[https://grasswiki.osgeo.org/wiki/PSC_Meeting_2024-05-10]
[1] 
https://grasswiki.osgeo.org/wiki/PSC_Meeting_2024-06-14[https://grasswiki.osgeo.org/wiki/PSC_Meeting_2024-06-14]
 --

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/[https://veroandreo.gitlab.io/]___
 grass-psc mailing list grass-psc@lists.osgeo.org 
https://lists.osgeo.org/mailman/listinfo/grass-psc[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 during Prague Community Meeting

[Helmut Kudrnovsky via grass-psc]

Hi Vero,

>Thanks for your answer! Helena, Huidae, Michael, what do you say? 
>The rest of us will be in the same room and time zone if jet lag permits, 
>hopefully :) 
 
 I'll be in the train to Prague; will see if there is an internet connection.

best
Helli
 


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

Re: [GRASS-PSC] PSC meeting during Prague Community Meeting

[Helmut Kudrnovsky via grass-psc]

Hi Vero,

thanks for your initative.

>We can then meet on Friday June 14, at 15 UTC

In the best case, I'm sitting in the train to Prague at that time; not sure if 
there is internet connection available. In a not so good case, due to some 
health issues, I'm not able to travel to Prague, then I'm available online.

best
Helli 
 
--
Gesendet: Montag, 03. Juni 2024 um 14:00 Uhr
Von: "Veronica Andreo via grass-psc"
An: "GRASS-PSC" 
Betreff: [GRASS-PSC] PSC meeting during Prague Community Meeting

Dear all,
 
As discussed during our last PSC meeting [0], this year we have PSC elections. 
While we already have some definitions [0,1], there are still refinements to be 
made and we need to decide on the date, so our CRO can plan ahead. 
 
Several of us will be in person in Prague from June 13 until June 19, so this 
is a great opportunity to resume discussions. Given time zones differences [2], 
perhaps we can use the same time slot we usually do PSC meetings. We can then 
meet on Friday June 14, at 15 UTC (See local times 
here[https://www.timeanddate.com/worldclock/meetingdetails.html?year=2024&month=6&day=14&hour=15&min=0&sec=0&p1=207&p2=204&p3=25&p4=197]).
 What do you think?
 
Looking forward to hearing from you and meeting soon! :)
 
Vero
 
[0] 
https://grasswiki.osgeo.org/wiki/PSC_Meeting_2024-05-10[https://grasswiki.osgeo.org/wiki/PSC_Meeting_2024-05-10]
[1] 
https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210203[https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210203]
[2] 
https://www.timeanddate.com/worldclock/meetingtime.html?iso=20240614&p1=207&p2=204&p4=25&p5=197[https://www.timeanddate.com/worldclock/meetingtime.html?iso=20240614&p1=207&p2=204&p4=25&p5=197]--

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/[https://veroandreo.gitlab.io/]___
 grass-psc mailing list grass-psc@lists.osgeo.org 
https://lists.osgeo.org/mailman/listinfo/grass-psc[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 final report and issue the 2nd payment

[Helmut Kudrnovsky via grass-psc]

>Big thanks to Linda and her mentors for their work and commitment! Thanks as 
>well to those testing and providing feedback! Very nice >work Linda!! 
>Congratulations!
>
>I hereby propose to approve her final report and issue the second payment.
>
>I start with my +1
>
>Vero
 
 +1

best
helli
 


___
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

[Helmut Kudrnovsky via grass-psc]

+1

Helli
 
--

Gesendet: Mittwoch, 24. Januar 2024 um 20:17 Uhr
Von: "Martin Landa via grass-psc" 
An: "GRASS PSC list" 
Betreff: [GRASS-PSC] [Motion] Proposing Linda Karlovska as a new core developer

Dear PSC,
 

st 24. 1. 2024 v 18:29 odesílatel 
mailto:linda.karlov...@seznam.cz]> 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[https://github.com/lindakladivova]) as a 
core developer.
 
I start with my +1.
 
Martin--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/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[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] Proposing Linda Karlovska as a new core developer

[Helmut Kudrnovsky via grass-psc]

Dear PSC, Hi Martin,

I support this. :-)

Best
Helli 


---
Gesendet: Mittwoch, 24. Januar 2024 um 10:01 Uhr
Von: "Martin Landa via grass-psc" 
An: "GRASS PSC list" 
Cc: "Linda Kladivova" 
Betreff: [GRASS-PSC] Proposing Linda Karlovska as a new core developer

Dear PSC,

Let me propose Linda Karlovska (https://github.com/lindakladivova) to be
accepted as a core developer.

Linda has contributed relevant improvements (ie. single layout window mode) and 
fixes to various parts of GUI code base:

- accepted PRs (95!):
https://github.com/OSGeo/grass/pulls?q=is%3Apr+author%3Alindakladivova+is%3Aclosed+[https://github.com/OSGeo/grass/pulls?q=is%3Apr+author%3Alindakladivova+is%3Aclosed+]
- currently proposed PRs (open):
https://github.com/OSGeo/grass/pulls/lindakladivova[https://github.com/OSGeo/grass/pulls/lindakladivova]
 
I have asked her off-list and she would be happy to join the core team [1] with 
write access to the main repository.
 
Linda, 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 [3] all PSC members will then need to vote in a separate 
motion.

Best regards, Martin
 
[1] 
https://github.com/orgs/OSGeo/teams/grass-write[https://github.com/orgs/OSGeo/teams/grass-write]
[2] 
https://github.com/OSGeo/grass/blob/main/doc/development/rfc/legal_aspects_of_code_contributions.md[https://github.com/OSGeo/grass/blob/main/doc/development/rfc/legal_aspects_of_code_contributions.md]
[3] 
https://github.com/OSGeo/grass/blob/main/doc/development/rfc/PSC_guidelines.md#operation-of-the-psc[https://github.com/OSGeo/grass/blob/main/doc/development/rfc/PSC_guidelines.md#operation-of-the-psc]
 --
Martin Landa
http://geo.fsv.cvut.cz/gwiki/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[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] [OSGeo-Discuss] Mailing lists to discourse migration

[Helmut Kudrnovsky via grass-psc]

hi PSC members,

forwarding from OSGeo Discuss ML

Anything we should discuss about it?

Happy New Year!
Helli

--
[OSGeo-Discuss] Mailing lists to discourse migration
[https://lists.osgeo.org/pipermail/discuss/2023-December/040016.html]

>Hello all
>
>We are ready to migrate mailing lists to discourse,
>* Have the mailing list migrated completely to discourse
>* Have a mirror of the mailing in discourse
>* Have a category on discourse and not have a mailing list
>* Opt to not migrate or mirror the mailing list
>
>A comprehensive list of mailing lists can be found here (not including
>private mailing lists):
>https://lists.osgeo.org/mailman/listinfo
>
>You need to open a ticket to have the work done.
>Follow the ticket examples below for the first 3 cases
>
>Regards
>Vicky Vergara
>
>Example: Have the mailing list migrated completely to discourse:
>
>Ticket: https://trac.osgeo.org/osgeo/ticket/3064 (has link to ticket 3063)
>+
>Comment in Ticket: https://trac.osgeo.org/osgeo/ticket/3063
>
>Created the following discourse category
>https://discourse.osgeo.org/c/qgis/qgis-fr-user/5
>And the archives of the mailing list will not be removed:
>https://lists.osgeo.org/pipermail/qgis-fr-user/
>Migration has finished so any new message to the list will not be received
>on discourse, but the list will be disabled for before the end of january.
>Mail on discourse: qgis-fr-user/@discourse.osgeo.org
>
>Example: Have a mirror of the mailing in discourse
>Ticket: https://trac.osgeo.org/osgeo/ticket/3062
>Created the following discourse category
>https://discourse.osgeo.org/c/sac-global-category/sac/13
>The mailing list will not be removed, and it is a mirror to the mailing list
>emails continue to be sent to sac at lists.osgeo.org
>Replies can be done
>https://discourse.osgeo.org/t/re-osgeo-3062-import-sac-mailing-list-to-discourse/4747/2?u=cvvergara
>But they will no be reflected on the mailing list
>https://lists.osgeo.org/pipermail/sac/2023-December/thread.html
>
>Example: of category without mailing list
>Ticket: https://trac.osgeo.org/osgeo/ticket/3066
>https://discourse.osgeo.org/c/osgeolive/osgeolive-docs/8
___
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

[Helmut Kudrnovsky via grass-psc]

+1

merry christmas!
helli 



https://docs.google.com/document
https://grasswiki.osgeo.org/wiki/Student_Grants[https://grasswiki.osgeo.org/wiki/Student_Grants].
 
https://lists.osgeo.org/mailman/listinfo/grass-psc[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] Fw: Re: [Motion] Proposing Edouard Choinière as a new core developer

[Helmut Kudrnovsky via grass-psc]

>Von: "Veronica Andreo via grass-psc" 
>Thanks Markus for the motion and thanks everyone for voting! 
 
Welcome on board, Edouard!

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

that's a good idea!

best
Helli
 

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

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

[Helmut Kudrnovsky via grass-psc]

forwarding to the ML, see below 
 

Gesendet: Donnerstag, 14. Dezember 2023 um 13:51 Uhr
Von: "Helmut Kudrnovsky" 
An: hmit...@ncsu.edu
Betreff: Aw: Re: [GRASS-PSC] [Motion] Proposing Edouard Choinière as a new core 
developer

*
 +1

Helli
* 

Gesendet: Donnerstag, 14. Dezember 2023 um 13:42 Uhr
Von: "Helena Mitasova via grass-psc" 
An: "GRASS-PSC" 
Betreff: Re: [GRASS-PSC] [Motion] Proposing Edouard Choinière as a new core 
developer

+1
 
 Helena

 

On Dec 14, 2023, at 7:33 AM, Anna Petrášová via grass-psc 
mailto:grass-psc@lists.osgeo.org]> wrote: 

+1
 
Anna 

On Thu, Dec 14, 2023, 7:32 AM Veronica Andreo via grass-psc 
mailto:grass-psc@lists.osgeo.org]> wrote:

Great! 
+1! 
 
Vero 

El jue, 14 dic 2023 a las 9:29, Markus Neteler via grass-psc 
(mailto:grass-psc@lists.osgeo.org]>) escribió: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[https://lists.osgeo.org/pipermail/grass-psc/2023-December/002784.html[https://lists.osgeo.org/pipermail/grass-psc/2023-December/002784.html]]

Motion: accept Edouard Choinière 
(https://github.com/echoix[https://github.com/echoix][https://github.com/echoix[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 
mailto:nete...@osgeo.org]> wrote:
>
> Dear PSC,
>
> Let me propose Edouard Choinière 
> (https://github.com/echoix[https://github.com/echoix][https://github.com/echoix[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[https://github.com/OSGeo/grass/pulls?q=is%3Apr+author%3Aechoix+is%3Aclosed][https://github.com/OSGeo/grass/pulls?q=is%3Apr+author%3Aechoix+is%3Aclosed[https://github.com/OSGeo/grass/pulls?q=is%3Apr+author%3Aechoix+is%3Aclosed]]
> - currently proposed PRs (open):
>   
>https://github.com/OSGeo/grass/pulls/echoix[https://github.com/OSGeo/grass/pulls/echoix][https://github.com/OSGeo/grass/pulls/echoix[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[https://github.com/OSGeo/grass-addons/pulls?q=is%3Apr+author%3Aechoix+is%3Aclosed][https://github.com/OSGeo/grass-addons/pulls?q=is%3Apr+author%3Aechoix+is%3Aclosed[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[https://github.com/OSGeo/grass-addons/pulls/echoix][https://github.com/OSGeo/grass-addons/pulls/echoix[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[https://github.com/OSGeo/grass-website/pulls?q=is%3Apr+author%3Aechoix+is%3Aclosed][https://github.com/OSGeo/grass-website/pulls?q=is%3Apr+author%3Aechoix+is%3Aclosed[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[https://github.com/OSGeo/grass/blob/main/doc/development/rfc/PSC_guidelines.md#operation-of-the-psc][https://github.com/OSGeo/grass/blob/main/doc/development/rfc/PSC_guidelines.md#operation-of-the-psc[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[https://github.com/OSGeo/grass/blob/main/doc/development/rfc/legal_aspects_of_code_contributions.md][https://github.com/OSGeo/grass/blob/main/doc/development/rfc/legal_aspects_of_code_contributions.md[https://github.com/OSGeo/grass/blob/main/doc/development/rfc/legal_aspects_of_code_contributions.md]]
>
> --
> Markus Neteler, PhD
> https://www.mundialis.de[https://www.mundialis.de][https://www.mundialis.de/[https://www.mundialis.de/]]
>  - free data with free software
> https://grass.osgeo.org[https://grass.osgeo.org][https://grass.osgeo.org/[h

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

[Helmut Kudrnovsky via grass-psc]

+1

helli 
 

Gesendet: Freitag, 01. Dezember 2023 um 18:46 Uhr
Von: "Veronica Andreo via grass-psc" 
An: "GRASS-PSC" 
Betreff: [GRASS-PSC] [Motion] Appoint Vaclav Petras as new treasurer

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

[Helmut Kudrnovsky via grass-psc]

 +1
 
 helli

Gesendet: Freitag, 01. Dezember 2023 um 09:39 Uhr
Von: "Martin Landa via grass-psc" 
An: "GRASS PSC list" 
Betreff: [GRASS-PSC] [Motion] Approve OSGeo Code Sprint 2023 reimbursements

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[https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023]
[2] 
https://docs.google.com/spreadsheets/d/1PYFJIwq_M8jm3rrGyUWOwZ5QQTOmKvyBuIiIFRLLqRY/edit?usp=sharing[https://docs.google.com/spreadsheets/d/1PYFJIwq_M8jm3rrGyUWOwZ5QQTOmKvyBuIiIFRLLqRY/edit?usp=sharing]
 --
Martin Landa
http://geo.fsv.cvut.cz/gwiki/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[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 - November 10, 2023

[Helmut Kudrnovsky via grass-psc]

Hi Vero,
 
sorry for not joining the PSC meeting. I was on the road and mobile internet 
unfortunately didn't work .

Thanks for sharing the meeting minutes! Where should I comment the bullets 
points? Here or in the wiki.

best
Helli 
 
-
Gesendet: Sonntag, 12. November 2023 um 17:16 Uhr
Von: "Veronica Andreo via grass-psc"

Betreff: [GRASS-PSC] PSC meeting minutes - November 10, 2023

Dear all,
 
 
Here are the PSC meeting minutes of our last meeting:
https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20231110 
Comments, suggestions and contributions are more than welcome, I might have 
missed something :)

 

Thanks everyone! 
 
Vero--

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/[https://veroandreo.gitlab.io/]___
 grass-psc mailing list grass-psc@lists.osgeo.org 
https://lists.osgeo.org/mailman/listinfo/grass-psc[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 Community Sprint 2023

[Helmut Kudrnovsky via grass-psc]

Von: "Martin Landa via grass-psc"
>I just aware of Markus, me and Linda planning to come to Vienna code sprint.

I'll be in Vienna too at that time. ;-) 

though not sure I'm able to join code sprint during day; but I'm available for 
discussions in the evening. :-) 

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

Re: [GRASS-PSC] Fwd: [OSGeo-Discuss] Preparing annual report on the AGM slides

[Helmut Kudrnovsky]

Hi Vero,

>I have updated the GRASS slide for the AGM, feel free to edit or suggest 
>modifications :)
 
thanks for the AGM slide update!

I've left some comments there. Maybe adding a short note there about future 
development directions, i.e. inital work to support cmake building/compilation. 
maybe in that way we are able to attract more helping hands. :-) the same is 
valid for the inital work for the R-GRASS-interface upgrade.

ciao
Helli 
 


___
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

[Helmut Kudrnovsky]

>Gesendet: Montag, 15. Mai 2023 um 21:26 Uhr
>Von: "Veronica Andreo"
>An: "GRASS-PSC" 
>Betreff: [GRASS-PSC] [Motion] Approve and adopt RFC about Python Language 
>Support
>
>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
 
+1

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

Re: [GRASS-PSC] RFC: Version Numbering

[Helmut Kudrnovsky]

>Von: "Vaclav Petras"
>
>Betreff: [GRASS-PSC] RFC: Version Numbering
>
>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

helmut
 

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

[Helmut Kudrnovsky]

Hi Markus, 
 
>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? 

good idea! :-)

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

lets do it :-)

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

[Helmut Kudrnovsky]

+1
 helli 
 

Gesendet: Montag, 06. März 2023 um 14:13 Uhr
Von: "Veronica Andreo
An: "GRASS-PSC" 
Betreff: [GRASS-PSC] [Motion] Approve Linda's student grant final report and 
make the 2nd payment

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á mailto:l.kladiv...@seznam.cz]>
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: mailto:grass-...@lists.osgeo.org]>, 
mailto:grass-u...@lists.osgeo.org]> 
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[https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/ImprovingSingleWindowUX]
[2] 
https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/RedesigningStatusbar#FinalReport[https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/RedesigningStatusbar#FinalReport]
[3] 
https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/ImprovingSingleWindowUX#FinalReport[https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/ImprovingSingleWindowUX#FinalReport]
[4] 
https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/ImprovingSingleWindowUX#ScreenshotsofSingle-WindowGUIimprovements[https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/ImprovingSingleWindowUX#ScreenshotsofSingle-WindowGUIimprovements]
 
Have a nice week.
Linda___
grass-dev mailing list
grass-...@lists.osgeo.org[mailto: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[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] [Board] Travis usage of GRASS

[Helmut Kudrnovsky]

forwarding from the Board ML:

https://lists.osgeo.org/pipermail/board/2023-February/013223.html

-

After not seeing any builds for a while in Travis from Grass, I just saw one 
recently. 

We were considering cancelling OSGeo’s subscription but if this is something 
GRASS is actively using/depending on, we can maintain. We might scale back the 
subscription if its only lightly used those. I have to renew on Feb 19 so if 
you could let me know before then.


Thanks,
Mike

-
Michael Smith
OSGeo Treasurer

-

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

Re: [GRASS-PSC] Welcome Helmut Kudrnovsky

[Helmut Kudrnovsky]

Hi Vaclav, dear PSC,

>Dear all,
> 
>It is my pleasure to welcome Helmut Kudrnovsky as a new Project Steering 
>Committee member.
> 
>This was confirmed at the PSC meeting last Friday. The relevant portion of 
>meeting 
>minutes[https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20230210] is 
>here: "We welcomed Helli as a new PSC member following the procedure defined 
>in Feb 
>2021[https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210203] and 
>the results of 2020's 
>election[https://trac.osgeo.org/grass/wiki/PSC/Election2020#Results].";
> 
>Welcome, Heli!
>
>Vaclav

thank you very much for your kind words! 

It is a major honor for me to serve on the GRASS GIS PSC!

Back in October 2004, IIRC, I've posted my first question on the GRASS user ML. 
oh, it's really really quite long ago. :-)

https://lists.osgeo.org/pipermail/grass-user/2004-October/026854.html

> [GRASSLIST:4667] from line to polygon
> 
> Hi GRASS friends,
> 
> I am very new in using GRASS (5.3, 5.7, LINUX). I have two questions:
> 
> 1) I have a line-Shape-file, in which areas (vegetation types) are 
> digitized. After importing into GRASS, is it possible to convert the 
lines 
> into polygones?
> 
> 2) Is it possible to export these polygones in Arc/Info-e00-format?
> 
> Thanks with greetings from Tyrol
> Helli
 
the cool thing is, that you can learn so much about GIS from the great 
community. :-)

I've never studied GIS; all, I know about GIS, data and projections, I've 
learned by following the mailing lists of free and
open source software like GRASS GIS, GDAL and PROJ. Nowadays, I use GIS in my 
daily life as ecologist still using these tools. :-)

Best
Helli  

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

[GRASS-PSC] Card or Flowers for Markus?

[Helmut Kudrnovsky]

>Michael Barton:
>I would certainly like to add my best wishes to any virtual card or other 
>message you are able to send.

same here, I would also like to add my best wishes!

thanks!

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

Re: [GRASS-PSC] proposal: winGRASS 32bit versions - phasing out in 2020

[Helmut Kudrnovsky]

Martin Landa wrote
> Hi,
> 
> čt 25. 2. 2021 v 16:29 odesílatel Moritz Lennert
> <

> mlennert@.worldonline

> > napsal:
>> Do I understand correctly that 32bit is already gone in the current
>> osgeo4w release ? Then yes, I think an announcement would be
> 
> I don't think so, see
> http://download.osgeo.org/osgeo4w/x86/release/grass/grass/
> 
>> appropriate. Otherwise, we could possibly combine it with the
>> announcement of a grass 8 release.
> 
> I have no objection to drop 32bit support starting GRASS 8. It somehow
> corresponds with QGIS [1].

I suggest to drop it now that transition to 64bit only is clear.

citing Jürgen's mail

>It also has PDAL 2.2 which is required for native support of point clouds
in 
>QGIS - something that you find lacking in the "old" OSGeo4W repository and
in
>turn in the current standalones.

maybe also a good time to switch to pdal powered modules in GRASS and drop
the liblas powered modules.

now to more challenging issues with a switch in short/mid/long term to the
new built OSGeo4W 64bit environment:

>Also note that it now only has one version of Python - namely 3.9, which
>doesn't support Windows 7 anymore.  

are we already python 3.9 ready?

>Other updates include Qt 5.15, GDAL 3.2,
>PROJ 7.2 <=

just have a look at
http://download.osgeo.org/osgeo4w/testing/x86_64/release/proj/proj-data/

proj-data-1.4-1.tar.bz2 558M <= !!!

in PROJ7, there is a complete change how PROJ related/needed data is
handled:

(1) dynamically via https://cdn.proj.org/
(3) via a revamped proj-data with file size of more than 500 MB

* will GRASS be ready to handle it dynamically via CDN?

* including more than 500MB data into our standalone installer will explode
our used NSIS system, it won't work; maybe we have to switch also to a MSI
based system or another system

all in all, quite a lot of work will be needed to provide standalone/OSGeo4W
winGRASS.






-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] proposal: winGRASS 32bit versions - phasing out in 2020

[Helmut Kudrnovsky]

Hi PSC members,


Helmut Kudrnovsky wrote
> Martin Landa wrote
>> Hi Helmut,
>> 
>> pá 1. 5. 2020 v 22:16 odesílatel Helmut Kudrnovsky <
> 
>> hellik@
> 
>> > napsal:
>>> not yet, as I think there should be a PSC descision/discussion before
>>> such a
>>> far-reaching action. :-)
>> 
>> thanks for raising this issue. I agree that we should drop 32bit at
>> certain point. The question is when. I would personally do this step
>> together with QGIS community. Are you aware of any QGIS plans?
> 
> I'm not aware of any QGIS plan yet. I'll ask on the QGIS dev-ML in the
> next
> days.
> 
> related:
> https://www.bleepingcomputer.com/news/microsoft/rip-microsoft-to-drop-support-for-windows-10-on-32-bit-systems/
> 
> "Microsoft to drop support for Windows 10 on 32-bit systems":
> 
> Microsoft has stated that future versions of Windows 10, starting with the
> May 2020 Update, will no longer be available as 32-bit builds on new OEM
> computers.
> 
> all in all a good moment to phase out winGRASS 32bit versions.


see https://lists.osgeo.org/pipermail/grass-user/2021-February/082242.html

[...]
In OSGeo4W there has lately been a big effort to reboot it, meaning that it
has 
been completely rebuilt using newer source versions of mostly every package 
using a newer compiler.
[...]
As the new OSGeo4W only supports
64bit
[...]

so it's time now (without a phasing out :-) ) to say good bye and retire
winGRASS 32bit too.

an announcement to the community needed?



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
___
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?

[Helmut Kudrnovsky]

Hernán,

thanks for work as CRO!


Chief Return Officer (CRO) - GRASS GIS election 2020 wrote
> Dear members of the GRASS GIS PSC,
> 
> Those of you willing to stand up as candidates for reelection to the PSC 
> are asked to e-mail their candidacy to me (possibly also publicly to the 
> relevant lists if you may wish so), including a brief statement on what 
> you aim to achieve as PSC member during a potential new tenure period.
> 
> Regards,
> 
> Hernán
> 
> Chief Return Officer (CRO)


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?



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Contribution in AddOns

[Helmut Kudrnovsky]

>Unfortunately not completely. Now it seems to hang (like some other modules)
at the matplotlib import:

IIRC, windows requires some special matplotlib import.

see:

https://github.com/OSGeo/grass-addons/blob/master/grass7/raster/r.width.funct/r.width.funct.py#L113

def plotImage(x,y,image,type,xlabel,ylabel,title):
import matplotlib #required by windows
matplotlib.use('wxAGG') #required by windows
import matplotlib.pyplot as plt

not all matplotlib backends works the same in windows like in linux



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] proposal: winGRASS 32bit versions - phasing out in 2020

[Helmut Kudrnovsky]

Martin Landa wrote
> Hi Helmut,
> 
> pá 1. 5. 2020 v 22:16 odesílatel Helmut Kudrnovsky <

> hellik@

> > napsal:
>> not yet, as I think there should be a PSC descision/discussion before
>> such a
>> far-reaching action. :-)
> 
> thanks for raising this issue. I agree that we should drop 32bit at
> certain point. The question is when. I would personally do this step
> together with QGIS community. Are you aware of any QGIS plans?

I'm not aware of any QGIS plan yet. I'll ask on the QGIS dev-ML in the next
days.

related:
https://www.bleepingcomputer.com/news/microsoft/rip-microsoft-to-drop-support-for-windows-10-on-32-bit-systems/

"Microsoft to drop support for Windows 10 on 32-bit systems":

Microsoft has stated that future versions of Windows 10, starting with the
May 2020 Update, will no longer be available as 32-bit builds on new OEM
computers.

all in all a good moment to phase out winGRASS 32bit versions.




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] proposal: winGRASS 32bit versions - phasing out in 2020

[Helmut Kudrnovsky]

hi Peter,

>was the announcement of the discontinuation of winGRASS 32bit communicated
via the OSGeo-announce >list (or similar) ?

not yet, as I think there should be a PSC descision/discussion before such a
far-reaching action. :-)



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] proposal: winGRASS 32bit versions - phasing out in 2020

[Helmut Kudrnovsky]

Helmut Kudrnovsky wrote
> dear GRASS PSC,
> 
> a few days ago, I've asked in the GRASS user ML following question [1]:
> 
> *winGRASS - still a need for 32bit versions?*
> 
> reasoning:
> 
> - 64bit computer architecture and 64bit windows operating systems are very
> common
> - 32bit computer architecture and 32bit windows operating systems will
> find
> their EOL
> 
> and the important reasons:
> 
> - reduce the high maintenance burden to keep 2 build environments of
> winGRASS (32bit, 64bit) alive
> - facilitate to find possible (automatic) alternatives of winGRASS build
> environments beside the actual MSYS2/OSGeo4W workflow  
> 
> so far, no feedback by the community that there is still a need for a
> winGRASS 32bit version.
> 
> thus I propose:
> 
> * phasing out of winGRASS 32bit versions in 2020
> * communicate early and communicate often ;-) about this phasing out
> 
> in my original post, I've suggested  'middle next year (2020 July 31)'
> 
> it can be discussed if it should happen at middle next year (2020 July 31)
> or end of year 2020; though IMHO it should happen... ;-)
> 
> any feedback? any suggestions?
> 
> [1]
> http://osgeo-org.1560.x6.nabble.com/winGRASS-still-a-need-for-32bit-versions-td5424586.html
> 
> 
> 
> -
> best regards
> Helmut
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
> ___
> grass-psc mailing list

> grass-psc@.osgeo

> https://lists.osgeo.org/mailman/listinfo/grass-psc

Coming back to this? Any opinions? Any suggestions?

Citing here https://trac.osgeo.org/osgeo4w/ticket/627#comment:3



The current idea is to switch to 5.14 and use the occasion to upgrade
compilers and drop 32bit (according to the latest qgis survey only 7% of the
participants still use it).


I still think we should phase out wingrass 32bit  in 2020 ;-)   and
should announce it earlier than later. 




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] proposal: winGRASS 32bit versions - phasing out in 2020

[Helmut Kudrnovsky]

dear GRASS PSC,

a few days ago, I've asked in the GRASS user ML following question [1]:

*winGRASS - still a need for 32bit versions?*

reasoning:

- 64bit computer architecture and 64bit windows operating systems are very
common
- 32bit computer architecture and 32bit windows operating systems will find
their EOL

and the important reasons:

- reduce the high maintenance burden to keep 2 build environments of
winGRASS (32bit, 64bit) alive
- facilitate to find possible (automatic) alternatives of winGRASS build
environments beside the actual MSYS2/OSGeo4W workflow  

so far, no feedback by the community that there is still a need for a
winGRASS 32bit version.

thus I propose:

* phasing out of winGRASS 32bit versions in 2020
* communicate early and communicate often ;-) about this phasing out

in my original post, I've suggested  'middle next year (2020 July 31)'

it can be discussed if it should happen at middle next year (2020 July 31)
or end of year 2020; though IMHO it should happen... ;-)

any feedback? any suggestions?

[1]
http://osgeo-org.1560.x6.nabble.com/winGRASS-still-a-need-for-32bit-versions-td5424586.html



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Write access to grass-addons github

[Helmut Kudrnovsky]

stevenpawley wrote
> Dear GRASS development team,
> 
> I previously had write access to the grass-addons svn, and my github id is
> listed on the contributors page. However, I can't seem to get permission
> to
> commit using my github id and password. Is it possible to get write access
> because I would like to update my addons to fix issues with python3.
> 
> Steve
> 
> ___
> grass-psc mailing list

> grass-psc@.osgeo

> https://lists.osgeo.org/mailman/listinfo/grass-psc


regarding ssh key, der

https://help.github.com/en/articles/adding-a-new-ssh-key-to-your-github-account



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Write access to grass-addons github

[Helmut Kudrnovsky]

stevenpawley wrote
> Dear GRASS development team,
> 
> I previously had write access to the grass-addons svn, and my github id is
> listed on the contributors page. However, I can't seem to get permission
> to
> commit using my github id and password. Is it possible to get write access
> because I would like to update my addons to fix issues with python3.
> 
> Steve
> 
> ___
> grass-psc mailing list

> grass-psc@.osgeo

> https://lists.osgeo.org/mailman/listinfo/grass-psc

Have you added your public ssh key to your github profile?



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] git migration

[Helmut Kudrnovsky]

Markus Neteler wrote
> PS: Did I mention that Martin Landa did an outstanding hard job with
> developing the svn2git converter scripts for code and issues? Weeks of
> work... thanks Martin!!

big kudos to Martin!




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] GRASS GIS Budget 2019 - draft

[Helmut Kudrnovsky]

>Vero wrote a nice motivation: 
>
>https://grasswiki.osgeo.org/wiki/Website_migration_plan_2019#Why_a_new_Website

thanks to Vero for the very nice motivation letter.





-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [Motion] Proposing Stefan Blumentrath as a new core developer

[Helmut Kudrnovsky]

Markus Neteler wrote
> I turn this into a motion:
> 
> On Tue, Jan 30, 2018 at 10:48 PM, Markus Neteler <

> neteler@

> > wrote:
>> PSC,
>>
>> I pick up a recent suggestion on grass-dev, to invite Stefan
>> Blumentrath as a core developer.
>>
>> All of you will know him (virtually or in person):
>> - https://www.osgeo.org/member/blumentrath/
>> - https://github.com/ninsbl
>>
>> He is continuously contributing to various parts of the source code
>> through others (see ChangeLog).
>>
>> I asked him off-list and he's interested to join the core team with
>> write access.
>>
>> According to RFC1 [1] we all need then to vote here once a motion is
>> made. Optionally I can make this a motion right away.
> 
> +1 Markus

although I'm not a PSC member, I support the motion.




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Fwd: [Board] Budgeting project event support for 2018

[Helmut Kudrnovsky]

Markus Neteler wrote
> On Oct 21, 2017 4:17 PM, "Veronica Andreo" <

> veroandreo@

> > wrote:
>>From: Moritz Lennert <

> mlennert@.worldonline

> >
>>> Le 20 octobre 2017 17:11:51 GMT+02:00, Markus Neteler <

> neteler@

> >
> a écrit :
>>> >Hi PSC,
>>> >
>>> >I think we should ask for more for 2018 which implies that we develop a
>>> >spending plan. This is a bit overdue :)
>>> >
>>> >Your comments are welcome!
>>>
>>> I think it might be good to plan at least one developer meeting per
> year, like the one Vero just proposed and to be able to pay some of the
> accommodation/food costs (obviously trying to find free or cheap solutions
> if possible) and maybe help one or two developers from further away to pay
> the trip.
>>>
>>> Plus participation in one OSGEO code sprint, again trip / accommodation.
> So maybe we should aim for +/- 3000 ?
>>
>>
>> while not psc, +1
> 
> I have added 3500 USD for now in
> 
> https://wiki.osgeo.org/wiki/OSGeo_Budget_2018

not a GRASS PSC member, but what about 5000 USD to get a nice dev group at
one place in order to reach/start the next target: GRASS 8?




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Let's approve new core developers

[Helmut Kudrnovsky]

Markus Neteler wrote
> PSC,
> 
> On Tue, Jun 13, 2017 at 8:59 AM, Markus Neteler <

> neteler@

> > wrote:
>> PSC,
>>
>> we didn't invite new core developers for a while, I think this should
>> be done asap.
>>
>> Again a somewhat sensitive topic, how shall we proceed? I have some
>> ideas but did not approach those people yet.
>>
>> Open discussion without names :-)
> 
> Time for a new round!
> We have great Addon developers, power users and more.
> 
> Let's get more people directly involved, i.e. grant write access to trunk.
> 
> Opinions?

though not on PSC, I think these are good ideas to enlarge the devs.




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Let's approve new core developers

[Helmut Kudrnovsky]

Markus Neteler wrote
> On Thu, Jun 15, 2017 at 6:31 PM, Moritz Lennert
> <

> mlennert@.worldonline

> > wrote:
> ...
>> Does anyone have someone they want to propose as core developer ?
> 
> Yes: I would like to propose Veronica Andreo
> (https://veroandreo.wordpress.com ;
> https://www.researchgate.net/profile/Veronica_Andreo2).
> 
> For a long time, she is continuously contributing to GRASS GIS, a
> great (T)GRASS power user and likely to contribute a better
> documentation and more.
> Granting core write access to her would enables her to collect
> contribution related "credits" directly rather than through indirect
> "on behalf of someone" commit messages.
> I am sure that she'd be careful when committing and, thanks to the
> revision system things are peer reviewed (via
> https://lists.osgeo.org/pipermail/grass-commit/) and adjustable
> anyway.

no PSC member, but I support Markus' proposal.




-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Let-s-approve-new-core-developers-tp5323972p5324480.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Introducing DOI for software, documentation and data in the GRASS project

[Helmut Kudrnovsky]

Michael Barton wrote
> Markus and Co.
> 
> This is something CoMSES Net (Network for Computational Modeling in Social
> and Ecological Sciences: http://www.comses.net) has been working with for
> some years now. We maintain a software code library, where researchers can
> publish model code. We also provide for the option of code peer review,
> which can happen when code is submitted to the library for review along
> with a paper sent to a journal, or independent of any paper review. Code
> that has passed peer review is currently assigned a “handle” from
> handle.net;. Handle.net;
> is the organization that oversees the digital identifier ecosystem. DOI’s
> are commercial instances and handles are open source instances, but both
> are ultimately under the purview of handle.net;.
> With a new grant from NSF, CoMSES Net is now part of a new national data
> infrastructure network in the US. One of our plans is to transition from
> handles to DOI’s because these are more widely recognized.
> 
> Given all this, we’ve had to think quite a bit about how to ‘publish’
> model code and assign identifiers. As Vaclav points out there are
> significant issues with versioning. What happens with a new version? We’ve
> adopted a conceptual position that we are not a versioning repository
> primarily, but a place where authors can publish ‘finished’ code used in a
> research project or product. We are trying to treat this like a library
> and journal environment in that sense. We allow for minor revisions to
> correct errors (including as a response to reviews). But if a new product
> (e.g., a research paper) uses a new version of model code, we consider
> that a new digital object published, which could get a new handle/DOI
> distinct from a version of a model used for an earlier product. This
> remains something that is complicated to implement in practice. But the
> concept involves the reason for giving out the handle/DOI in the first
> place.
> 
> Currently, only about 10% of published model based science makes code
> available for review or reuse. We think it is increasingly important that
> researchers share the code that is an important component to scientific
> practice in the same way they share research protocols and results—and are
> increasingly encouraged to share data. But sharing code takes effort, and
> even researchers with the best intentions may find it difficult to find
> the time or energy to make code available. So we are trying to create
> incentives that will have some value in the academic/research world,
> including citable products. All models published in the CoMSES Net library
> have automatically generated citations. Those that have passed peer
> review, verifying some degree of software quality, are also given
> permanent identifiers (handles/DOIs), with the idea that researchers can
> put them on their CVs where they at least have the possibility of gaining
> them some recognition for the work carried out. That is, we consider a DOI
> as an incentive for sharing code and a bit of a lever to get others to
> cite that code if they use it.
> 
> We are still trying to work out how best to handle improvements (bug
> fixes) to a model vs. new models. We are moving our library to a Git
> environment, but are still working out how to implement our concept of
> “published” snapshots of code in a library/journal in versions and
> releases in Git. We do have a roadmap and are working on it, but we don’t
> yet have a solution in place.
> 
> Where is all this leading? We need to ask what is the value to assigning
> DOIs to GRASS code, how might they benefit GRASS developers, and how might
> they be used by GRASS software users? I don’t see that they provide the
> kind of incentives that CoMSES Net is envisioning for computational model
> developers. Most DOIs are assigned to finished products as digital
> objects. From that perspective, GRASS could get a DOI, but not its
> component modules. But what about each version of GRASS?  GRASS has formal
> releases, but not its components. Some code is in the released code base
> and other is in addons. There is ongoing development in the SVN. GRASS is
> a digital object of course, as are its component code modules, but it is a
> dynamic, living one and not a static one. Perhaps there are other benefits
> to working out the complications of where and when to assign DOIs in the
> GRASS ecosystem. But it will be good to start with a discussion of why and
> for whom we would do it.
> 
> (I’m copying Allen Lee from the CoMSES Net leadership team as he has
> thought a lot about this and might have other things to add.)
> 
> Cheers
> Michael

some kind of related:

http://ivory.idyll.org/blog/2016-using-zenodo-to-archive-github.html
https://zenodo.org/






-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Introducing-DOI-for-software-documentation-and-data-in-the

Re: [GRASS-PSC] Migration to git/gog

[Helmut Kudrnovsky]

>... and who is willing to dedicate time for a while to keep everything 
>up and running. 
>This was one of the obstacles so far. Anyone? 

maybe asking in user ML if there may be some interest and support? 



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/next-PSC-task-tp5286412p5294020.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] next PSC task

[Helmut Kudrnovsky]

>IMHO we need to have someone besides the current candidate(s) to 
>organize the election of the chair. 
>I hoped for some faster pace here :-) 

is there a similar system /infrastructure needed as for the PSC voting?



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/next-PSC-task-tp5286412p5286532.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] next PSC task

[Helmut Kudrnovsky]

Dear PSC, 

after the election of the new PSC, before defining the new chair, may I (as
a community member) ask you what will be the next task of the PSC?

when will be the new chair announced? 

I think an important first/next step to broaden the dev community may be to
investigate how new source code management technologies like GIT could be
implemented beside/instead of svn.

There are ongoing some OSGeo initiatives to provide GIT infrastructure for
OSGeo projects? Will be the GRASS GIS project will use such new
technologies?

Python 3 is heavily knocking on the door.

Will there be some lead of the new PSC regarding these challenges? 

Thanks for clarifications!



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/next-PSC-task-tp5286412.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS-dev] Comment regarding PSC election

[Helmut Kudrnovsky]

>This sounds like a good interim step for now. It is something that the new
PSC should continue to work on. 

seconded.



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Fwd-GRASS-dev-Comment-regarding-PSC-election-tp5278043p5278131.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [voting] financial support contributors meeting in San Michele (Feb 2016)

[Helmut Kudrnovsky]

Martin Landa wrote
> Dear PSC,
> 
> I would like to open request to financially support of contributors
> meeting (as discussed [1]) held in San Michele in Feb 2016 [2]. The
> collected bills [3] covers travel expenses (petrol) and lunch on
> Monday 15/2, see overview [4].
> 
> I would like to ask the chair (Markus) to officially launch this
> voting if possible.
> 
> Thanks! Martin
> 
> [1] http://lists.osgeo.org/pipermail/grass-psc/2016-February/001442.html
> [2]
> http://grasswiki.osgeo.org/wiki/GRASS_GIS_contributors_meetings_in_San_Michele/February_2016
> [3] https://drive.google.com/open?id=0B9xu5EldorOPTVlCMng0WXN5VmM
> [4]
> https://docs.google.com/spreadsheets/d/1hfSw38SYuY-qb4QllHEql2P4e5CKtedAGY6lA07GWpM/edit?usp=sharing
> 
> -- 
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.cz/mentors/landa
> ___
> grass-psc mailing list

> grass-psc@.osgeo

> http://lists.osgeo.org/mailman/listinfo/grass-psc

I'm no PSC member, I'm 1+.

but I 'm also for communicating early and loudly enough for such events to
attract interested people around nearby the event location.



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/voting-financial-support-contributors-meeting-in-San-Michele-Feb-2016-tp5255884p5255944.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] SVN write access request

[Helmut Kudrnovsky]

stevenpawley wrote
> [...]
> r.tri - the terrain ruggedness index of Riley et al. (1999), which can be
> extended in the script to be calculated over 3x3 to 11x11 window sizes.
> [...]

nice contributions to the GRASS GIS addons!

looking at
https://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.tri/r.tri.py#L57

may be some hints regarding a simplified moving window by r.mapcalc in a
python script:

https://grasswiki.osgeo.org/wiki/GRASS_Python_Scripting_Library#r.mapcalc_example:_defining_a_moving_window

or

https://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.valley.bottom/r.valley.bottom.py#L130




-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/SVN-write-access-request-tp5241020p5241265.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS-dev] too many branches => retirement GRASS6.5.svn (=develbranch6)

[Helmut Kudrnovsky]

Markus Metz-3 wrote
> Since the code base of devbr6 and relbr6 is largely identical,
> the same fix can be applied to both branches which is not a lot of
> work.
> ___
> grass-psc mailing list

> grass-psc@.osgeo

> http://lists.osgeo.org/mailman/listinfo/grass-psc

are you sure devbr6 and relbr6 are largely identical? 

if yes what's the benefit (for users and devs) to have both, when the focus
on grass7 development/improvement would be a desired target ?

if no what should be ported (from users' and devs'-view) from devbr6 to
relbr6, when the focus on grass7 development/improvement would be a desired
target ?

as Martin mentioned on the ML, there aren't anymore nightly devbr6-wingrass
nightlies (osgeo4w/standalone).




-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/too-many-branches-tp5131993p5133711.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] too many branches => retirement GRASS6.5.svn (=develbranch6)

[Helmut Kudrnovsky]

Martin Landa wrote
> 2014-04-06 15:16 GMT+02:00 Moritz Lennert
> 
>> Hamish, maybe you could be the official grass6 maintainer, managing the
>> whole grass6 development in the way you propose, i.e. any new development
>> and bugfixes first go into grass6dev for a period of testing, before
>> _you_
>> make the decision that something can be backported to grass6release. I do
>> think however, that for this to work, we would need to regularly publish
>> snapshots of grass6dev for easy testing.
> 
> I think we should really stop thinking about GRASS 6 "development",
> ideally we should fully focus our energy on GRASS 7. We do not have
> enough man-power for keeping development in GRASS 6, simply saying. So
> please bug fix only should go there (relbr64). No new functionality.
> 
> Martin
> -- 
> Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa

I encourage this.

the intention/motivation, why I've written the mail (and mail subject) in
that way I did, was/is to push forward GRASS 7 to a status ready for release
_and not to forget_ GRASS 6 - just always keeping grass-dev man power in
mind.

IMHO sometimes it's time to do the next (maybe challenging) step to get
GRASS 7 with all the fancy news out into the wild.

regarding release stability, I think it's all about communication with the
community.



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/too-many-branches-tp5131993p5133442.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] releases schedule

[Helmut Kudrnovsky]

> It counts with release once a year and a half year bugfixing (feature
freeze) period before the release.

+1 for release once a year and your proposal; maybe some fine tuning is
needed to follow the KISS-strategy ... for users and devs!



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/releases-schedule-tp5131995p5132062.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] too many branches => retirement GRASS6.5.svn (=develbranch6)

[Helmut Kudrnovsky]

Dear GRASS GIS PSC,


margherita wrote
> Dear Luca,
> 
> thank you for raising this issue,
> 
> On Sat, Mar 29, 2014 at 7:04 AM, Luca Delucchi <

> lucadeluge@

> > wrote:
>>
>>
>> with the upcoming GRASS 7 release we have to many branches to maintain
>> (releasebranch6, devbranch6, releasebranch7 and trunk).
>> Can I ask you to take a decision about the future of all this branches?
>>
>> I could suggest something like:
>> - keep releasebranch6 only for important bugfixes, no new feature and
>> starting to forget it
>> - put in reading mode or remove (after backport the differences with
>> grass64) devbranch6
>> - releasebranch7 is the new stable release branch, so new features
>> only when we are far from release a new version
>> - trunk for new feature
>>
>> what do you think?
>>
> 
> I'm in favor. Having too many branches from users point of view only
> raises
> confusion, and for developers is much more effort required to keep track
> of
> everything.
> 
> My 2c
> Regards,
> Madi
> 
>>
>> Thanks a lot
>> Best regards
>>
>> --
>> ciao
>> Luca
>>
>> http://gis.cri.fmach.it/delucchi/
>> www.lucadelu.org
>> ___
>> grass-psc mailing list
>> 

> grass-psc@.osgeo

>> http://lists.osgeo.org/mailman/listinfo/grass-psc
>>
> 
> 
> 
> -- 
> Best regards,
> 
> Dr. Margherita DI LEO
> Scientific / technical project officer
> 
> European Commission - DG JRC
> Institute for Environment and Sustainability (IES)
> Via Fermi, 2749
> I-21027 Ispra (VA) - Italy - TP 261
> 
> Tel. +39 0332 78 3600

> margherita.di-leo@.europa

> 
> Disclaimer: The views expressed are purely those of the writer and may not
> in any circumstance be regarded as stating an official position of the
> European Commission.
> 
> ___
> grass-psc mailing list

> grass-psc@.osgeo

> http://lists.osgeo.org/mailman/listinfo/grass-psc

it was a pleasure to meet GRASS devs but also GRASS users at the Vienna
OSGeo Code Sprint [1] which was also a GRASS community sprint [2].
In addition it was a honour for me to help getting beta release of GRASS GIS
7.0.0, the upcoming stable release, into the wild.
 
Now for us, GRASS devs _and_ users, there are now several branches of GRASS
GIS (trunk, releasebranch7, releasebranch6, develbranch6) [4] to maintain,
test and use.

A lot of important improvements and new, exciting and fancy features are now
in trunk and releasebranch7 which will never be backported to releasebranch6
and so on.
 
It is time for GRASS devs _and_ users to focus development on and maintain,
improve, test and use GRASS7.
 
As I trust in GRASS devs experience and carefulness of code submitting and
in order
 
(1) to _minimize_ GRASS user's confusion which version to test, to use and
to give feedback for improvements and bug fixing

and

(2) to _reduce_ GRASS dev's burden to maintain, develop, improve and to fix
bugs in trunk and 3 branches
 
I request the retirement of GRASS6.5.svn (=develbranch6) and keep
releasebranch6 for release only in bug fixing mode and trunk and
releasebranch7 for future improvements and development.
 
best regards
Helmut
GRASS user, sometimes lightweight GRASS dev, osgeo charter member
 
[1] http://wiki.osgeo.org/wiki/Vienna_Code_Sprint_2014
[2] http://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Vienna_2014
[3] http://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Sprint_Vienna_2014
[4] http://trac.osgeo.org/grass/browser/grass




-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/too-many-branches-tp5131993p5132059.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] applying for svn writing access

[Helmut Kudrnovsky]

margherita wrote
> Dear PSC,
> 
> in Vienna I've been working on manual pages cleanup on addons for their
> moving to trunk. Since the manual pages in trunk still need a good deal of
> clean up work, I would like to apply for SVN writing access. My OSGeo ID
> is
> madi.
> 
> cheers,
> madi
> 
> -- 
> Best regards,
> 
> Dr. Margherita DI LEO
> Scientific / technical project officer
> 
> European Commission - DG JRC
> Institute for Environment and Sustainability (IES)
> Via Fermi, 2749
> I-21027 Ispra (VA) - Italy - TP 261
> 
> Tel. +39 0332 78 3600

> margherita.di-leo@.europa

> 
> Disclaimer: The views expressed are purely those of the writer and may not
> in any circumstance be regarded as stating an official position of the
> European Commission.
> 
> ___
> grass-psc mailing list

> grass-psc@.osgeo

> http://lists.osgeo.org/mailman/listinfo/grass-psc

I'm not a PSC member, but I'm support to grant write access by following
reason.

the r.stream.*-modules manuals need cleanup and update. as madi worked a lot
with this modules and wrote her own addon script based upon these tools, she
has thematic
background for improving the manuals. write access would ease the update a
lot.



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/applying-for-svn-writing-access-tp5132036p5132037.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Vienna Code Sprint 2014: Meet (also) GRASS GIS developers

[Helmut Kudrnovsky]

Markus Neteler wrote
> Dear all,
> 
> in case you didn't see it yet:
> 
> OSGeo » Code Sprint 2014
>Get together, hack, decide, tackle large geospatial problems, have
> fun, and explore a city.
> March 24th to 28th. Vienna, Austria.
> http://vienna2014.sprint.osgeo.org/
> 
> Register at:
> http://wiki.osgeo.org/wiki/Vienna_Code_Sprint_2014
> 
> We could consider it as a GRASS GIS Community Sprint oppurtunity, too :-)
> 
> Best
> Markus
> ___
> grass-psc mailing list

> grass-psc@.osgeo

> http://lists.osgeo.org/mailman/listinfo/grass-psc

 
I'm not a PSC member, but from here in Vienna +1




-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Vienna-Code-Sprint-2014-Meet-also-GRASS-GIS-developers-tp5094267p5094988.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] [GRASS-web] authorization reproduction

[Helmut Kudrnovsky]

maybe something for the PSC? from the GRASS-web-ML (Wed Oct 23):

http://lists.osgeo.org/pipermail/grass-web/2013-October/004568.html

--

Dear Sir

I am preparing a book entitled "Connaissance de la biodiversité 
végétale" in which I wish integrate screenshots of results obtained with 
Grass Gis. My editor "Lavoisier (Tec & Doc)" want reproduction 
authorization for these screenshots. So, I send you anattached letter to 
request this authorization.

I hope that it does not raise problem

Best regards

Jan-Bernard Bouzillé

--






-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/GRASS-web-authorization-reproduction-tp5085402.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] winGRASS6/7 and python - funding to improve the actual situation?

[Helmut Kudrnovsky]

Hi,

as suggested by Margherita, I put it here in the PSC.

there are open tickets related to winGRASS6/7 and python, both osgeo4w-stack
and standalone installer:

- related to nice and smart grass6-addons written in python and winGRASS6

http://trac.osgeo.org/grass/ticket/1555

- related to invoking python-scripts in general

http://trac.osgeo.org/grass/ticket/1871

both are based upon the same issue, finding the python interpreter. so
winGRASS6/7-python could be improved, also with a view to the users.

maybe funding a dedicated python developer to solve this issue would be nice
and worth at some point?






-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.n6.nabble.com/winGRASS6-7-and-python-funding-to-improve-the-actual-situation-tp5033286.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] PSC nomination: Margherita Di Leo

[Helmut Kudrnovsky]

Dear PSC members, dear Community,

I would like to nominate Margherita Di Leo [1] as PSC member.

Margherita has contributed awesome GRASS GIS addons [2]-[6] and is helpful
with users in the ML.
Furthermore she's an active member in the open source GIS community
(OSGeo,GFOSS.it).

Best regards
Helmut


[1] http://wiki.osgeo.org/wiki/User:Madi

[2] https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.basin/
[3] https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.ipso/
[4] https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.wf/
[5] https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.hazard.flood/
[6] https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.stream.preview/



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.n6.nabble.com/PSC-nomination-Margherita-Di-Leo-tp5008302.html
Sent from the GRASS-PSC mailing list archive at Nabble.com.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

FW: Re: [GRASS-PSC] Request for SVN-write-access

[Helmut Kudrnovsky]

-Ursprüngliche Nachricht-
Von: Massimiliano Cannata 
Gesendet: 18.01.10 09:37:20
An: Helmut Kudrnovsky 
Betreff: Re: [GRASS-PSC] Request for SVN-write-access

+1 fro me too.
Win-GRASS related experts are welcome.

Maxi

Helmut Kudrnovsky wrote:
> hi,
>
> recently I've helped in Windows-related things (testing, building 
> WinGrass-installer for testing, etc.) and SVN-write-access would make this 
> easier.
>
> So I've read and accepted the Legal aspects of code contributions (RFC2) and 
> request for SVN-write-access.
>
> My OSGEO-ID is hellik
>
> best regards
> Helmut
>
>
> ___
> Preisknaller: WEB.DE DSL Flatrate für nur 16,99 Euro/mtl.! 
> http://produkte.web.de/go/02/
>
>   
> 
>
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc
>   


-- 

Dr. Eng. Massimiliano Cannata
Responsabile Area Geomatica
Istituto Scienze della Terra
Scuola Universitaria Professionale della Svizzera Italiana
Via Trevano, c.p. 72
CH-6952 Canobbio-Lugano
Tel: +41 (0)58 666 62 14
Fax +41 (0)58 666 62 09 





Kostenlos tippen, täglich 1 Million gewinnen: zum WEB.DE MillionenKlick!
http://produkte.web.de/go/08/



smime.p7s
Description: S/MIME Cryptographic Signature
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] Request for SVN-write-access

[Helmut Kudrnovsky]

hi,

recently I've helped in Windows-related things (testing, building 
WinGrass-installer for testing, etc.) and SVN-write-access would make this 
easier.

So I've read and accepted the Legal aspects of code contributions (RFC2) and 
request for SVN-write-access.

My OSGEO-ID is hellik

best regards
Helmut


___
Preisknaller: WEB.DE DSL Flatrate für nur 16,99 Euro/mtl.! 
http://produkte.web.de/go/02/



smime.p7s
Description: S/MIME Cryptographic Signature
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc