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

[Vaclav Petras via grass-psc]

+1, Vaclav

On Tue, 14 May 2024 at 13:46, Anna Petrášová via grass-psc <
grass-psc@lists.osgeo.org> wrote:

> +1 for me!
> Anna
>
> On Tue, May 14, 2024 at 12:29 PM Veronica Andreo via grass-psc <
> grass-psc@lists.osgeo.org> wrote:
>
>> Dear PSC,
>>
>> Linda has just completed her student grant project and submitted the
>> final report (forwarded below).
>>
>> I hereby propose to approve her final report and issue the second
>> payment.
>>
>> 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 start with my +1
>>
>> Vero
>>
>>
>> -- Forwarded message -
>> De: Linda Karlovská via grass-dev 
>> Date: lun, 13 may 2024 a las 14:15
>> Subject: [GRASS-dev] Final reports for Mini project 2024: Easy command
>> history navigation through the History browser panel
>> To: GRASS developers list , <
>> grass-u...@lists.osgeo.org>
>>
>> Hello everyone,
>>
>> I am sending the short report for weeks 7-9 and the final report of the
>> Mini Project devoted to improving GUI, particularly the History browser
>> pane. The goal of this project was to provide a user with a better command
>> history navigation and I think it was quite successful :-), you can have a
>> look at screenshots here: [1]
>>
>> *What did I complete during weeks 7-9?*
>> I completed the PR [2]
>> implementing time node branching in the history tree. Moreover, I also
>> added a button to update the current region based on the region used during
>> command execution (PR [3]).
>> Besides that, I introduced icons representing command status (success,
>> failed, running, aborted, unknown) and added them in front of history
>> entries (PR [4]).
>>
>> Thanks Anna Petrasova for the valuable comments in the reviews!
>>
>> *Final report*
>> *Abstract*
>>
>> This project builds upon the work initiated during the OSGeo sprint in
>> Prague in the summer of 2023, which focused on creating a new History
>> Browser panel to facilitate access to the command history. Although the new
>> History Browser panel became available in the GRASS development version
>> starting December 8th (refer to the PR [5]), initially it provided only a
>> basic, single-level display of commands from the history log, with the
>> capability to relaunch commands but lacking detailed command information.
>> This project aims to enhance the basic functionality by incorporating
>> several improvements.
>>
>> *The state of the art BEFORE the start of the Mini project:*
>> The History Browser panel displayed a simple tree of command entries
>> loaded from a plain-text history log. It had only the capability to
>> relaunch commands.
>>
>> *The state of the art AFTER Mini project:*
>> Implemented changes include:
>>
>>- Transitioning the plain text format of the history log
>>(.wxgui_history) to JSON format, allowing more information to be stored 
>> for
>>each executed command. Newly, the log stores information about the
>>timestamp, command status, runtime duration, region settings, and mask
>>usage.
>>
>>
>>- Instead of implementing the initially planned context option "Show
>>Info" and displaying a small dialog with process information, the history
>>pane was redesigned into two sections. The upper part features the history
>>tree, while the lower part includes two static boxes presenting 
>> information
>>stored in the history log. The first box contains general details, and the
>>second box displays the computational region during command execution.
>>
>>
>>- Adding a symbol in front of each command in the tree based on the
>>command's status.
>>
>>
>>- Branching the tree based on the date of command execution - tree is
>>branched into days and sorted from the Today node to older nodes. Command
>>nodes are sorted from the oldest to the newest.
>>
>> The task of filtering commands based on status was not addressed during
>> the project due to higher-priority issues that emerged:
>>
>>- Adding the "Update current region" button, which dynamically
>>updates the region based on the executed command and its information 
>> stored
>>in the JSON-formatted history log.
>>- Introducing a new Delete option in the command tree
>>- Rearranging the Export History button
>>
>> *Next Steps:*
>> Possible improvements for the History browser pane:
>>
>>- Fixing of command status for nonsense entries (already noted here:
>>[6]):
>>- Sorting the commands in the history tree from the newest to oldest
>>(seems more logical)
>>- Implementing efficient refresh methods (currently all nodes are
>>refreshed when adding a command)
>>- Showing the complete error text if a command fails. (Now there is a
>>“failed” status written but no clue what 

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

[Vaclav Petras via grass-psc]

I would like to point out that Linda has 87 merged PRs (not 95 which is the
number of closed PRs), but still it is +1 from me! :-)))

https://github.com/OSGeo/grass/pulls?q=is%3Apr+author%3Alindakladivova+is%3Aclosed+is%3Amerged

On Wed, 24 Jan 2024 at 04:01, Martin Landa via grass-psc <
grass-psc@lists.osgeo.org> wrote:

> 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+
>
> - currently proposed PRs (open):
> 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
> [2]
> 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
>
> --
> 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] [Motion] Approve Linda's student grant project and issue first payment

[Vaclav Petras via grass-psc]

+1, Vaclav

On Thu, 21 Dec 2023 at 10:38, Anna Petrášová via grass-psc <
grass-psc@lists.osgeo.org> wrote:

> +1
> Anna
>
> On Thu, Dec 21, 2023 at 9:44 AM Veronica Andreo via grass-psc <
> grass-psc@lists.osgeo.org> 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
>>
> ___
> 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] Fw: Aw: Re: [Motion] Proposing Edouard Choinière as a new core developer

[Vaclav Petras via grass-psc]

Seeing Edouard's work, I'm very happy to have Edouard on board!

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

[GRASS-PSC] Budget for 2024, sprint, OSGeo budget request

[Vaclav Petras via grass-psc]

Dear PSC members and others,

Please, see the planned budget for GRASS GIS for 2024:

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

The request for OSGeo is on OSGeo wiki:

https://wiki.osgeo.org/wiki/GRASS_GIS_Budget_2024

We are also sending a separate request for our community meeting (aka
sprint):

https://wiki.osgeo.org/wiki/GRASS_GIS_Community_Meeting_2024:_Budget

After asking Angelos Tzotsos (OSGeo President), it is clear that OSGeo
expects a sprint budget request to be separate from project budget request.
After discussion between Vaclav, Vero, Anna, and Helmut, we are treating
the community meeting as an event with its own budget separate from the
GRASS GIS project budget, although the event is organized by a members of
the GRASS GIS community and the GRASS GIS project will use its budget to
support the event. Ignoring some past confusion about the requests to
OSGeo, this is practically what we did in 2023, but we are clarifying the
situation now and we are following the OSGeo budget system better.

The OSGeo budget is available at:

https://wiki.osgeo.org/wiki/OSGeo_Budget_2024

If you want to modify the budget or have any questions, please contact me
(the GRASS GIS treasurer) before Tuesday, Dec 19 (Wednesday, Dec 20 is the
OSGeo budget request deadline). PSC members, this does not require a
motion, but you can raise your concerns to me or publicly if needed.

The budget and requests were prepared by Vaclav (me) with contributions
from Vero, Anna, and Helmut with further support from Markus, Martin,
Helena, Huidae, and Michael. Thank you, all!

Best,
Vaclav

PS: I contacted Michael Smith (OSGeo Treasurer), to reopen the discussion
about paying for DeepL integration with Weblate which Markus started. This
item is not in the budget because it is OSGeo-wide, not just GRASS GIS
specific.
___
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

[Vaclav Petras via grass-psc]

Hi Markus,

On Tue, 12 Dec 2023 at 12:22, Markus Neteler  wrote:

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

I think I'm in a situation where I don't know what I don't know. I do know
I don't have write access to the ledger. Maybe we can use one of our
upcoming meetings to catch up on that.

Thanks,
Vashek
___
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

[Vaclav Petras via grass-psc]

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 <
grass-psc@lists.osgeo.org> wrote:

> Hi everyone,
>
> Thanks Vashek for volunteering for this role. I agree with Helena though,
> so I'll do my best to help out.
>
> Voting results:
> Martin Landa: +1
> Markus Neteler: +1
> Helena Mitasova: +1
> Anna Petrasova: +1
> Michael Barton: +1
> Huidae Cho: +1
> Helmut Kudrnovsky: +1
> Veronica Andreo: +1
> Vaclav Petras: 0
>
> I hereby declare this motion as passed.
>
> Best,
> Vero
>
> El lun, 4 dic 2023 a las 6:09, Huidae Cho via grass-psc (<
> grass-psc@lists.osgeo.org>) escribió:
>
>> +1
>>
>> Best,
>> Huidae
>> --
>> Huidae Cho, Ph.D., GISP
>> GRASS GIS Developer
>> https://idea.isnew.info/
>> Sent from my phone
>>
>> On Mon, Dec 4, 2023, 5:52 PM Martin Landa via grass-psc <
>> grass-psc@lists.osgeo.org> wrote:
>>
>>> Dear all,
>>>
>>> so 2. 12. 2023 v 17:17 odesílatel Markus Neteler via grass-psc <
>>> grass-psc@lists.osgeo.org> napsal:
>>>
>>> +1
>>>
>>> Thanks Vashek for volunteering on the position of the new new treasurer!
>>>
>>> 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
>>
> ___
> 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

[Vaclav Petras via grass-psc]

+1, Vaclav

On Fri, 1 Dec 2023 at 09:49, Michael Barton via grass-psc <
grass-psc@lists.osgeo.org> wrote:

> +1
> _
>
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (
> https://scas.asu.edu)
> Professor, School of Human Evolution & Social Change (
> https://shesc.asu.edu)
> Director, Center for Social Dynamics & Complexity (
> https://complexity.asu.edu)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
>
> Executive Director, Open Modeling Foundation (
> https://openmodelingfoundation.github.io)
> Director, Network for Computational Modeling in Social & Ecological
> Sciences (https://comses.net)
>
> personal website: http://www.public.asu.edu/~cmbarton
>
>
> On Dec 1, 2023, at 4:29 AM, Veronica Andreo via grass-psc <
> grass-psc@lists.osgeo.org> wrote:
>
> +1
>
> Vero
>
> El vie, 1 dic 2023 a las 5:39, Martin Landa via grass-psc (<
> grass-psc@lists.osgeo.org>) escribió:
>
>> 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://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!fYXY1AAsLYhm8AIrbQ6lFD0-Omfr57g-bgZfc6rEEMkPzbc4sVyDEEvUvV-tsBpTzr2v_YcNKMnoMXTrTayTeavF4Rs$
>
>
> ___
> 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] Preservation of Spearfish data set on Zenodo

[Vaclav Petras]

On Wed, 9 Aug 2023 at 09:02, Peter Löwe  wrote:

> Hi PSC,
>
> earlier this year it was agreed to deposit the Spearfish dataset on Zenodo.
>
> The original GRASS4-dataset finally just got its DOI:
>
> https://doi.org/10.5281/zenodo.7930523
>
> The Spearfish datasets for GRASS5/6/7/8 will be added as versions with
> their own version DOI.
>
> Here's a question regarding possible redundancvies:
>
>
> 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
___
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

[Vaclav Petras]

+1

On Mon, 15 May 2023 at 22:26, Huidae Cho  wrote:

> +1
>
> Huidae
> --
> Huidae Cho, Ph.D., GISP
> GRASS GIS Developer
> https://idea.isnew.info/
> Sent from my phone
>
> On Mon, May 15, 2023, 2:11 PM Markus Neteler  wrote:
>
>> +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 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] RFC: Version Numbering

[Vaclav Petras]

Yes, that's what I mean, PSC approves by email, but reviews (e.g.,
implementation, wording, comments for rejection by PSC members, ...) should
go to the PR.

On Fri, 12 May 2023 at 18:13, Michael Barton  wrote:

> I guess you mean approve by email.
>
> +1
>
> Michael
> _
>
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (
> https://scas.asu.edu)
> Professor, School of Human Evolution & Social Change (
> https://shesc.asu.edu)
> Director, Center for Social Dynamics & Complexity (
> https://complexity.asu.edu)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
>
> Executive Director, Open Modeling Foundation (
> https://openmodelingfoundation.github.io)
> Director, Network for Computational Modeling in Social & Ecological
> Sciences (https://comses.net)
>
> personal website: http://www.public.asu.edu/~cmbarton
>
>
> On May 12, 2023, at 2:16 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
> <https://urldefense.com/v3/__https://github.com/OSGeo/grass/pull/2357__;!!IKRxdwAv5BmarQ!aYbJRl4qIi-rEkGLH4U8lmgCVCS9xaJYmT6AAI2EkyDwbFyRx40PEE9_U01oQF-p3ys0D8scwlJdnd2TbaRdWN8$>
>
> Use Files changed > Display the rich diff to view the RFC itself.
>
> PSC members, please approve or reject this RFC (-1, 0, +1).
>
> 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://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!aYbJRl4qIi-rEkGLH4U8lmgCVCS9xaJYmT6AAI2EkyDwbFyRx40PEE9_U01oQF-p3ys0D8scwlJdnd2TpCqIJRQ$
>
>
>
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] RFC: Version Numbering

[Vaclav Petras]

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

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

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

[Vaclav Petras]

Hi Peter,

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.

Best,
Vaclav


> There are already several GRASS-related datasets on Zenodo:
> https://wiki.osgeo.org/wiki/DOI#GRASS_GIS
>
> One indicator of their relevance for science are the access- and download
> numbers from Zenodo, e.g. https://zenodo.org/record/3359632#.ZCBTjXZBxD8
>
> Kind regards,
> Peter
>
> 
>
> ___
> 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 student grant final report and make the 2nd payment

[Vaclav Petras]

+1

On Tue, 14 Mar 2023 at 10:14, Veronica Andreo  wrote:

> Dear all,
>
> This is a kind reminder for those of you that haven't done so to please
> cast your vote in this motion so we can proceed to issue the second payment
> to Linda.
>
> Thanks!
> Vero
>
> El lun, 6 mar 2023 a las 16:44, Helmut Kudrnovsky ()
> escribió:
>
>> +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]>, <
>> grass-u...@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]
>> 

Re: [GRASS-PSC] [Board] Travis usage of GRASS

[Vaclav Petras]

Thank you, Helmut. Michael Smith contacted me and other people privately a
couple hours ago. The confusion was resolved and scaling down the
subscription should not have any impact on us. We can revisit this on
grass-dev, but there is probably no need.

On Tue, 14 Feb 2023 at 16:06, Helmut Kudrnovsky  wrote:

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

[GRASS-PSC] Welcome Helmut Kudrnovsky

[Vaclav Petras]

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 
is here: "We welcomed Helli as a new PSC member following the procedure
defined in Feb 2021
 and
the results of 2020's election
."

Welcome, Heli!

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

[Vaclav Petras]

Thanks Vero. Keeping focus on the 40th bday sprint and using the existing
grant program makes sense as well as the numbers for the sprint - as far as
I understood what OSGeo asks for, we need to seek sponsorship for it anyway.

Vaclav

On Fri, 20 Jan 2023 at 13:31, Veronica Andreo  wrote:

> Hi all,
>
> I'd try to get into the Google Summer of Docs first. If that doesn't work,
> we can assign one of the 2 budgeted student grants to documentation tasks.
>
> Since the budget presentation deadline is today, I will complete the OSGeo
> table (https://wiki.osgeo.org/wiki/OSGeo_Budget_2023) asking for 5000 usd
> mainly for GRASS GIS 40th bday community sprint and student grants. See the
> details at: https://wiki.osgeo.org/wiki/GRASS_GIS_Budget_2023 and
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2023.
>
> Cheers,
> Vero
>
> El vie, 20 ene 2023 a las 13:49, Michael Barton ()
> escribió:
>
>> I think it is a good idea. The docs are very important but for a lot of
>> reasons often get lower priority.
>>
>> Michael
>> _
>>
>> C. Michael Barton
>> Associate Director, School of Complex Adaptive Systems (
>> https://scas.asu.edu)
>> Professor, School of Human Evolution & Social Change (
>> https://shesc.asu.edu)
>> Director, Center for Social Dynamics & Complexity (
>> https://complexity.asu.edu)
>> Arizona State University
>> Tempe, AZ 85287-2701
>> USA
>>
>> Executive Director, Open Modeling Foundation (
>> https://openmodelingfoundation.github.io)
>> Director, Network for Computational Modeling in Social & Ecological
>> Sciences (https://comses.net)
>>
>> personal website: http://www.public.asu.edu/~cmbarton
>>
>>
>> On Jan 20, 2023, at 8:39 AM, Markus Neteler  wrote:
>>
>> 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://urldefense.com/v3/__https://developers.google.com/season-of-docs/docs/timeline__;!!IKRxdwAv5BmarQ!dZCTWD1i4KdlFTwbbn2snZP_fbm_K-uQhpFLEqhyV88msQjJY7YnlADF8p9e2U-h65NBxN3hEXnwfnNE3gk$
>> )
>> - 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://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!dZCTWD1i4KdlFTwbbn2snZP_fbm_K-uQhpFLEqhyV88msQjJY7YnlADF8p9e2U-h65NBxN3hEXnwGvfioIU$
>>
>>
>> ___
>> 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 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

[Vaclav Petras]

+1

On Sat, 14 Jan 2023 at 11:07, Helena Mitasova via grass-psc <
grass-psc@lists.osgeo.org> wrote:

> +1
>
> Helena Mitasova
> Professor, Department of Marine, Earth and Atmospheric Sciences
> Associate Director and Faculty Fellow, Center for Geospatial Analytics
> North Carolina State University
> Raleigh, NC 27695-8208
> hmit...@ncsu.edu
>
>
> "All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.”
>
>
>
>
> On Jan 14, 2023, at 10:48 AM, Michael Barton 
> wrote:
>
> +1
>
> Michael Barton
> School of Human Evolution  Change
> School of Complex Adaptive System Science
> Center for Social Dynamics & Complexity
> Arizona State University
>
> ...Sent from my iPad
>
> On Jan 14, 2023, at 7:24 AM, 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
> --
> 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://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!fksJhZUk1YAOnU30J33KBzYACHtZROncnnmWEqLv6Nwdk1XHsgJIEKE7jmzwPFUB59nuPnRrIPWQ4hBe2ZpxFqY$
>
> ___
> 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 mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

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

[Vaclav Petras]

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

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

[Vaclav Petras]

+1

On Fri, 11 Nov 2022 at 14:27, Anna Petrášová  wrote:

> 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] Important question about GRASS Mac binaries

[Vaclav Petras]

On Tue, 16 Aug 2022 at 14:00, Michael Barton  wrote:

>
> Is there storage for the GRASS project where these can go?
>

They can be uploaded as assets to releases at GitHub, see e.g.:

https://github.com/OSGeo/grass/releases/tag/8.2.0

Having binaries on the development platform seems quite natural, it is done
by other projects, and in the future the whole thing would ideally happen
automatically.

It's not huge but not tiny. Currently at about 13 GB for all. If not, I may
> look into creating an OSF or Zenodo community I can use.
>

There are cases of software binaries at Zenodo:

https://zenodo.org/record/4659370

We are already using Zenodo, so that would make sense. The issued DOIs for
binaries in addition to the source code may cause confusion, though. Zenodo
has a main DOI for a "project" and a DOI for each version of the "project".
The main DOI is a redirect to the latest version. For source code, we have
some confusion there already with latest, because it is latest by release
date, not by version number. This would likely be the same for binaries.

OSF would probably work too, but you won't be using most of its project
management features and I don't know how good it is for simple cases (where
Zenodo works well).

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

Re: [GRASS-PSC] Grass birthday, upcoming PSC meeting and stickers

[Vaclav Petras]

I'm expecting some discussion too, but more of an open-ended community
discussion, but it depends on who joins. Toasted bread :-))) Yes, I'll,
too, be toasting with milk or something.

Following up on the link privately.


On Thu, 28 Jul 2022 at 16:35, Michael Barton  wrote:

> Can you send the link today. It is quite early for me tomorrow. Are
> discussing things or just toasting? Also a bit early for a toast for me
> (unless it is toasted bread).
>
> Michael
> _
>
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (
> https://scas.asu.edu)
> Professor, School of Human Evolution & Social Change (
> https://shesc.asu.edu)
> Director, Center for Social Dynamics & Complexity (
> https://complexity.asu.edu)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
>
> Executive Director, Open Modeling Foundation (
> https://openmodelingfoundation.github.io)
> Director, Network for Computational Modeling in Social & Ecological
> Sciences (https://comses.net)
>
> personal website: http://www.public.asu.edu/~cmbarton
>
>
> On Jul 28, 2022, at 1:27 PM, Vaclav Petras  wrote:
>
> For birthday call tomorrow, I'll send it tomorrow an hour before the
> meeting. For PSC meeting in two weeks, I need to check.
>
> On Thu, Jul 28, 2022, 3:53 PM Michael Barton 
> wrote:
>
>> Are you sending us a Zoom link or is it the same as last time?
>>
>> Michael
>> _
>>
>> C. Michael Barton
>> Associate Director, School of Complex Adaptive Systems (
>> https://scas.asu.edu)
>> Professor, School of Human Evolution & Social Change (
>> https://shesc.asu.edu)
>> Director, Center for Social Dynamics & Complexity (
>> https://complexity.asu.edu)
>> Arizona State University
>> Tempe, AZ 85287-2701
>> USA
>>
>> Executive Director, Open Modeling Foundation (
>> https://openmodelingfoundation.github.io
>> <https://urldefense.com/v3/__https://openmodelingfoundation.github.io/__;!!IKRxdwAv5BmarQ!akolvVahNoJo26gXBi2s8N6Qk--AKWlbyuL6cC4KRRE-gx8itZdh27njcWvUxDRWSET0uuhC9SVKKr8JvtvbXHA$>
>> )
>> Director, Network for Computational Modeling in Social & Ecological
>> Sciences (https://comses.net
>> <https://urldefense.com/v3/__https://comses.net__;!!IKRxdwAv5BmarQ!akolvVahNoJo26gXBi2s8N6Qk--AKWlbyuL6cC4KRRE-gx8itZdh27njcWvUxDRWSET0uuhC9SVKKr8JaNuR4iw$>
>> )
>>
>> personal website: http://www.public.asu.edu/~cmbarton
>>
>>
>> On Jul 28, 2022, at 12:03 AM, Veronica Andreo 
>> wrote:
>>
>> Hi Vashek,
>>
>> Thanks for your reply! I'll ping you in the chat regarding stickers then
>> :)
>>
>> The suggested time for this friday "GRASS 39 b-day" sounds good to me!
>> I'll send out an invite to the lists and then, tomorrow before the meeting
>> you can send the link as we have done before :)
>>
>> For the PSC meeting , yes, it would be great if you can take over this
>> time. If my plans change then, I'll join as well.
>>
>> See you tomorrow!
>> Vero
>>
>> El mié, 27 jul 2022 a las 20:53, Vaclav Petras ()
>> escribió:
>>
>>> Hi Vero!
>>>
>>> On Wed, 27 Jul 2022 at 12:00, Veronica Andreo 
>>> wrote:
>>>
>>>>
>>>> I am reaching out for different reasons:
>>>> - *Stickers*: I'm thinking it would be nice to take some GRASS
>>>> stickers to FOSS4G, no? Shall we order them? Maybe 500 or even more, and
>>>> then each of us can get some to take to other events. If you agree I can
>>>> order them and get them delivered in brussels or have them sent elsewhere
>>>>
>>>>
>>>
>>> Yes, that sounds great. Let's chat off the list about what to get.
>>>
>>>
>>>> - *GRASS birthday* this friday: Last year we did the psc meeting on
>>>> grass birthday, maybe we are already too close to the date this time?? What
>>>> do you think?
>>>>
>>>
>>> Maybe, not a PSC meeting, but more a community call. We can gather
>>> feedback on things like 8.2, single window, ... What about Friday 15:00 UTC?
>>>
>>> 15:00 UTC
>>> 17:00 CET
>>> 11am ET
>>> 8am MT
>>>
>>>
>>>> - *Upcoming PSC meeting*: the planned date is Friday August 12th.
>>>> Unfortunately that day got a bit complicated for me with traveling. Clearly
>>>> you can still meet that day or we can also move it to FOSS4G and so some of
>>>> us will be in person. What do you say?
>>>>
>>>
>>> ...and some people won't be at FOSS4G in person. Let's have a virtual
>>> meeting on the 12th. I can take over organizing that one.
>>>
>>> Vaclav
>>>
>> ___
>> grass-psc mailing list
>> grass-psc@lists.osgeo.org
>>
>> https://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!ZyM79ADcI-UvajDgD89sotGpPbMDCVds6IS4QRK8SSNNJ0sdl_NmGR8BvJY9TmkIcmjXQbDbQAVy_9a-KqQYLYY$
>>
>>
>>
>
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Grass birthday, upcoming PSC meeting and stickers

[Vaclav Petras]

For birthday call tomorrow, I'll send it tomorrow an hour before the
meeting. For PSC meeting in two weeks, I need to check.

On Thu, Jul 28, 2022, 3:53 PM Michael Barton  wrote:

> Are you sending us a Zoom link or is it the same as last time?
>
> Michael
> _
>
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (
> https://scas.asu.edu)
> Professor, School of Human Evolution & Social Change (
> https://shesc.asu.edu)
> Director, Center for Social Dynamics & Complexity (
> https://complexity.asu.edu)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
>
> Executive Director, Open Modeling Foundation (
> https://openmodelingfoundation.github.io)
> Director, Network for Computational Modeling in Social & Ecological
> Sciences (https://comses.net)
>
> personal website: http://www.public.asu.edu/~cmbarton
>
>
> On Jul 28, 2022, at 12:03 AM, Veronica Andreo 
> wrote:
>
> Hi Vashek,
>
> Thanks for your reply! I'll ping you in the chat regarding stickers then :)
>
> The suggested time for this friday "GRASS 39 b-day" sounds good to me!
> I'll send out an invite to the lists and then, tomorrow before the meeting
> you can send the link as we have done before :)
>
> For the PSC meeting , yes, it would be great if you can take over this
> time. If my plans change then, I'll join as well.
>
> See you tomorrow!
> Vero
>
> El mié, 27 jul 2022 a las 20:53, Vaclav Petras ()
> escribió:
>
>> Hi Vero!
>>
>> On Wed, 27 Jul 2022 at 12:00, Veronica Andreo 
>> wrote:
>>
>>>
>>> I am reaching out for different reasons:
>>> - *Stickers*: I'm thinking it would be nice to take some GRASS stickers
>>> to FOSS4G, no? Shall we order them? Maybe 500 or even more, and then each
>>> of us can get some to take to other events. If you agree I can order them
>>> and get them delivered in brussels or have them sent elsewhere
>>>
>>
>> Yes, that sounds great. Let's chat off the list about what to get.
>>
>>
>>> - *GRASS birthday* this friday: Last year we did the psc meeting on
>>> grass birthday, maybe we are already too close to the date this time?? What
>>> do you think?
>>>
>>
>> Maybe, not a PSC meeting, but more a community call. We can gather
>> feedback on things like 8.2, single window, ... What about Friday 15:00 UTC?
>>
>> 15:00 UTC
>> 17:00 CET
>> 11am ET
>> 8am MT
>>
>>
>>> - *Upcoming PSC meeting*: the planned date is Friday August 12th.
>>> Unfortunately that day got a bit complicated for me with traveling. Clearly
>>> you can still meet that day or we can also move it to FOSS4G and so some of
>>> us will be in person. What do you say?
>>>
>>
>> ...and some people won't be at FOSS4G in person. Let's have a virtual
>> meeting on the 12th. I can take over organizing that one.
>>
>> Vaclav
>>
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
>
> https://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!ZyM79ADcI-UvajDgD89sotGpPbMDCVds6IS4QRK8SSNNJ0sdl_NmGR8BvJY9TmkIcmjXQbDbQAVy_9a-KqQYLYY$
>
>
>
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Grass birthday, upcoming PSC meeting and stickers

[Vaclav Petras]

Hi Vero!

On Wed, 27 Jul 2022 at 12:00, Veronica Andreo  wrote:

>
> I am reaching out for different reasons:
> - *Stickers*: I'm thinking it would be nice to take some GRASS stickers
> to FOSS4G, no? Shall we order them? Maybe 500 or even more, and then each
> of us can get some to take to other events. If you agree I can order them
> and get them delivered in brussels or have them sent elsewhere
>

Yes, that sounds great. Let's chat off the list about what to get.


> - *GRASS birthday* this friday: Last year we did the psc meeting on grass
> birthday, maybe we are already too close to the date this time?? What do
> you think?
>

Maybe, not a PSC meeting, but more a community call. We can gather feedback
on things like 8.2, single window, ... What about Friday 15:00 UTC?

15:00 UTC
17:00 CET
11am ET
8am MT


> - *Upcoming PSC meeting*: the planned date is Friday August 12th.
> Unfortunately that day got a bit complicated for me with traveling. Clearly
> you can still meet that day or we can also move it to FOSS4G and so some of
> us will be in person. What do you say?
>

...and some people won't be at FOSS4G in person. Let's have a virtual
meeting on the 12th. I can take over organizing that one.

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

[Vaclav Petras]

On Wed, 18 May 2022 at 14:56, Markus Neteler  wrote:

>
> I have added as an idea, to showcase selected GRASS GIS commands
> (those which have a (nice) screenshot in the manual, for easier
> publishing).
>

To get an overview of images in the manual pages, use the manual gallery:

https://grass.osgeo.org/grass83/manuals/manual_gallery.html
___
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

[Vaclav Petras]

+1, Vaclav

On Tue, 19 Apr 2022 at 17:17, Veronica Andreo  wrote:

> Dear PSC,
>
> Caitlin 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 Caitlin and her mentors for your work and
> commitment! Thanks as well to those testing and providing feedback along
> the process! Great work Caitlin!! Congratulations!
>
> I start with my +1 !!
>
> Vero
>
> -- Forwarded message -
> De: Caitlin Haedrich 
> Date: lun., 18 abr. 2022 19:25
> Subject: [GRASS-dev] grass.jupyter Mini Project Final Report
> To: , 
>
>
> Hi all,
>
> Last week, we wrapped a final push on grass.jupyter and are excited for
> its official release with GRASS 8.2. Here's my final report along with a
> summary of grass.jupyter changes introduced as part of the project. Thank
> you all for your support, feedback and testing over the past few months!
>
> *The state of the art BEFORE the start of the Mini Project:*
> During GSoC 2021, we created “grass.jupyter”, a package that improves the
> integration of GRASS GIS and Jupyter with a set of functions for displaying
> GRASS data in Jupyter Notebooks. In its previous state, “grass.jupyter”
> allows users to create static visuals and simple interactive maps. However,
> several additional features are needed to allow Jupyter users to fully and
> easily access the power GRASS, including space-time dataset visualization
> and more options for interactive mapping.
>
> *Project Goals*:
> In preparation for the stable release of grass.jupyter with GRASS 8.2,
> this project had three main goals: (1) create space time dataset
> visualizations for use in Jupyter Notebooks, (2) improve the integration of
> GRASS with folium (leaflet library for Python) and (3) write a function for
> displaying vector attributes in nicely-formatted tables (using Pandas or
> Geopandas). Along the way, we also wanted to finalize the naming of
> grass.jupyter classes and create documentation (thank you Vaclav Petras).
>
> *The state 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)
> 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
> an

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

[Vaclav Petras]

+1 for Linda!

On Fri, Mar 4, 2022, 7:09 AM Markus Neteler  wrote:

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

[Vaclav Petras]

Hi Michael,

This looks more like a grass-dev topic, than grass-psc. I'm adding
grass-dev, please remove grass-psc when (if) you reply.

I'll let others comment on the tarball and website and comment on the Git
and GitHub part. +1 for Nickals' answer.

Git is definitely a valid way of getting source code for a build and
perhaps a preferred one since there is all the extra metadata for files.
Maybe we should work on clarifying whether that's really the preferred way.

When using Git locally, you need to be careful if you are using your fork
or the upstream, OSGeo repo. If you do a new clone from GitHub, it should
be pretty clear what you used.

Clone by default gets the default branch which is main, so you need to
switch to another branch (`git switch` in modern Git, `git checkout` in old
Git):

git switch releasebranch_8_0
git switch --detach 8.0.0

git checkout releasebranch_8_0
git checkout 8.0.0

When we one does repetitive clones (e.g., in CI), you can do a shallow
clone with --branch (which works for tags too) to get just one given state
of the repo:

git clone --depth 1 --branch releasebranch_8_0
git clone --depth 1 --branch 8.0.0

When using GitHub, the link Download ZIP which is under the green Clone
button respects the current branch which you set using the combo-box at the
right side or using the "8 branches" link. You can get, e.g.,

https://github.com/OSGeo/grass/archive/refs/heads/releasebranch_8_0.zip

On top of what Nicklas said about the release, you can also use the "124
tags" link which takes you to an overview page with links for all tags
(==releases in our case).

https://github.com/OSGeo/grass/tags

Best,
Vaclav

On Mon, 14 Feb 2022 at 11:16, Michael Barton  wrote:

> I stand corrected. I am not sure that I have the current 8.0 stable
> release. Cloning gives me the main repository, not 8.0.0 stable. I can
> check out a branch but need to make sure that I've got the stable release
> 8.0.0. The reason is that I'm trying to package this in sync with other
> platforms. It looks like the 8.0.0 branch was updated recently. So it is
> not the fixed stable release of 17 days ago.
>
> Michael
> _
>
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (
> https://scas.asu.edu)
> Professor, School of Human Evolution & Social Change (
> https://shesc.asu.edu)
> Director, Center for Social Dynamics & Complexity (
> https://complexity.asu.edu)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
>
> Executive Director, Open Modeling Foundation (
> https://openmodelingfoundation.github.io)
> Director, Network for Computational Modeling in Social & Ecological
> Sciences (https://comses.net)
>
> personal website: http://www.public.asu.edu/~cmbarton
>
>
> On Feb 14, 2022, at 9:08 AM, 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. This is fine for people who want dev versions. But I would
> think that some people just want the package. I eventually cloned one from
> GitHub, but even there, it is not transparent how to get the stable release
> vs. an updated version. Even on GitHub, the clone/download button seemed to
> be missing.
>
> While I could get the software, it seems like we should put back in a link
> to the source code packages somewhere.
>
> Michael
> _
>
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (
> https://scas.asu.edu)
> Professor, School of Human Evolution & Social Change (
> https://shesc.asu.edu)
> Director, Center for Social Dynamics & Complexity (
> https://complexity.asu.edu)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
>
> Executive Director, Open Modeling Foundation (
> https://openmodelingfoundation.github.io)
> Director, Network for Computational Modeling in Social & Ecological
> Sciences (https://comses.net)
>
> personal website: http://www.public.asu.edu/~cmbarton
>
>
>
> ___
> 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] GRASS DOI

[Vaclav Petras]

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

Once we decide where the ORCIDs should go, we can start to collect them
with PRs.


On Thu, Jan 13, 2022 at 9:46 AM Michael Barton 
wrote:

> I agree about including ORCID ID.
>
> Here is mine: -0003-2561-1927
>
> Michael Barton
> School of Human Evolution  Change
> School of Complex Adaptive System Science
> Center for Social Dynamics & Complexity
> Arizona State University
>
> ...Sent from my iPad
>
> On Jan 13, 2022, at 7:30 AM, Huidae Cho  wrote:
>
> 
> All,
>
> I agree with Peter. +1 for ORCIDs.
>
> Best,
> Huidae
>
> On Thu, Jan 13, 2022 at 9:23 AM Peter Löwe  wrote:
>
>> Hi all,
>> I'm not part of the PSC but would like to strongly encourage to
>> include ORCIDs.
>> Once this is achieved, credit for each following GRASS release will
>> automatically be transferred to all ORCID accounts in the commiters list.
>> Commiters without an ORCID will still benefit from the citation options
>> ("Cite as") on the GRASS landing page at Zenodo.
>>
>> Seems like none of the other OSGeo projects using DOI has implemented
>> that (except for an early proof of content for the ploewe/MOSS github repo
>> -> https://doi.org/10.5281/zenodo.4931427
>> <https://urldefense.com/v3/__https://doi.org/10.5281/zenodo.4931427__;!!IKRxdwAv5BmarQ!JZ25YcMjdi1ZLlqFRywxJVJPUTzsYYdqel0skeCmzfSIPcLofjQy9rYoSegCL7oIH0s$>
>> :-) ).
>> Could be another first for the GRASS project !
>>
>> Best,
>> Peter
>>
>> 
>>
>>
>> *Gesendet:* Donnerstag, 13. Januar 2022 um 14:28 Uhr
>> *Von:* "Veronica Andreo" 
>> *An:* "Vaclav Petras" 
>> *Cc:* "GRASS-PSC" 
>> *Betreff:* Re: [GRASS-PSC] GRASS DOI
>>
>>
>> El jue, 13 ene 2022 a las 3:19, Vaclav Petras ()
>> escribió:
>>
>>>
>>> On Wed, Jan 12, 2022 at 4:40 PM Markus Neteler 
>>> wrote:
>>>
>>>>
>>>> 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
>>>> <https://urldefense.com/v3/__https://github.com/OSGeo/gdal/pull/5101/files__;!!IKRxdwAv5BmarQ!JZ25YcMjdi1ZLlqFRywxJVJPUTzsYYdqel0skeCmzfSIPcLofjQy9rYoSegC6o2eHgE$>
>>>
>>>
>>> .zenodo.json or CITATION.cff both should work now with Zenodo.
>>> CITATION.cff is new, but it works as far as I know. .zenodo.json allows you
>>> to set some Zenodo specific info. CITATION.cff is picked by other systems
>>> such as GitHub or FAIR systems. We could generate one from the other (that
>>> was recommended practice before Zenodo started to support CITATION.cff.
>>>
>>> In case we generate the file from the existing contributors.csv, we can
>>> generate both. Adding ORCiDs there would be nice.
>>>
>>
>> +1 for adding ORCiD for those that have it
>>
>>
>>>
>>> Is contributors.csv or starting a new list with the GitHub committers
>>> like what GDAL did more appropriate?
>>>
>>
>> Maybe a new one is better. It will probably also depend if we want to
>> list all ppl in the contributors.csv or the main xx as in gdal.
>>
>> Vero
>> ___ grass-psc mailing list
>> grass-psc@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-psc
>> <https://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!JZ25YcMjdi1ZLlqFRywxJVJPUTzsYYdqel0skeCmzfSIPcLofjQy9rYoSegCvdpqFxo$>
>> ___
>> grass-psc mailing list
>> grass-psc@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-psc
>> <https://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!JZ25YcMjdi1ZLlqFRywxJVJPUTzsYYdqel0skeCmzfSIPcLofjQy9rYoSegCvdpqFxo$>
>>
>
>
> --
> Huidae Cho, Ph.D., GISP, /hidɛ
> <https://urldefense.com/v3/__http://ipa-reader.xyz/?text

Re: [GRASS-PSC] GRASS DOI

[Vaclav Petras]

On Wed, Jan 12, 2022 at 4:40 PM Markus Neteler  wrote:

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

.zenodo.json or CITATION.cff both should work now with Zenodo. CITATION.cff
is new, but it works as far as I know. .zenodo.json allows you to set some
Zenodo specific info. CITATION.cff is picked by other systems such as
GitHub or FAIR systems. We could generate one from the other (that was
recommended practice before Zenodo started to support CITATION.cff.

In case we generate the file from the existing contributors.csv, we can
generate both. Adding ORCiDs there would be nice.

Is contributors.csv or starting a new list with the GitHub committers like
what GDAL did more appropriate?
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] GRASS DOI

[Vaclav Petras]

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.

Best,
Vaclav

[1] https://github.com/OSGeo/grass/graphs/contributors
[2] https://doi.org/10.5281/zenodo.5176030

On Mon, Jan 3, 2022 at 4:02 PM Helena Mitasova via grass-psc <
grass-psc@lists.osgeo.org> wrote:

> Peter Loewe is including the OSGeo projects' DOI in the Springer Handbook
> chapter about open source geospatial
> and we noticed that the authors names are messy (some are just ID) - I
> assume that this is autogenerated and I am wondering
> what would be the best way to fix it. Vashek, did you set this up? Do you
> have any suggestions?
> Here is the GRASS DOI link
> https://doi.org/10.5281/zenodo.5810537
>
> Thank you, Helena
>
> Helena Mitasova
> Professor, Department of Marine, Earth and Atmospheric Sciences
> Faculty Fellow, Center for Geospatial Analytics
> North Carolina State University
> Raleigh, NC 27695-8208
>
>
> -- Forwarded message -
> From: Peter Löwe 
> Date: Mon, Jan 3, 2022 at 11:09 AM
> Subject: Aw: Re: Open Source Chapter of the Springer Handbook of
> Geoinformation: Status update / New Deadline / Opportunity
> To: Helena Mitasova 
>
>
> Helena,
>
> I just checked the DOI landing page for GRASS GIS (
> https://doi.org/10.5281/zenodo.5810537).
> It's amazing to see how the content has grown.
>
> One minor detail: Your name shows in the list of authors in uppercase
> letters, unlike the other authors. Is this intended ?
>
> 1. Martin Landa, Markus Neteler, Markus Metz, Anna Petrasova, glynnc,
> HamishB, Vaclav Petras, huhabla, Huidae Cho, Luca Delucchi, Pietro, Michael
> Barton, Yann Chemin, Tomas Zigo, Māris Nartišs, ostepok, Helmut Kudrnovsky,
> mlennert, nilason, Stefan Blumentrath, William Kyngesburye, Linda
> Kladivova, aghisla, Veronica Andreo, 積丹尼 Dan Jacobson, Denis Ovsienko,
> madi, HELENA MITASOVA, Carmen Tawalika, Caitlin H.: OSGeo/grass: GRASS GIS
> 8.0.0RC1, (2021)
>
> Cheers,
> Peter
>
> 
>
>
> > Gesendet: Sonntag, 26. Dezember 2021 um 04:57 Uhr
> > Von: "Helena Mitasova" 
> > An: "Peter Löwe" 
> > Cc: "Markus Neteler" 
> > Betreff: Re: Open Source Chapter of the Springer Handbook of
> Geoinformation: Status update / New Deadline / Opportunity
> >
> > Peter,
> >
> > Thank you for sharing the proof - the GRASS history and section looks
> good to me, just a minor request if possible -
> > For the Fig. 30.2 would it be possible to add GRASS GIS to the caption?
> Something like this
> > Examples of geospatial modeling and analysis in GRASS GIS with 2D/3D
> raster data, vector data and tangible interaction.
> >
> > Thank you and let's hope for a Happy New Year,
> >
> > Helena
> >
> > > On Dec 23, 2021, at 4:42 AM, Peter Löwe  wrote:
> > >
> > > Dear co-authors of the Open Source Chapter of the Springer Handbook of
> Geoinformation,
> > >
> > > I hope you are all in good health, ready for the upcoming holiday
> season and the new year.
> > >
> > > Work on the Springer Handbook of Geoinformation has progressed.
> Corrections and updates for all chapters are being implemented and checked.
> The Handbook is now scheduled to be pub

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

[Vaclav Petras]

+1

On Thu, Dec 30, 2021 at 8:48 PM Anna Petrášová 
wrote:

> +1
>
> On Thu, Dec 30, 2021 at 7:22 AM Markus Neteler  wrote:
>
>> +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
>>
> ___
> 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] Fwd: Re: [Motion] Approve Linda's proposal for GRASS mini grant

[Vaclav Petras]

Thank you, Moritz. In my comment, I just wanted to clarify for anyone from
the community what happened in private. I agree it is not a sustainable
solution.

On Thu, Dec 16, 2021 at 3:04 PM Moritz Lennert 
wrote:

> Sent this from the wrong address...
>
>
>  Courriel d’origine 
> De : Moritz Lennert
> Envoyé : 16 décembre 2021 21:01:28 GMT+01:00
> À : grass-psc@lists.osgeo.org, Vaclav Petras ,
> Veronica Andreo 
> Cc : GRASS-PSC 
> Objet : Re: [GRASS-PSC] [Motion] Approve Linda's proposal for GRASS mini
> grant
>
> 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 just
> received an application from Caitlin. I'll forward it to the PSC in a
> direct mail.
>
> Moritz
>
> Le 16 décembre 2021 20:03:08 GMT+01:00, Vaclav Petras <
> wenzesl...@gmail.com> a écrit :
> >+1
> >
> >For the sake of clarity, I'll just add that PSC received the proposal
> >privately through Moritz and that's when the "previous discussion"
> happened.
> >
> >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
> >>
> ___
> 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

[Vaclav Petras]

+1

For the sake of clarity, I'll just add that PSC received the proposal
privately through Moritz and that's when the "previous discussion" happened.

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

[Vaclav Petras]

On Tue, Nov 16, 2021 at 11:53 AM Moritz Lennert <
mlenn...@club.worldonline.be> wrote:

> ...to move toward the competition model, but
> I'm not a big fan of it as it generally means many people doing a lot of
> work for free.
>

That may not be exactly our case since - according to the current draft on
the wiki page - the program involves mentorship, so you do get the benefit
of being mentored. The technical writing GSoC spinoff (which I'm not sure
if it is going on) was supposed to be "like GSoC," but without pay.

>From our project work amount, the mentorship-and-possible-award program
will require more commitment to the mentorship than just the work/grant
program where the mentorship might be optional. Perhaps it could be two
independent programs, but the idea here is you have to get mentored in
order to be eligible, so we reward not only the result, but also the
professional development.

However, I'm open to a simple awards program without mentorship as well.
People now work on the project for many different reasons and when done,
students could newly apply for an award. Just work on GSoC (and potentially
any future OSGeo or GRASS paid work) would be excluded from being eligible
(no double-dipping to the OSGeo pool).

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

Re: [GRASS-PSC] Moving sponsoring to Open Collective

[Vaclav Petras]

On Sat, Sep 4, 2021 at 2:53 AM Nikos Alexandris 
wrote:

> I wonder if this new way can facilitate to "sponsor" work on
> specific issues/user-needs.
> ...
> Say a developer is interested in
> fixing this and he sets a cost for it. The user decides to sponsor this
> specific work and things happen.
>

The facilitation is more useful for crowdfunding a specific task. In the
case above, if a user is interested in paying for a feature, the user can
just contact one of the developers and ask for a quote.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Fwd: [GSoC 2021 - Urgent] Feedback Required Regarding Disbursal of GSoC Org Payments/Mentor Stipend to the Mentors

[Vaclav Petras]

I would likely vote for the funds going to the mentors. However, as for
myself, even if we get the slots, I can't get the money legally anyway, so
I would have to choose GRASS budget for my part. Depending on the
particular GSoC project or mentor combo, identifying the main mentor may
not be clear, so that would be a small hurdle in distributing, but I have
seen other projects in similar context simply letting the main person (in
our case the mentor submitting reviews) distribute the money as they see
fit and I think we would manage that. As for putting it to the GRASS
budget, I don't see a need to keep the money as dedicated to a particular
purpose partially for simplicity and partially because we often focus the
budget on "collaborative development activities" anyway.

Vaclav

On Thu, Apr 29, 2021 at 9:45 PM Michael Barton 
wrote:

> I think this is a good plan.
>
> Michael
>
> Michael Barton
> School of Human Evolution  Change
> School of Complex Adaptive System Science
> Center for Social Dynamics & Complexity
> Arizona State University
>
> ...Sent from my iPad
>
> On Apr 29, 2021, at 6:07 PM, Helena Mitasova  wrote:
>
> 
> I am not sure whether other members of PSC or other GSoC mentors received
> this but here is a message from Rajat regarding the potential GSoC mentor
> compensation. Feel free to read the entire message below but here is the
> important part (note that I was at the board meeting
> where this was discussed and the feedback from the board was that osgeo
> will give the funds to the participating projects to use as they see fit.)
> So if you have ideas about what is the best procedure to receive and
> distribute the funds for the GRASS project
> please share them here on the PSC list and I will compile them and provide
> to Rajat (note that this would be $1200 if we get 3 slots)
>
> As a backup mentor I would vote for all funds going to the main mentor or
> to cover some collaborative development activity (in the past
> it would have been e.g. travel to code sprint).
>
> Helena
>
> Our decision as administrators is to reach out to the projects’ PSC for
> your comments about the following idea.
>
>- GSoC team will deposit $400 per accepted proposal
>- The project can claim the money and distribute it to the “main”
>mentors and “backup” mentors as they see fit.
>- The claim can be done after the GSoC team deposits the stipend to
>   the OSGeo organization.
>
>
> This idea has not yet been approved by the board, we need your input to
> refine the idea and procedure. Based on your inputs, we will list the
> possible options and forward them to the OSGeo board for their comments.
>
>
>
> Begin forwarded message:
>
> *From: *Rajat Shinde 
> *Subject: **[GSoC 2021 - Urgent] Feedback Required Regarding Disbursal of
> GSoC Org Payments/Mentor Stipend to the Mentors*
> *Date: *April 29, 2021 at 3:11:29 PM EDT
> *To: *Helena Mitasova 
> *Cc: *"gsoc-adminosgeo.org
> "
> , Rahul Chauhan 
>
> Dear Prof. Mitasova,
>
> Greetings!
> I am sending this email with regards to the Google Summer of Code (GSoC)
> 2021 stipend for mentors. This is OSGeo’s 15th year participating in the
> GSoC 2021 and GRASS GIS is one of the participating projects under the
> OSGeo umbrella organization. Also, this is our second year working as
> OSGeo-GSoC administrators team, and since last year it came to our
> attention that mentors were not getting remuneration for their work. We
> feel that this is very unfortunate and lacks incentive for the mentors to
> continue mentoring. Moreover, mentoring for GSoC is a full-time commitment
> and requires a lot of effort (which might vary depending on the coding and
> administration mentoring).
>
> In this regard, I had a meeting with the board on April 26 [1] and it was
> clear to me that the GSoC program does make a deposit to OSGeo. Citing
> below from the website for reference:
>
> [1]
> https://wiki.osgeo.org/wiki/Board_Meeting_2021-04-26#Google_Summer_of_Code_organization_payment_discussion
> 
>
> “$400 per student developer for your organization (often called the mentor
> stipend) though the money does not generally go to the actual mentor. One
> payment is sent to the org, and if the org wishes to disburse the funds to
> their mentors they are welcome to do that on their own.” [2]
>
> [2]
> https://developers.google.com/open-source/gsoc/help/org-payments#i_included_in_your_payment
> 

Re: [GRASS-PSC] [motion] Language standard support for C and C++ in GRASS GIS

[Vaclav Petras]

+1 Vaclav

On Mon, Mar 22, 2021 at 3: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
> ___
> 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] Statement Vaclav Petras

[Vaclav Petras]

Dear GRASS community,

Thank you for a nomination for a second term at PSC. I've been at PSC since
2016 and a core developer since 2012. I'm working in academia mostly on
developing or helping people to develop code for research. I think I have
touched a lot of files in the GRASS GIS code base, but according to the
command below [1], it is only 16.5%. I presented GRASS GIS at various
conferences and taught it to graduate students and at workshops. My
favorite presentation I did is perhaps *33 Years Of GRASS GIS As An
Innovation Platform* [2, 3].

As a PSC member, I will vote for sponsoring crucial or special project
needs on top of sprints and promotion what we did so far. Additionally, I
would like to see more support and promotion within the project for people
and organizations which provide some kind of GRASS GIS support or services
as part of their business. For example, I think that a developer seeking
crowdfunding should not only be supported by the project, but there should
be an established and ongoing process of doing that. Therefore, I will
support proposals which make promotion, sponsoring, customer-contractor
matching, and contributing and thanking by money more common and present in
our community.

Best,
Vaclav

[1] python -c "print(100 * $(git log --pretty='%H' --author='wenzeslaus' |
while read commit_hash; do git show --oneline --name-only $commit_hash |
tail -n+2; done | sort | uniq | xargs ls -d 2>/dev/null | wc -l) / $(git
ls-tree -r master --name-only | wc -l))"
[2] https://ncsu-geoforall-lab.github.io/grass-as-a-platform/ncgis2017.html
[3] https://youtu.be/Vv5NnPg6MOY
___
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

[Vaclav Petras]

+1 for Tomas.

I also second Anna's request for a clear policy.

On Sun, Nov 22, 2020 at 2:22 AM Margherita Di Leo 
wrote:

> +1
> Regards
>
> Inviato da iPhone
>
> Il giorno 22 nov 2020, alle ore 04:03, Helena Mitasova 
> ha scritto:
>
> +1 from me too.
>
> Thank you Tomas for all your work, Helena
>
> On Nov 21, 2020, at 9:16 PM, Anna Petrášová  wrote:
>
> Definitely +1
>
> I would suggest with any new core devs we should have a policy that all
> their PRs go through at least 1 review for some time. This policy would be
> nice for all PRs (even from current devs), because it significantly
> improves the code, but of course it's not always possible or practical
> given the workload.
>
> Anna
>
> On Fri, Nov 20, 2020 at 5: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
>> ___
>> 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
>
>
> Helena Mitasova
> Professor, Department of Marine, Earth and Atmospheric Sciences
> Faculty Fellow,
> Center for Geospatial Analytics
> North Carolina State University
> Raleigh, NC 27695-8208
> hmit...@ncsu.edu
>
>
>
> ___
> 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 mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [Motion] First payment for new GRASS GIS Hugo based web site

[Vaclav Petras]

+1

Step in the right direction.

Vaclav

On Mon, Feb 17, 2020 at 7:58 AM Markus Neteler  wrote:

> Dear PSC,
>
> After a long time of discussions and developments, the first prototype
> of the new GRASS GIS website is available at
> https://staging.grass.osgeo.org/ with the code available at
> https://github.com/OSGeo/grass-website .
>
> The entire project follows what has been discussed earlier:
> https://grasswiki.osgeo.org/wiki/Website_migration_plan_2019
> We requested OSGeo in 2019 to cover the development with 6000 USD, see
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2019 - given the
> delays it was moved to
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2020 . See therein
> for the related OSGeo budget wiki page.
>
> This motion is to vote on the first payment of 4000 USD (out of 6000
> USD) to the developer, Nicolas Bozon (https://github.com/nbozon). Some
> issues are still open and he scheduled to continue further work on the
> Hugo code later this month.
>
> The money transfer can then be directly done from OSGeo to the
> developer (already clarified with the OSGeo treasurer).
>
> Motion:
> I start with a +1.
>
> Best,
> Markus
>
> PS: once the web site is sufficiently (!) completed we'll switch the
> DNS entries:
>   https://grass.osgeo.org/ --> https://old.grass.osgeo.org/ , and
>   https://staging.grass.osgeo.org/ --> https://grass.osgeo.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] GRASS GIS stickers reloaded

[Vaclav Petras]

Hi Markus,

On Sun, Feb 2, 2020 at 1:28 PM Markus Neteler  wrote:

> Hi PSC,
>
> Just going back from FOSDEM where I left the remaining stickers I had.
> AFAIK new stickers were recently printed and handed over in Prag, are
> there still any in Europe?
>

I guess there are be some in Prague, but...


>
> Or do we need to print more?


...I would suggest to print more. I did not go through the approved budged
in detail, but it looks like we have a budged for it as we planned. Rather
than sending them from one person to the other, I would prefer everybody
who needs them to have their supply (i.e., you are going for a conference,
you get them yourself - we can exchange some know-how if needed). Also,
they are not flyers, so they don't go out of date. What do you think?


> (btw: any non-plastic ones existing?)
>

The ones I did were vinyl. I guess separate orders help in getting what you
think is the best for the given audience.

Best,
Vaclav


> 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] [MOTION] Prague 2019 Community Sprint Reimbursements

[Vaclav Petras]

On Tue, Jan 7, 2020 at 8:22 AM Martin Landa  wrote:

> Dear PSC members,
>
> based on thread [1] I am taking liberty to start motion related to
> GRASS GIS Community Sprint Prague 2019 [2] (see reports [3]). Overall
> expenses contains two major items:
>
> * food & drinks (112.78EUR), and
> * promotional materials printed (222.20EUR)
>
> See [3], tab "Reimbursements".
>
> This motion is about asking for 100% funding of participation expenses
> listed above [3].
>
> I will start with +0 since I am also asking for funding .
>

Same here, so +0 too.

Vaclav


>
> Thanks for voting in advance, best regards, Martin
>
> [1] https://lists.osgeo.org/pipermail/grass-psc/2019-December/002075.html
> [2]
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Community_Sprint_Prague_2019
> [3]
> https://grasswiki.osgeo.org/wiki/Talk:GRASS_GIS_Community_Sprint_Prague_2019#Participants_and_Reports
> [4]
> https://docs.google.com/spreadsheets/d/1CWvgUKRc2bUUUfQIFVFFMzk2R6JSOLVJj_WWfwKT13A/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

Re: [GRASS-PSC] GRASS GIS Budget request for 2020

[Vaclav Petras]

On Mon, Jan 6, 2020 at 6:58 AM Markus Neteler  wrote:

> On Mon, Jan 6, 2020 at 12:57 PM Moritz Lennert
>  wrote:
> > Am 6. Januar 2020 12:50:12 MEZ schrieb Markus Neteler  >:
> > >Hi PSC,
> > >
> > >Below the email which I had sent to the board.
> > >However, we need to modify the request as code sprint support needs to
> > >be requests separately from the general (current) request.
> > >
> > >Hence, I have separated out the sprint requests (to be submitted later
> > >this year):
> > >https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2020#Planned_Expenses


Thank you. I like that the new budget is more compatible with OSGeo. I was
just thinking that the meetup item should go to the the events [1] since it
is likely to be more outreach event than a sprint. Do you have any thoughts
on that?

Perhaps more importantly, I don't understand where the "delta to be
fundraiser" is coming from, although it generally makes sense to have it.

[1] https://lists.osgeo.org/pipermail/grass-psc/2019-December/002089.html


>
> > >
> > >Now:
> > >- please verify that the figures are right
> >
> > Sprint budget thus only includes catering and possibly some venue costs ?
> >
> > If that is the case, 2000 seems a lot, no ?
>
> I think this was inserted by @Vaclav Petras  AFAIK.
> Maybe he can enlighten us?
>

I quickly went through the past sprint budgets and got cost for each budget
item and then combined them. The previous sprints were lucky enough and
were always able to reduce one or more items in the budget to zero or
nearly zero (e.g., free venue), so this counts for kind of a worst case,
e.g., no attendees being able to sponsor their travel. Otherwise, I assume
same funding usage Jody mentions [2]. That seem to fit with what we were
doing so far.

The separate travel grants item is for travel to other sprints than the
GRASS GIS ones, e.g., the OSGeo one, possibly even to other events for
promotional purposes, and also as a backup if more is needed for the GRASS
GIS sprint.

Please, let me know if you have more questions about this and/or make any
changes. I just provided my best guess for a 2020 plan.

Vaclav

[2] https://lists.osgeo.org/pipermail/grass-psc/2020-January/002099.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] GRASS GIS budget 2020 - was: Re: [Board] OSGeo Budget 2020

[Vaclav Petras]

Markus, PSC,

On Fri, Dec 27, 2019 at 5:56 AM Markus Neteler  wrote:

> Dear PSC,
>
> Please revisit our budget, we need to communicate it to the board ideally
> by tomorrow.
>
> No remarks?
>

Nothing regarding the items from me since I created the draft. The website
is not clear to me, but I think it needs to be included again (with a note
added to OSGeo Budget). Another thing is that in the past we did not split
the request into project budget, events, and sprints. This year, this would
turn out:

Project: 2900 EUR + website
Events: 500 EUR
Sprints: 5500 EUR

Lastly, the amounts need to converted from EUR to USD (as of today,
google.com).

Project: 3240.66 USD + website
Events: 558.74 USD
Sprints: 6146.09 USD

Best,
Vaclav


>
> Thanks
> Markus
>
> Markus Neteler  schrieb am Mo., 23. Dez. 2019, 20:32:
>
>> Dear PSC,
>>
>> Our draft budget is at
>>
>> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2020
>>
>> We have to ask to carry over the web site payment, maybe more?
>>
>> Please revisit it, comments welcome.
>>
>> Thanks
>> Markus
>>
>> -- Forwarded message -
>> Von: Angelos Tzotsos 
>> Date: Mo., 23. Dez. 2019, 19:35
>> Subject: Re: [Board] OSGeo Budget 2020
>> To: 
>> Cc: OSGeo Discussions , OSGeo Board <
>> bo...@lists.osgeo.org>
>>
>>
>> Hi all,
>>
>> Please submit your budget requests by Dec 30th so we can start drafting
>> the 2020 budget.
>>
>> Happy holidays,
>> Angelos
>>
>> On 12/9/19 9:38 PM, Angelos Tzotsos wrote:
>> > 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 is reaching out to all committees, including project steering
>> > committees, to help plan our budget for 2020.
>> >
>> > As in last year, the board is discussing about assigning a starting
>> > budget of 2000$ 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).
>> >
>> > For projects with more of a plan (to pursue a specific goal) projects
>> > are welcome to send a more detailed request for approval (see detailed
>> > budget requests from 2019 e.g.
>> > https://wiki.osgeo.org/wiki/GvSIG_Budget_2019)
>> >
>> > A good idea is to focus on OSGeo participation, for example attending
>> > the AGM or OSGeo code sprint. Also keep in mind OSGeo goals as an
>> > organization, (e.g. interoperability goal: CITE compliance or
>> > participation developing new standards)
>> >
>> > 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_2020
>> >
>> > ideally by Dec 30 ahead 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
>> Charter Member
>> 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 mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] GRASS GIS budget 2020 - was: Re: [Board] OSGeo Budget 2020

[Vaclav Petras]

Hi Peter,

On Fri, Dec 27, 2019 at 7:39 AM "Peter Löwe"  wrote:

> Hello Markus, hi PSC,
>   ...
> The preliminary planned 2020 budget is currently slightly lower than the
> 2019 budget, however we should be prepared to answer questions on how we
> really intend to spend the overall amount - and to avoid overbudgeting as
> in 2019 (provided that the numbers are complete).
>

I can't comment on the concrete sprint/travel budget, but there are
multiple reason why over-budgeting in 2019 happened. For sprints, we ask a
certain sum from OSGeo, but then we raise funds ourselves (as requested by
OSGeo) as well as minimize the expenses. I have some plans for
strikers/promo/swag, but I started to carry them out only now. Then there
is of course the website. So, I would say it is natural - at least for the
way how we currently organize the budget.

Best,
Vaclav


>
> Kind regards,
> Peter
>
>
>
> 
>
>
> *Gesendet:* Freitag, 27. Dezember 2019 um 11:56 Uhr
> *Von:* "Markus Neteler" 
> *An:* GRASS-PSC 
> *Betreff:* [GRASS-PSC] GRASS GIS budget 2020 - was: Re: [Board] OSGeo
> Budget 2020
> Dear PSC,
>
> Please revisit our budget, we need to communicate it to the board ideally
> by tomorrow.
>
> No remarks?
>
> Thanks
> Markus
>
> Markus Neteler  schrieb am Mo., 23. Dez. 2019, 20:32:
>
>> Dear PSC,
>>
>> Our draft budget is at
>>
>> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2020
>>
>> We have to ask to carry over the web site payment, maybe more?
>>
>> Please revisit it, comments welcome.
>>
>> Thanks
>> Markus
>>
>> -- Forwarded message -
>> Von: Angelos Tzotsos 
>> Date: Mo., 23. Dez. 2019, 19:35
>> Subject: Re: [Board] OSGeo Budget 2020
>> To: 
>> Cc: OSGeo Discussions , OSGeo Board <
>> bo...@lists.osgeo.org>
>>
>>
>> Hi all,
>>
>> Please submit your budget requests by Dec 30th so we can start drafting
>> the 2020 budget.
>>
>> Happy holidays,
>> Angelos
>>
>> On 12/9/19 9:38 PM, Angelos Tzotsos wrote:
>> > 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 is reaching out to all committees, including project steering
>> > committees, to help plan our budget for 2020.
>> >
>> > As in last year, the board is discussing about assigning a starting
>> > budget of 2000$ 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).
>> >
>> > For projects with more of a plan (to pursue a specific goal) projects
>> > are welcome to send a more detailed request for approval (see detailed
>> > budget requests from 2019 e.g.
>> > https://wiki.osgeo.org/wiki/GvSIG_Budget_2019)
>> >
>> > A good idea is to focus on OSGeo participation, for example attending
>> > the AGM or OSGeo code sprint. Also keep in mind OSGeo goals as an
>> > organization, (e.g. interoperability goal: CITE compliance or
>> > participation developing new standards)
>> >
>> > 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_2020
>> >
>> > ideally by Dec 30 ahead 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
>> Charter Member
>> 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 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] GRASS GIS Community Sprint Prague 2019 Expenses

[Vaclav Petras]

Hi Moritz and all,

Sorry for getting back to this late. I'm picking up where you and Martin
left.

On Thu, Dec 12, 2019 at 10:43 AM Moritz Lennert <
mlenn...@club.worldonline.be> wrote:

> On 12/12/19 10:51, Martin Landa wrote:
> > Hi Moritz,
> >
> > čt 12. 12. 2019 v 10:13 odesílatel Moritz Lennert
> >  napsal:
> >> - IIUC, most of the budget you are asking for is actually for
> >> promotional material (stickers, magnets) that are only indirectly linked
> >> to the code sprint, or ? I would therefore suggest to separate the two
> >
> > make sense to me. In reality you are suggesting two separated voting
> > procedures, right?
>
> Well, don't know if we really need two voting procedures, or just one
> vote combining the two expenses...
>

I guess it could be one email with two items and we would add -1/0/+1 to
each of these, but the reason it is there is that the division is not
clear: couple of the promotional items are for the people at the sprint,
e.g. stickers for their laptops (small amount, but why order just few?) and
rest for people to take with them from the sprint and give out later on
(indirect, yes, but would not happen without the sprint).


>
> >
> >> requests to make that more apparent. Your actual "sprinting" costs are
> >> <60€, or ?
>

The above potentially applies to other events too. It just so happened here
that the rest of the expenses are smaller than the promo part of the
budget. I was just quickly going through budgets from the previous sprints
to put something reasonable to the 2020 budget and sometimes the by far
biggest expense is food, sometimes it is travel reimbursements.

Generally, it seems we don't have a clear procedure of assigning the
expenses to different budget items. Are travel grants part of sprint budget
or are on top of it? Or should the actual sprint budget expenses be
combined from budged for sprint, travel grants and promo?

https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2019
https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2020



> >
> > Yes, only one dinner, two lunches + small food.
>
> No beer ??? ;-)
>

As everybody knows, beer is a part of a meal in Prague (today, it can be
also non-alcoholic!). ;-)


> >
> >> - In the report, you write: "We spent several hours over the course of
> >> the sprint discussing different alternatives and finding a best way to
> >> implement the one we have chosen." I see that everything has been
> >> documented in detail on the relevant wiki page:
> >>
> https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/New_Startup#GRASSGISCommunitySprintPrague2019
> ,
> >> but would it be possible summarize the general philosophy on the mailing
> >> list ? I think this is an important part of GRASS GIS and discussion
> >> should be larger.
> >
> > Sure, on the other hand we cannot discuss it forever :-) We have
> > prepared step-by-step roadmap, see [1]. No big revolution, just small
> > but important steps. Feel free to comment!
> >
>
> Yes, I saw that (that's why I already included the same link ;-) ), but
> it is very detailed and so I'm not sure I really understand the big
> picture of the general philosophy you have decided. On the wiki page we
> started out by discussing two general options: "Keep current paradigm,
> but make contact easier" or "Change paradigm" (e.g. "Open into a
> predefined lat-long location but give information message"). IIUC, your
> roadmap follows the first option, or ?
>
> There's just too many trees for me to see the forest ;-)
>

I have added the result of our discussion as another "proposal" which
should be a quick read. One of the reasons I wrote the detailed notes is
that not only the discussion results are available, but the whole
discussion leading to that decision is available too.

https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/New_Startup#ProposalA3Prague2019:Datatreeandbigbuttons

Best,
Vaclav



> Moritz
>
>
> ___
> 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: Migrate SVN and trac tickets to github under OSGeo organization

[Vaclav Petras]

On Thu, Apr 18, 2019 at 4:22 PM Markus Neteler  wrote:

> PSC members,
>
> RFC6 [1] about the migration from OSGeo SVN and tickets on trac to
> github under the OSGeo organization has been up for review since 5th
> of March 2019.
> Since no further comments have been expressed I regard RFC6 as ready
> for a vote by the PSC.
>
> I’ll start with my +1.
>

+1

Just as a heads up. We still have things to address. I made some late
comments to the RFC about best practices and mirroring of issues:

https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub?action=diff=20_version=18
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] git migration

[Vaclav Petras]

On Thu, Apr 11, 2019 at 4:40 PM Markus Neteler  wrote:

> On Wed, Apr 10, 2019 at 4:58 PM Vaclav Petras 
> wrote:
> > On Sun, Apr 7, 2019 at 4:02 PM Markus Neteler  wrote:
> >>
> >>
> >> RFC 6: Migration from SVN to GitHub
> >> https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
> >
> > Looks great. Thanks!
> >
> > One thing it lacks are best practices for using Git. Git is not
> Subversion and we just can't use it as Subversion.
>
> Please suggest a text snippet to add there (or add directly).
>

Added.


> >> It also proposes an exit strategy incl. to implement a
> >> continuous mirror on GitLab.com.
> >
> > How realistic is the continuous mirror? I know GitLab has migration
> tools, but does it have sync as well?
>
> https://docs.gitlab.com/ee/workflow/repository_mirroring.html
> "
> Repository mirroring allows for mirroring of repositories to and from
> external sources. It can be used to mirror branches, tags, and commits
> between repositories.
> A repository mirror at GitLab will be updated automatically. You can
> also manually trigger an update at most once every 5 minutes.
> "
>
> ... looks fine.
>

The mirroring covers only the code, but not the issues which we are also
migrating. The migration does cover them, but the problem is the guarantee
of being able to do the migration when needed. A periodical backup from
GitHub would be probably fine.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Write Access for GRASS Add-ons SVN

[Vaclav Petras]

On Mon, Jan 21, 2019 at 3:35 PM Martin Landa  wrote:

> Hi,
>
> po 21. 1. 2019 v 21:26 odesílatel Vaclav Petras 
> napsal:
> > I can be Brendan's mentor. I already worked with him on the code he is
> planning to submit.
>
> mentor for getting write access to Addons? I thought that there is no
> such requirement. Ma
>

Although the language is not 100% consistent, we require it based on what
is on wiki [1]. Here are the relevant parts of Write access to the
GRASS-Addons-SVN repository:

Rationale:

Write access to the Addons SVN repository is much less rigorous than to the
core source code repository. ... Write access does not require the full
vote of the GRASS-PSC, just the support of one mentor and adherence to our
RFC2 document... As opposed to write access to the Main SVN repository,
write access to the Addons repository is typically initiated by the new
contributor.
Overall:

GRASS developers with write access can grant SVN write access to
contributors (you may contact an active developer, see grass-dev mailing
list archive). The selected developer is a sort of "sponsor/mentor" for the
requester.
Procedure:
...
The request needs to be sent to the GRASS-PSC mailing list, stating that
RFC2 was read and accepted (ideally also suggest a mentor among the
developers). ...
...

Best,
Vaclav

[1]
https://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheGRASS-Addons-SVNrepository
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Write Access for GRASS Add-ons SVN

[Vaclav Petras]

Hi all,

I can be Brendan's mentor. I already worked with him on the code he is
planning to submit.

Best,
Vaclav

On Sat, Jan 19, 2019 at 11:16 PM Brendan  wrote:

> Hello, I would like to request write access for the GRASS Add-ons SVN
> repository. My osgeo_id is baharmon and I would like Vaclav Petras as my
> mentor. I have read and accepted the RFC2.
> Thanks, Brendan
> ___
> 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] Write access to the GRASS-SVN repository Ondřej Pešek

[Vaclav Petras]

+1 Vaclav

On Sun, Jan 20, 2019 at 4:17 PM Martin Landa  wrote:

> Hi,
>
> ne 20. 1. 2019 v 0:44 odesílatel Markus Neteler 
> napsal:
> > > - proposal published: 12 Jan 2019
> > > - voting to be opened on 19 Jan 2019
> >
> > I start with a
> > +1
>
> +1 recently Ondrej started studying for his PhD. under prof. Cepek and
> mine supervision at the CTU in Prague, I willing to be mentor for
> Ondrej. I assume that his  patches/commits will be under wider review
> in the frame of trac tickets/issues. 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] [motion] Bonn Community Sprint funding

[Vaclav Petras]

+1

I'm really pleased we can cover the travel costs. Please, just confirm that
I understand well that except the travel expenses, there is no other cost
for the sprint which needs to be covered (it was budgeted - would be payed
from the 2017 surplus). Regarding the budget in general, all, please note
that re-budgeting or additional funding will be required for additional
code sprints (as the Bonn travel is most of the money we asked from OSGeo
for the code sprints (== travel in our case)).

Best,
Vaclav

On Fri, May 18, 2018 at 2:14 PM, Moritz Lennert <
mlenn...@club.worldonline.be> wrote:

> +1
>
> Moritz
>
>
> Am 18. Mai 2018 18:02:06 MESZ schrieb Helena Mitasova :
>>
>> +1
>>
>> Helena
>>
>> On May 18, 2018, at 11:11 AM, Martin Landa 
>> wrote:
>>
>> Hi,
>>
>> I am taking liberty to start motion thread related to GRASS Community
>> Sprint in Bonn [0,1] organized as part of the OSGeo Code Sprint [2].
>> Our goal is to cover at best all participants travel and accommodation
>> expenses expressed in [3] from our GRASS Budget [4].
>>
>> I will start with +0 since I am also asking for funding as one of
>> participants.
>>
>> Thanks for your feedback, Ma
>>
>> [0] https://grass.osgeo.org/news/75/15/Recap-from-the-OSGeo-Code
>> -Sprint-in-Bonn-2018/
>> [1] https://grasswiki.osgeo.org/wiki/GRASS_GIS_Community_Sprint_Bonn_2018
>> [2] https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018
>> [3] https://docs.google.com/spreadsheets/d/1BgFMiYlLosFjsVUlUCWw
>> ssoxiQB_G7gpkVFgG29gZBM/edit?usp=sharing#gid=5
>> [4] https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2018
>>
>> --
>> 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
>>
>>
>> Helena Mitasova
>> Professor at the Department of Marine,
>> Earth, and Atmospheric Sciences
>> Associate director and faculty fellow at the Center for Geospatial
>> Analytics
>> North Carolina State University
>> Raleigh, NC 27695-8208
>> hmit...@ncsu.edu
>> http://geospatial.ncsu.edu/osgeorel/publications.html
>>
>> "All electronic mail messages in connection with State business which are
>> sent to or received by this account are subject to the NC Public Records
>> Law and may be disclosed to third parties.”
>>
>>
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
>
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [Motion] Print 500 GRASS GIS stickers for the upcoming conferences

[Vaclav Petras]

+1

On Tue, Feb 27, 2018 at 7:12 PM, Anna Petrášová 
wrote:

> +1
>
> Anna
>
> On Tue, Feb 27, 2018 at 7:03 PM, Helena Mitasova  wrote:
> > +1
> >
> > Helena
> >
> > On Feb 27, 2018, at 5:38 PM, Markus Neteler  wrote:
> >
> > hi PSC,
> >
> > since printing needs time, here my motion to approve 150 USD for
> > printing 500 stickers, die cut, 2x2" through stickermule.
> >
> > The current budget plan foresees more than that sum for stickers, so
> > that would be in line with our planning:
> > https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2018
> >
> > I start with a +1.
> >
> > Markus
> > ___
> > grass-psc mailing list
> > grass-psc@lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/grass-psc
> >
> >
> > Helena Mitasova
> > Professor at the Department of Marine,
> > Earth, and Atmospheric Sciences
> > Associate director and faculty fellow at the Center for Geospatial
> Analytics
> > North Carolina State University
> > Raleigh, NC 27695-8208
> > hmit...@ncsu.edu
> > http://geospatial.ncsu.edu/osgeorel/publications.html
> >
> > "All electronic mail messages in connection with State business which are
> > sent to or received by this account are subject to the NC Public Records
> Law
> > and may be disclosed to third parties.”
> >
> >
> > ___
> > grass-psc mailing list
> > grass-psc@lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/grass-psc
> ___
> 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] Proposing Stefan Blumentrath as a new core developer

[Vaclav Petras]

+1 for Stefan Blumentrath as a core developer.

I assume no new thread is needed at this point.

Vaclav

On Tue, Jan 30, 2018 at 10:18 PM, Helena Mitasova  wrote:

> +1
>
> Helena
>
> Helena Mitasova
> Professor, Department of Marine, Earth and Atmospheric Sciences
> Faculty Fellow, Center for Geospatial Analytics
> North Carolina State University
> Raleigh, NC 27695-8208
> http://www4.ncsu.edu/~hmitaso/
> http://geospatial.ncsu.edu/osgeorel/publications.html
>
> email: hmit...@ncsu.edu
> ph: 919-513-1327 <(919)%20513-1327> (no voicemail)
> fax 919 515-7802 <(919)%20515-7802>
>
> On Tue, Jan 30, 2018 at 5:02 PM, Markus Neteler  wrote:
>
>> I turn this into a motion:
>>
>> On Tue, Jan 30, 2018 at 10:48 PM, Markus 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
>>
>>
>> > Best,
>> > Markus
>> >
>> >
>> > [1] https://trac.osgeo.org/grass/wiki/RFC/1_ProjectSteeringCommi
>> tteeGuidelines
>> >
>> > --
>> > Markus Neteler, PhD
>> > http://www.mundialis.de - free data with free software
>> > http://grass.osgeo.org
>> > http://courses.neteler.org/blog
>> ___
>> 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 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

[Vaclav Petras]

On Fri, Jan 5, 2018 at 12:04 PM, Markus Neteler <nete...@osgeo.org> wrote:

> On Fri, Jan 5, 2018 at 6:01 PM, Vaclav Petras <wenzesl...@gmail.com>
> wrote:
> > On Fri, Jan 5, 2018 at 5:37 AM, Markus Neteler <nete...@osgeo.org>
> wrote:
> ...
> >> https://wiki.osgeo.org/wiki/OSGeo_Budget_2018
> >>
> >
> > Both seems in sync to me. I put 2000+1500 for events (grants+sprint) and
> > 1500 (itemized) for promo materials. Do you see something else?
>
> All fine, isn't it?
>


At one point, I wanted to clean up the plan for USD vs EUR, but forgot
about it. We will need to cover the difference from 2017 surplus if needed.
If I remember correctly, the variation in prices I was trying to guess was
higher than the exchange rate anyway.
___
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

[Vaclav Petras]

On Fri, Jan 5, 2018 at 5:37 AM, Markus Neteler <nete...@osgeo.org> wrote:

> On Wed, Nov 15, 2017 at 4:16 AM, Vaclav Petras <wenzesl...@gmail.com>
> wrote:
> > On Mon, Oct 23, 2017 at 3:53 PM, Markus Neteler <nete...@osgeo.org>
> wrote:
> >> I have drafted our budget for 2018 here:
> >>
> >> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2018
> >>
> >> We could use that page to detail how we want to use the funding to be
> >> requested.
> >
> >
> > I updated the budged draft. I added 2000 for travel money, 1500 for the
> > sprint (based on 1st Genova sprint) and added price for promo things
> based
> > on recent events (stickers for Boston) or online price estimates
> > (alliedshirts.com). I was not sure how to mark it as a suggestion. Is
> more
> > detail needed?
>
> We need to keep this page updated:
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2018
>
> At time there are 5000 USD planned here (1500 + 3500), see
> https://wiki.osgeo.org/wiki/OSGeo_Budget_2018
>
>
Both seems in sync to me. I put 2000+1500 for events (grants+sprint) and
1500 (itemized) for promo materials. Do you see something else? Do you want
to add something for website?

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

[Vaclav Petras]

On Wed, Nov 15, 2017 at 10:41 AM, Markus Neteler <nete...@osgeo.org> wrote:

> On Wed, Nov 15, 2017 at 4:16 AM, Vaclav Petras <wenzesl...@gmail.com>
> wrote:
> > On Mon, Oct 23, 2017 at 3:53 PM, Markus Neteler <nete...@osgeo.org>
> wrote:
> >>
> >> On Sat, Oct 21, 2017 at 11:23 PM, Helmut Kudrnovsky <hel...@web.de>
> wrote:
> >> > Markus Neteler wrote
> >> ...
> >> >> 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?
> >>
> >> Could be! But we need to come up with a more detailed plan how we plan
> >> to use the money, otherwise it will not be accepted.
> >>
> >> I have drafted our budget for 2018 here:
> >>
> >> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2018
> >>
> >> We could use that page to detail how we want to use the funding to be
> >> requested.
> >
> >
> > I updated the budged draft. I added 2000 for travel money, 1500 for the
> > sprint (based on 1st Genova sprint) and added price for promo things
> based
> > on recent events (stickers for Boston) or online price estimates
> > (alliedshirts.com). I was not sure how to mark it as a suggestion. Is
> more
> > detail needed?
>
> I guess not at time.
>
> Here we stated 3,500 USD:
> http://wiki.osgeo.org/wiki/OSGeo_Budget_2018#OSGeo_Projects
>


I updated that wiki page too and linked our 2017 and 2018 pages.
___
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

[Vaclav Petras]

On Mon, Oct 23, 2017 at 3:53 PM, Markus Neteler  wrote:

> On Sat, Oct 21, 2017 at 11:23 PM, Helmut Kudrnovsky  wrote:
> > Markus Neteler wrote
> ...
> >> 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?
>
> Could be! But we need to come up with a more detailed plan how we plan
> to use the money, otherwise it will not be accepted.
>
> I have drafted our budget for 2018 here:
>
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2018
>
> We could use that page to detail how we want to use the funding to be
> requested.
>

I updated the budged draft. I added 2000 for travel money, 1500 for the
sprint (based on 1st Genova sprint) and added price for promo things based
on recent events (stickers for Boston) or online price estimates (
alliedshirts.com). I was not sure how to mark it as a suggestion. Is more
detail needed?

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

Re: [GRASS-PSC] [voting] printing of stickers and flyers for FOSS4G Europe

[Vaclav Petras]

+1 from Vaclav for stickers and flyers

On Sat, Jul 22, 2017 at 11:14 AM, Markus Neteler  wrote:

> Dear PSC,
>
> I take liberty to open the voting about reimbursement of Vero Andreo
> for the printing of stickers and flyers for FOSS4G Europe 2017.
> See below for details.
>
> I will start with +1.
>
> Markus
>
>
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] T-shirts for GRASS GIS Community Sprint at FOSS4G-Europe

[Vaclav Petras]

On Sat, Jul 22, 2017 at 8:17 AM, Moritz Lennert <
mlenn...@club.worldonline.be> wrote:

> Please all note that Martin has opened a separate thread with [voting] in
> the subject line. I think it would make things easier if everyone responded
> to that thread.
>

Sorry, Gmail shows this as the voting thread, including Peter's email. I'm
not sure why is Gmail  confused. Please, let us (Peter, Anna, Vaclav) know
in case we need to vote again.

https://lists.osgeo.org/pipermail/grass-psc/2017-July/thread.html


>
> Moritz
>
> On 22/07/17 14:02, Vaclav Petras wrote:
>
>> +1 from Vaclav
>>
>> On Sat, Jul 22, 2017 at 8:00 AM, Anna Petrášová <kratocha...@gmail.com
>> <mailto:kratocha...@gmail.com>> wrote:
>>
>> +1 from Anna
>>
>> On Sat, Jul 22, 2017 at 6:47 AM, "Peter Löwe" <peter.lo...@gmx.de
>> <mailto:peter.lo...@gmx.de>> wrote:
>>  > +1
>>  > Peter
>>  > --
>>  > Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX
>> Mail gesendet.
>>  > Am 22.07.17, 12:40, Martin Landa <landa.mar...@gmail.com
>> <mailto:landa.mar...@gmail.com>> schrieb:
>>  >>
>>  >> Hi,
>>  >>
>>  >> 2017-07-22 11:43 GMT+02:00 Milena Nowotarska
>> <do.mile...@gmail.com <mailto:do.mile...@gmail.com>>:
>>  >> > I would like to ask you for reimbursement for the t-shirts
>> printed for
>>  >> > the
>>  >> > GRASS GIS Community Sprint which will be held today at
>> FOSS4G-Europe
>>  >> > conference. I have printed 10 t-shirts for 466,50 PLN and
>> there is a
>>  >> > need to
>>  >>
>>  >> it's about 110EUR [1], right? I have started voting thread [2].
>>  >>
>>  >> Ma
>>  >>
>>  >> [1] https://themoneyconverter.com/PLN/EUR.aspx
>> <https://themoneyconverter.com/PLN/EUR.aspx>
>>  >> [2]
>> https://lists.osgeo.org/pipermail/grass-psc/2017-July/001737.html
>> <https://lists.osgeo.org/pipermail/grass-psc/2017-July/001737.html>
>>  >>
>>  >> --
>>  >> Martin Landa
>>  >> http://geo.fsv.cvut.cz/gwiki/Landa
>> <http://geo.fsv.cvut.cz/gwiki/Landa>
>>  >> http://gismentors.cz/mentors/landa
>> <http://gismentors.cz/mentors/landa>
>>  >> ___
>>  >> grass-psc mailing list
>>  >> grass-psc@lists.osgeo.org <mailto: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 <mailto: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 <mailto: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 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] T-shirts for GRASS GIS Community Sprint at FOSS4G-Europe

[Vaclav Petras]

+1 from Vaclav

On Sat, Jul 22, 2017 at 8:00 AM, Anna Petrášová 
wrote:

> +1 from Anna
>
> On Sat, Jul 22, 2017 at 6:47 AM, "Peter Löwe"  wrote:
> > +1
> > Peter
> > --
> > Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail
> gesendet.
> > Am 22.07.17, 12:40, Martin Landa  schrieb:
> >>
> >> Hi,
> >>
> >> 2017-07-22 11:43 GMT+02:00 Milena Nowotarska :
> >> > I would like to ask you for reimbursement for the t-shirts printed for
> >> > the
> >> > GRASS GIS Community Sprint which will be held today at FOSS4G-Europe
> >> > conference. I have printed 10 t-shirts for 466,50 PLN and there is a
> >> > need to
> >>
> >> it's about 110EUR [1], right? I have started voting thread [2].
> >>
> >> Ma
> >>
> >> [1] https://themoneyconverter.com/PLN/EUR.aspx
> >> [2] https://lists.osgeo.org/pipermail/grass-psc/2017-July/001737.html
> >>
> >> --
> >> 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 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] Let's approve new core developers

[Vaclav Petras]

On Fri, Jun 16, 2017 at 2:38 AM, Markus Neteler  wrote:

> On Thu, Jun 15, 2017 at 6:31 PM, Moritz Lennert
>  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).
>


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

Re: [GRASS-PSC] Again: Jim Westervelt retirement: May 2017

[Vaclav Petras]

On Mon, May 1, 2017 at 10:00 AM, Anna Petrášová 
wrote:

>
> Vaclav and I are going to be at the University of Illinois at
> Urbana-Champaign between 15-20th of May, so we could potentially
> deliver it in person.  T-shirt with the GRASS ASCII logo would look
> great I think, the problem is we would have to order it now and it
> might be quite costly, because they usually require minimum number of
> T-shirts, and we are not sure about the right size. It would be great
> though to have those T-shirts for conferences, so we can look into
> some options.
>

The T-shirts are usually around $20, but Allied Shirts have a sale right
now. I don't recall seeing T-shirt of this brand, so I can't comment on it.
Anyway, with the ASCII design (which has just one color) we get to $101.15
total when ordering 12 of them ($8.43 per T-shirt). For one T-shirt it is
$20 (it seems one can order it this way, but I'm not sure) and $15 ea for 4
T-shirts. All T-shirts must be one color (and there is limited selection),
but they can be different sizes and for the lower prices per T-shirt still
apply. Also all T-shirts must be one type - Budget (friendly) Unisex in
this case. The size chart is available [1]. A screenshot of the design is
attached (created at alliedshirts.com). We may need to pay extra for rush
delivery.


> We could also do something smaller, e.g., collect signatures and put
> them on a card.


This is nice. It is personal and it has no potential collisions with ones
fashion style. If somebody creates the design and collects the signatures,
we can print it (although I don't know where yet) and deliver it.

Vaclav

[1] http://www.alliedshirts.com/Product/budget-tee
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Write access to addons repository

[Vaclav Petras]

Hi Julien,

On Wed, Apr 26, 2017 at 10:30 AM, Markus Neteler  wrote:

> > The code was written from scratch by myself and Paulo van Breugel is and
> > already under GPL 3 license.


the RFC2 document actually requires GPL >=2 license [1]. Is that OK with
you?

Vaclav

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

Re: [GRASS-PSC] MOTION: approve Markus as GRASS GIS PSC chair

[Vaclav Petras]

+1 for Markus

On Sun, Sep 18, 2016 at 5:50 PM, Anna Petrášová <kratocha...@gmail.com>
wrote:

> +1 for Markus
>
> Anna
>
> On Sun, Sep 18, 2016 at 5:24 PM, Michael Barton <michael.bar...@asu.edu>
> wrote:
> > +1 from me.
> >
> > Michael
> > 
> > C. Michael Barton
> > Director, Center for Social Dynamics & Complexity
> > Professor of Anthropology, School of Human Evolution & Social Change
> > Head, Graduate Faculty in Complex Adaptive Systems Science
> > Arizona State University
> >
> > voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> > fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
> > www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
> >
> >
> > On Sep 18, 2016, at 1:13 PM, Margherita Di Leo <direg...@gmail.com>
> wrote:
> >
> > Thank you Helena, I second this motion!
> >
> > Il domenica 18 settembre 2016, Helena Mitasova <hmit...@ncsu.edu> ha
> > scritto:
> >>
> >> Dear members of PSC, I would like to make a motion to approve Markus
> >> Neteler as PSC chair.
> >>
> >> Helena
> >>
> >> P.S. Just to clarify the procedure - we need somebody to second this
> >> motion and then please all PSC members except Markus email your votes
> here.
> >>
> >> > On Sep 18, 2016, at 2:00 PM, Vaclav Petras <wenzesl...@gmail.com>
> wrote:
> >> >
> >> >
> >> > On Sun, Sep 18, 2016 at 12:45 PM, Markus Neteler <nete...@osgeo.org>
> >> > wrote:
> >> > >> 6 out of 9 PSC members nominated their candidate in 3 days. Since
> all
> >> > >> nominated the same candidate, Markus (who accepts the nomination),
> I
> >> > >> suggest to proceed with elections.
> >> > >
> >> > > +1
> >> >
> >> > Since I can hardly organize it myself, I kindly invite someone to
> >> > organize it.
> >> >
> >> >
> >> > I don't know what was done in the past and I don't see anything at the
> >> > wiki. Based on the current situation described above, it seems to me
> that a
> >> > public vote is fine this time with absolute majority (>=5 members)
> needed to
> >> > pass the vote. I would leave anything more complicated for the next
> >> > elections.
> >> > ___
> >> > grass-psc mailing list
> >> > grass-psc@lists.osgeo.org
> >> > http://lists.osgeo.org/mailman/listinfo/grass-psc
> >>
> >> Helena Mitasova
> >> Professor at the Department of Marine,
> >> Earth, and Atmospheric Sciences
> >> and Center for Geospatial Analytics
> >> North Carolina State University
> >> Raleigh, NC 27695-8208
> >> hmit...@ncsu.edu
> >> http://geospatial.ncsu.edu/osgeorel/publications.html
> >>
> >> "All electronic mail messages in connection with State business which
> are
> >> sent to or received by this account are subject to the NC Public
> Records Law
> >> and may be disclosed to third parties.”
> >>
> >> ___
> >> grass-psc mailing list
> >> grass-psc@lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/grass-psc
> >
> >
> >
> > --
> > Margherita Di Leo
> >
> > ___
> > grass-psc mailing list
> > grass-psc@lists.osgeo.org
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.
> osgeo.org_mailman_listinfo_grass-2Dpsc=CwIGaQ=
> AGbYxfJbXK67KfXyGqyv2Ejiz41FqQuZFk4A-1IxfAU=vxOW6PLS28MPea_
> dWUwPfRf71TAIziRDuFqWJimQN1I=XjAUCdJeZo1tVVJG1AaVQ0snpR0zZN
> 1F9f6r1vtE4rE=CIZcfNbM9kFTYL2vNSD1cDLt9cZb48Mzw_mvpgfGx8M=
> >
> >
> >
> > ___
> > grass-psc mailing list
> > grass-psc@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/grass-psc
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc
>
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS-announce] PSC election 2016 Result

[Vaclav Petras]

On Sun, Sep 18, 2016 at 12:45 PM, Markus Neteler  wrote:

> >> 6 out of 9 PSC members nominated their candidate in 3 days. Since all
> >> nominated the same candidate, Markus (who accepts the nomination), I
> >> suggest to proceed with elections.
> >
> > +1
>
> Since I can hardly organize it myself, I kindly invite someone to organize
> it.



I don't know what was done in the past and I don't see anything at the
wiki. Based on the current situation described above, it seems to me that a
public vote is fine this time with absolute majority (>=5 members) needed
to pass the vote. I would leave anything more complicated for the next
elections.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] funding community meeting in San Michele February 2016

[Vaclav Petras]

On Thu, Feb 18, 2016 at 9:14 AM, Markus Neteler  wrote:

> --> "contributors meeting"
>
> This is something slightly different, of a rather local scale. In this
> particular case we cannot host too many people (I assume likewise not
> in similar cases as Raleygh and Solany)
>


The (monthly) Raleigh meetups are actually open to anybody [1]. However, I
can see that some events might be by invitation only for different reasons
(location restrictions or focus of the event). I think both have their
place and I think the one focused on a specific group of developers is
quite important. Perhaps this is something which should be in the
application form.

[1] https://lists.osgeo.org/pipermail/grass-user/2016-February/073659.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] Fwd: [OSGeo-Discuss] OSGeo-Live metrics going public in next 9.5 release

[Vaclav Petras]

On Mon, Feb 1, 2016 at 8:09 AM, Moritz Lennert  wrote:

> Looking at the GRASS metrics at OpenHub used for OSGeo-Live (see below), I
> find it a pity that addons [1] is seperated from the main branches [2].
> Many new developers have been active recently, mostly coding addons.
>
> Any reason for this separation ? Would it be possible to merge them ?
>


I did it this way on purpose. The development cycle, code quality and code
importance are different. Even the pool of developers is little bit
different. Code stats for addons tell you nothing about the core GRASS
moving forward or not. Also if we decide that the addon is a good
contribution to main GRASS, we move it (e.g. i.segment) which will show the
code in the main stats. So, these are my reasons behind separate stats.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] GRASS-Addons-SVN repository write access request

[Vaclav Petras]

On Tue, Sep 22, 2015 at 9:44 AM, Giuseppe Amatulli <
giuseppe.amatu...@gmail.com> wrote:

> svn add   /home/selv/grass7_svn/grass7/raster/r.stream.watersheds/
>
> svn commit -m "first r.stream.watersheds and r.stream.variables"
>  raster/r.stream.variables/r.stream.variables  --username Elselvaje
> svn: E29: Commit failed (details follow):
> svn: E29: '/home/selv/grass7_svn/grass7/raster/r.stream.variables' is
> not known to exist in the repository and is not part of the commit, yet its
> child
> '/home/selv/grass7_svn/grass7/raster/r.stream.variables/r.stream.variables'
> is part of the commit
>

>From what I see you first add r.stream.watersheds but then you are trying
to commit r.stream.variables or even r.stream.variables/r.stream.variables.

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

Re: [GRASS-PSC] How to modify module folder content in SVN

[Vaclav Petras]

On Mon, Jun 22, 2015 at 5:21 AM, Eva Stopková eva.stopk...@gmail.com
wrote:

 My first idea was to completely replace PCL version, so I did not modify
 them. But then I realized it would be better to save both versions, so at
 first I would like to make them as much identical as possible
 (funcionality, layout). I intend to do this in the coming days.


I didn't get that before, but I agree with Moritz that two versions are not
ideal. Is there any reason to keep both? Performance? Different quality
algorithms/results? Do you have some tests or benchmarks which would
compare them?

In case of keeping both, I think that only option in case of PCL dependency
is that you svn cp the directory with each module:

svn cp v.nnstat v.nnstat.pcl

One version would be pure GRASS and the other PCL (which wouldn't compile
unless for most of the users unless they do additional steps). There would
be unfortunate duplication, but I don't see a way how to write a Makefile
which would create two modules with different dependencies (e.g.
raster/r.colors compiles two modules but it imposes unnecessary
dependencies for each of them).
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] How to modify module folder content in SVN

[Vaclav Petras]

Hi Eva,

On Sat, Jun 20, 2015 at 8:41 AM, Eva Stopková eva.stopk...@gmail.com
wrote:

 Dear all,

 I would like to ask you for advice.

 I have just commited new versions of modules *v.kriging* and *v.nnstat*
 (this commit is incomplete because of the issue described below). But now
 there are pairs of the source codes in C and in C++ in SVN - I replaced
 *kd-tree* (from PCL library) by *R-tree* (which is implemented in GRASS
 GIS) so I also switched back from C++ to C.


Great news! This means that both are now easily usable for all users
without any special effort. Would you like to do the announcement on
grass-user mailing list? (In case you are not subscribed, I can send it for
you.)


 Is it possible in some way to backup older C++ versions including
 changesets in the module folder in SVN?


The previous version is saved in the Subversion repository. You can view it
online using Trac, for example state of v.nnstat at r62698 is here:

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.nnstat?rev=62698

All the changes in the given file or directory are also available through
Trac (@number will take you to the state at that revision, the gearwheel to
the changeset). This is log for v.nnstat:

https://trac.osgeo.org/grass/log/grass-addons/grass7/vector/v.nnstat

You can do the same in the command line using svn commands. This will take
you to the given revision:

svn update -r 62698

and this will give you the last ten commits (newest first, l for limit):

svn log -l 10

Bottom line is that once you committed something it stays there, so you can
safely remove it (svn rm) or rename it (svn mv) and change it but the old
version with all the changes stays in Subversion repository.

I hope this is be enough information for what you need.

Vaclav


PS: grass-dev is the right mailing list to ask this type of question,
grass-psc is for more official things, although the information that we
don't need to use large dependency like PCL library in order to implement
advanced point analysis modules is relevant even for PSC members.

Thank you in advance for your answers.
 Best regards,

 Eva

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

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

Re: [GRASS-PSC] Proposal: Logo variant to include GRASS GIS as name

[Vaclav Petras]

On Wed, Apr 8, 2015 at 4:30 PM, Luca Delucchi lucadel...@gmail.com wrote:

 On 8 April 2015 at 22:25, Markus Neteler nete...@osgeo.org wrote:
  On Wed, Apr 8, 2015 at 3:49 PM, Vaclav Petras wenzesl...@gmail.com
wrote:
 
  On Wed, Apr 8, 2015 at 5:30 AM, Markus Neteler nete...@osgeo.org
wrote:
 
   for a better communication, I would suggest to add the string
GRASS
   GIS under the horizontal line in the logo as a variant of it (so,
   e.g. on the main Web site, upper left logo it is not needed).
  
  
   i.e. something like the central image on the top of:
  
   http://grasswiki.osgeo.org/w/images/GRASSGIS_splash_synthesis.jpg
  
   but without the tag line ?
 
  yes,
 
  Attaching (a screenshot of) what I used in the EGU Python poster (text
added
  in LaTeX, textbf textsf).
 
  and with all written in capital letters: GRASS GIS
 
  Just note that keeping capital letter everywhere will be a challenge
since
  we have all-lower-case in the Startup screen.
 
  Not everywhere. Just in this single version.
  In the past 20-30 years we were pretty open to different logo
incarnations :-)
 
  Your screenshot looks fine, do you have a vector version of it?

As I said it's from poster and it was done in LaTeX. However, I guess it
would be easy to recreate it in Inkscape with Libre Sans Serif.

Is the SVG on the website the one Vincent cleaned up?

 I like it, maybe I would remove a little bit of space between the line
and text.

Can be. This depends on the context (I think I had it differently for
different materials).

 Thanks Vaclav

  thanks
  Markus
 

 --
 ciao
 Luca

 http://gis.cri.fmach.it/delucchi/
 www.lucadelu.org
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] removal of RFC documents from SVN [was: releases schedule]

[Vaclav Petras]

On Fri, Jun 27, 2014 at 7:04 AM, Martin Landa landa.mar...@gmail.com
wrote:

 Hi,

 2014-06-27 9:29 GMT+02:00 Hamish hamis...@yahoo.com:

  Completed RFCs do not belong in a wiki. For bomb-proof full changelog
  disclosure, draft revisions probably belong in the main SVN too.

 I don't think so, see RFC of GDAL, they maintain it on wiki! So...

 Do we have some backup for Trac (wiki pages)? It is possible to obtain
them with history as text, diffs and log messages?

But anyway, it seems to me that nobody wants to update, maintain and read
RFC in SVN, this could be better in Trac.

Vaclav

Martin

 --
 Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa
 ___
 grass-psc mailing list
 grass-psc@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/grass-psc

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

Re: [GRASS-PSC] removal of RFC documents from SVN [was: releases schedule]

[Vaclav Petras]

On Fri, Jun 27, 2014 at 11:29 AM, Martin Landa landa.mar...@gmail.com
wrote:

  Do we have some backup for Trac (wiki pages)? It is possible to obtain
 them

 I guess OSGeo is doing backups, anyway Trac is only one component for
 which I am not doing backups. I will add it to my TODO list.



Thanks, it is good to know that there is/will be more backups.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] releases schedule

[Vaclav Petras]

On Tue, Jun 10, 2014 at 5:18 AM, Markus Neteler nete...@osgeo.org wrote:

  Afterwards do you prefer to simply remove `rfc` directory from source
  code or to replace content of files with link to Trac?

 Removal is probably fine. We just need to catch the link elsewhere
 (mainly Wiki + CMS) and update them. Will just be a few.


Link in SUBMITTING to RFC at Trac wiki might be ideal (as Moritz suggested
for SUBMITTING in another thread).
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] releases schedule

[Vaclav Petras]

On Mon, Apr 21, 2014 at 10:48 AM, Martin Landa landa.mar...@gmail.comwrote:

 Hi,

 2014-04-21 16:44 GMT+02:00 Markus Neteler nete...@osgeo.org:
  The duplication is certainly dangerous here. Trac seems like a proper
 place
  (although this does not completely fit to the Trac wiki rules I
 proposed
  because it does not fit anywhere).
 
  Any objections to move RFC from API manual to trac? Martin
 
  In general fine for me to move it out of the programmer's manual.
  But perhaps we use the GRASS Wiki since we already have several PSC
  related pages there? See
 
  http://grasswiki.osgeo.org/wiki/Category:PSC

 well, my preference would be to move all PSC pages from mediawiki
 (user space) to trac wiki (project management, development). Martin

 This is the kind of pages I don't have clear opinion. One approach is
development-related versus user-related but other approach is
in-development versus state-of-art.

The complication with the first is that user wants to script which is close
to writing C code (e.g. ctypes) and hopefully in the future even close to
GUI. This is my motivation for the in-development versus state-of-art
rule. But RFC/PSC is unclear because it is state-of-are but user does not
care even if he or she is writing C module. Hm, but he or she cares about
RFC when the module is going to addons, so GRASS wiki then?

Vaclav


  --
 Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa

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

Re: [GRASS-PSC] releases schedule

[Vaclav Petras]

On Mon, Apr 21, 2014 at 10:51 AM, Markus Neteler nete...@osgeo.org wrote:

 On Mon, Apr 21, 2014 at 4:48 PM, Martin Landa landa.mar...@gmail.com
 wrote:
 ...
  well, my preference would be to move all PSC pages from mediawiki
  (user space) to trac wiki (project management, development). Martin

 Sure, would make sense. Just the trac-wiki is so ugly :-) Maybe one
 day we get at least a more recent version running... [1].


Oh, I missed that email. I don't want to decide based on the CSS. My main
concern is the cleanness of GRASS wiki (i.e. no proposals, no TODO pages)
and jumping from one wiki to another. The fact is that the current
situation is that all release news, repository, releasing are at Trac, so
PSC may fit there.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] releases schedule

[Vaclav Petras]

On Sun, Apr 20, 2014 at 7:42 AM, Martin Landa landa.mar...@gmail.comwrote:

  We put the proposal to Trac wiki (1), so we can track changes into it. In
  future it can go to (Doxygen) documentation but not now.

 I would say that this proposal should be defined as RFC4 [1]. Are you
 willing to work on it?

 I'm. Not right now, but in next weeks yes. I'm not sure what means work on
it. I have to look at the other RFC what would be the appropriate format
etc. Then I have to go through comments here but I guess more comments are
needed but perhaps after I draft it first.


 BTW, I think that better place for RFC's would be Trac wiki rather
 than API manual (it's duplicated for G6 and G7). What do you think?


The duplication is certainly dangerous here. Trac seems like a proper place
(although this does not completely fit to the Trac wiki rules I proposed
because it does not fit anywhere).

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

Re: [GRASS-PSC] releases schedule

[Vaclav Petras]

On Mon, Mar 31, 2014 at 11:40 AM, Vaclav Petras wenzesl...@gmail.com
 wrote:


 I find that 6 months is a fairly long period to maintain a bugfix-only
 branch. I would rather propose to either branch later, or to allow more
 than just bugfixes into the release branch for 4-5 months before going into
 bugfix-only phase for the last month or two. During the first period new
 features can be ported to the release branch once they have had some
 testing in trunk.


 Moritz, I believe that these are two different things.

 ...

 Second, committing features to both branches is what is taking the time
 from us and creating uncertainty about what is where and what are the
 branches for. I think that this is crucial point and the lengths of time
 periods above should be decided based on this, not the other way around.

 On Mon, Mar 31, 2014 at 11:09 PM, Yann Chemin yche...@gmail.com wrote:

 It looks like we all want to see version numbers move on a yearly basis
 with periods of branching and periods of releasing...


We need to agree on the policy of committing to release branch(es). See my
proposal [1] for details.

[1] http://lists.osgeo.org/pipermail/grass-psc/2014-March/001150.html
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] releases schedule

[Vaclav Petras]

On Mon, Mar 31, 2014 at 11:09 PM, Yann Chemin yche...@gmail.com wrote:

 Should we finalize this policy and implement it?


Probably yes. Does PSC have to vote on this?

We put the proposal to Trac wiki (1), so we can track changes into it. In
future it can go to (Doxygen) documentation but not now.

(1) It does not completely fit into what I think Trac should be used for
but all other things about releases are there anyway.
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] releases schedule

[Vaclav Petras]

On Mon, Mar 31, 2014 at 4:35 AM, Moritz Lennert 
mlenn...@club.worldonline.be wrote:

 On 29/03/14 21:56, Vaclav Petras wrote:

 Inspired by what code sprint people were saying, I put together my
 proposal. It counts with release once a year and a half year bugfixing
 (feature freeze) period before the release. I expect comments and
 criticism and I would be glad to compare this proposal with some other
 proposal.

 Vaclav


 Releasing and branch management should follow these steps:

  1. have trunk
  2. fork release branch , e.g. release_7_1
  3. only bugfixes to release branch, new features (additions,

 refactoring, documentation) only to trunk
  4. release new version based on release branch, , e.g. 7.1.0
  5. only critical bugfixes go to release branch, release patched version

 if needed, e.g. 7.1.1, .7.1.2
  6. fork a new release branch (e.g. release_7_2), set old release branch

 to readonly and continue with point 3.

 It seems that release should be done every year. A new release branch
 should be forked half a year before planned release.


 I find that 6 months is a fairly long period to maintain a bugfix-only
 branch. I would rather propose to either branch later, or to allow more
 than just bugfixes into the release branch for 4-5 months before going into
 bugfix-only phase for the last month or two. During the first period new
 features can be ported to the release branch once they have had some
 testing in trunk.


Moritz, I believe that these are two different things.

First, the lengths of time periods. First question is how often we want to
release MAJOR.MINOR version. Once a year looks good for me but I have no
special reasons for this. The length of period between fork and release can
be probably anything from 1 month to 6 months. The length of period after
release to next release should be the rest so from 6 month to 11.

Second, committing features to both branches is what is taking the time
from us and creating uncertainty about what is where and what are the
branches for. I think that this is crucial point and the lengths of time
periods above should be decided based on this, not the other way around.

Vaclav


 Moritz

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