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

2023-08-09 Thread Peter Löwe
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 ? 

 

Best,

Peter

 



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


Re: [GRASS-PSC] Proposal: Display GRASS DOI icon on project webpage

2023-04-09 Thread Peter Löwe
Hi Vero, all,

 

the DOI badge (and maybe a short explanation what can be done with it) should definitely be included in https://grass.osgeo.org/about/license/

 

However, to get a similar discoverablity effect as for PROJ, GDAL, etc. I would suggest to also put the the icon right under the GRASS logo which sits currently below VIEW GALLERY and LATEST NEWS.

 

This could even become a news item by itself .. ?

 

Best & happy Easter (if applicable),

Peter 

 



 
 

Gesendet: Samstag, 08. April 2023 um 17:07 Uhr
Von: "Veronica Andreo" 
An: "Peter Löwe" 
Cc: grass-psc@lists.osgeo.org
Betreff: Re: [GRASS-PSC] Proposal: Display GRASS DOI icon on project webpage



Hi Peter,

 

I like the proposal, thanks!

 

Where in our website would you suggest to include the DOI badge? Our landing page is already a bit stuffed. This could be an option https://grass.osgeo.org/about/license/ as there's the citation there. What do you think?

 

Vero

 


El sáb, 8 abr 2023 a las 8:03, Peter Löwe (<peter.lo...@gmx.de>) escribió:

Hello PSC,

I would like to propose to include the DOI icon (https://zenodo.org/badge/DOI/10.5281/zenodo.7764250.svg) for GRASS GIS on a prominent spot on the GRASS GIS project page (https://grass.osgeo.org/). This is should require little effort but will result in benefitial consequences and visibility for the project community and GRASS GIS applications across all fields of Science.

It's been over a year that a DOI was registered for GRASS GIS. Other projects, such as PROJ and GDAL have also registered DOI. While this is great in itself, preserving OSGeo projects as part of the scientific record, enabling scientific citation, etc.,  this has not yet been announced to the greater public.

In the meantime other projects such as PROJ, GDAL and Mapserver have already included their DOI icons in their web pages (e.g. https://gdal.org/).

It seems that this alone already suffices to motivate and enable scientists to give due credit to the sofware projects and the project communities by DOI-based citation, including hi-visibility journals such as Nature.

Here are two recent examples for GDAL:
[2023-1] Scientific Data: A 1.2 Billion Pixel Human-Labeled Dataset for Data-Driven Classification of Coastal Environments (https://doi.org/10.1038/s41597-023-01929-2) -> Reference #40
[2023-3] Environmental Research Communications: Validation of FABDEM, a global bare-earth elevation model, against UAV-lidar derived elevation in a complex forested mountain catchment (https://doi.org/10.1088/2515-7620/acc56d)

The benefits of DOI based citation are twofold: As stated, the software projects receive proper credit, but in addition we will better understand from the publication records where and for what GRASS GIS is put to use.

The code snippets for the GRASS GIS DOI are provided by the GRASS GIS landing page on Zenodo in HTML, markdown and other formats (right-click on the black/blue DOI icon on the right side of the page):

https://doi.org/10.5281/zenodo.7764250">https://zenodo.org/badge/DOI/10.5281/zenodo.7764250.svg" alt="DOI">
[![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.7764250.svg)](https://doi.org/10.5281/zenodo.7764250)

Best,
Peter


<peter.lo...@gmx.de>

___
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] Proposal: Display GRASS DOI icon on project webpage

2023-04-08 Thread Peter Löwe
Hello PSC,

I would like to propose to include the DOI icon 
(https://zenodo.org/badge/DOI/10.5281/zenodo.7764250.svg) for GRASS GIS on a 
prominent spot on the GRASS GIS project page (https://grass.osgeo.org/). This 
is should require little effort but will result in benefitial consequences and 
visibility for the project community and GRASS GIS applications across all 
fields of Science.

It's been over a year that a DOI was registered for GRASS GIS. Other projects, 
such as PROJ and GDAL have also registered DOI. While this is great in itself, 
preserving OSGeo projects as part of the scientific record, enabling scientific 
citation, etc.,  this has not yet been announced to the greater public.

In the meantime other projects such as PROJ, GDAL and Mapserver have already 
included their DOI icons in their web pages (e.g. https://gdal.org/).

It seems that this alone already suffices to motivate and enable scientists to 
give due credit to the sofware projects and the project communities by 
DOI-based citation, including hi-visibility journals such as Nature.

Here are two recent examples for GDAL:
[2023-1] Scientific Data: A 1.2 Billion Pixel Human-Labeled Dataset for 
Data-Driven Classification of Coastal Environments 
(https://doi.org/10.1038/s41597-023-01929-2) -> Reference #40
[2023-3] Environmental Research Communications: Validation of FABDEM, a global 
bare-earth elevation model, against UAV-lidar derived elevation in a complex 
forested mountain catchment (https://doi.org/10.1088/2515-7620/acc56d)

The benefits of DOI based citation are twofold: As stated, the software 
projects receive proper credit, but in addition we will better understand from 
the publication records where and for what GRASS GIS is put to use.

The code snippets for the GRASS GIS DOI are provided by the GRASS GIS landing 
page on Zenodo in HTML, markdown and other formats (right-click on the 
black/blue DOI icon on the right side of the page):

https://doi.org/10.5281/zenodo.7764250;>https://zenodo.org/badge/DOI/10.5281/zenodo.7764250.svg; alt="DOI">
[![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.7764250.svg)](https://doi.org/10.5281/zenodo.7764250)

Best,
Peter




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


[GRASS-PSC] Proposal: Let's have a GRASS GIS group in Zenodo

2023-03-27 Thread Peter Löwe
Hi PSC,

another proposal: Can we have a Zendo group for all things GRASS GIS ? AFAIK, 
Zenodo groups are similar to thematic tags. Joining a group must be ok'd by the 
group owner (-> we should discuss Zenodo roles at some point).

FWIW, I'll propose the same to the OSGeo board regarding a OSGeo goup in Zenodo.

Best,
Peter



___
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

2023-03-27 Thread Peter Löwe
Hi Markus, Vaclav, all,

who were the original authors of the Spearfish dataset in 1993 (3 decades ago!) 
?

Best,
Peter




> Gesendet: Montag, 27. März 2023 um 09:15 Uhr
> Von: "Markus Neteler" 
> An: "Peter Löwe" 
> Cc: "GRASS-PSC" 
> Betreff: Re: [GRASS-PSC] DOI for GRASS reference data sets
>
> Hi Peter,
> 
> On Mon, Mar 27, 2023 at 3:41 AM Vaclav Petras  wrote:
> > On Sun, 26 Mar 2023 at 10:22, Peter Löwe  wrote:
> >>
> >> Hello PSC,
> >>
> >> I would like to suggest to register persistent DOI for GRASS GIS related 
> >> reference data sets such as Spearfish and North Carolina by preserving 
> >> them in the Open Access repository Zenodo (www.zenodo.org).
> >
> >
> > Good idea. I already considered it and I think it is quite appropriate. 
> > Please, go ahead.
> 
> Happy to assist here (we can do preparations off-list):
> 
> - Spearfish:
>   https://grass.osgeo.org/download/data/#SpearFishDataset
>   --> Original documentation from 1993:
> https://grass.osgeo.org/sampledata/spearDB.pdf
> 
> - North Carolina: see e.g.
>   https://grassbook.org/datasets/datasets-1st-edition/
>   https://grassbook.org/datasets/datasets-2nd-edition/
>   https://grassbook.org/datasets/datasets-3rd-edition/
>   There are different versions available starting from 2002 (GRASS GIS
> 5, 6, 7) which IMHO should all be tracked.
> 
> Best,
> Markus
>
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc


[GRASS-PSC] DOI for GRASS reference data sets

2023-03-26 Thread Peter Löwe
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).

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


Re: [GRASS-PSC] GRASS DOI

2022-06-22 Thread Peter Löwe
Hi Vero, PSC, all,

 

this discussion might get us to the current edge of software citation best practices: this topic is not (yet) mentionend in the FAIR Principles for Research Software (https://rd-alliance.org/group/fair-research-software-fair4rs-wg/outcomes/fair-principles-research-software-fair4rs)

 

IMHO, updating the contributor list for every release compares to a new volume of a Journal Publication (as an analogy for the GRASS project with its Concept DOI).

 

I propose to reach out to the RDA / FORCE 11 communities on this, which should be quick & easy.

 

Best,

Peter


 



 
 

Gesendet: Dienstag, 21. Juni 2022 um 11:35 Uhr
Von: "Veronica Andreo" 
An: "Markus Neteler" 
Cc: "GRASS-PSC" 
Betreff: Re: [GRASS-PSC] GRASS DOI



Hi Markus, all
 


El mar, 7 jun 2022 a las 11:42, Markus Neteler () escribió:

Hi PSC,

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

Still valid :-)

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

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

 

I personally like this idea as it seems fair to those contributing more in each release.

 

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] GRASS DOI

2022-01-13 Thread Peter Löwe
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 :-) ).

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

 

.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



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


Re: [GRASS-PSC] grass-psc Digest, Vol 144, Issue 5

2021-09-01 Thread Peter Löwe
Pease add also best wishes from my side for Markus and his family.

 

Best,

Peter
 



 
 

Gesendet: Dienstag, 31. August 2021 um 11:22 Uhr
Von: "Paulo van Breugel" 
An: grass-psc@lists.osgeo.org
Betreff: Re: [GRASS-PSC] grass-psc Digest, Vol 144, Issue 5




Please include my best wishes and strength to Markus and the family.
 

Paulo

 


On Mon, Aug 30, 2021 at 6:55 PM  wrote:

Send grass-psc mailing list submissions to
        grass-psc@lists.osgeo.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.osgeo.org/mailman/listinfo/grass-psc
or, via email, send a message with subject or body 'help' to
        grass-psc-requ...@lists.osgeo.org

You can reach the person managing the list at
        grass-psc-ow...@lists.osgeo.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of grass-psc digest..."


Today's Topics:

   1.  Fwd: Card or Flowers for Markus? (Helena Mitasova)
   2. Re:  Fwd: Card or Flowers for Markus? (Luca Delucchi)
   3. Re:  Fwd: Card or Flowers for Markus? (Veronica Andreo)
   4. Re:  Card or Flowers for Markus? (Michael Barton)


--

Message: 1
Date: Mon, 30 Aug 2021 10:36:35 -0400
From: Helena Mitasova 
To: Veronica Andreo 
Cc: GRASS-PSC 
Subject: [GRASS-PSC] Fwd: Card or Flowers for Markus?
Message-ID: <08dcd01b-f824-4481-8f32-9c43fc538...@ncsu.edu>
Content-Type: text/plain; charset="utf-8"

Vero,

I received a question below from our colleague who knows Markus quite well.
I assume that sending individual cards won?t work well but perhaps we can set up a virtual card that people
from the community can sign? I am not sure what is available but maybe there is a good way how to do this?

Thank you, Helena

> Begin forwarded message:
>
> From: Doug Newcomb 
> Subject: Card or Flowers for Markus?
> Date: August 30, 2021 at 8:51:18 AM EDT
> To: Helena Mitasova 
>
> Helena,
> Is there any way we can send Markus a card or flowers?
>
> Doug

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



-- next part --
An HTML attachment was scrubbed...
URL: 

--

Message: 2
Date: Mon, 30 Aug 2021 16:56:44 +0200
From: Luca Delucchi 
To: Helena Mitasova 
Cc: Veronica Andreo , GRASS-PSC
        
Subject: Re: [GRASS-PSC] Fwd: Card or Flowers for Markus?
Message-ID:
        
Content-Type: text/plain; charset="UTF-8"

On Mon, 30 Aug 2021 at 16:36, Helena Mitasova  wrote:
>
> Vero,
>

Hi all,

> I received a question below from our colleague who knows Markus quite well.
> I assume that sending individual cards won?t work well but perhaps we can set up a virtual card that people
> from the community can sign? I am not sure what is available but maybe there is a good way how to do this?
>

I'm in touch with Markus's wife if you want we can send her something
to bring to Markus

> Thank you, Helena
>

--
ciao
Luca

www.lucadelu.org


--

Message: 3
Date: Mon, 30 Aug 2021 17:04:12 +0200
From: Veronica Andreo 
To: Luca Delucchi 
Cc: Helena Mitasova , GRASS-PSC
        
Subject: Re: [GRASS-PSC] Fwd: Card or Flowers for Markus?
Message-ID:
        
Content-Type: text/plain; charset="utf-8"

Yes, that might work, Luca. Thanks! We could use a virtual card too.

In any case, we could start collecting our messages here or in a new
thread, so we send them altogether.
What do you think?

Vero

El lun, 30 ago 2021 a las 16:56, Luca Delucchi ()
escribi?:

> On Mon, 30 Aug 2021 at 16:36, Helena Mitasova  wrote:
> >
> > Vero,
> >
>
> Hi all,
>
> > I received a question below from our colleague who knows Markus quite
> well.
> > I assume that sending individual cards won?t work well but perhaps we
> can set up a virtual card that people
> > from the community can sign? I am not sure what is available but maybe
> there is a good way how to do this?
> >
>
> I'm in touch with Markus's wife if you want we can send her something
> to bring to Markus
>
> > Thank you, Helena
> >
>
> --
> ciao
> Luca
>
> www.lucadelu.org
>
-- next part --
An HTML attachment was scrubbed...
URL: 

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

2021-01-17 Thread Peter Löwe


 
 PSC,I support the current budget proposal.Thanks to Everybody who helped to set it up.Best,Peter   -- Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 17.01.21, 14:15 schrieb Markus Neteler :

  PSC,
  
   First of all, thanks to Moritz for his support with cleaning up the budget.
  
   I have slightly expanded the description herein:
   https://wiki.osgeo.org/wiki/GRASS_GIS_Budget_2021
  
   Please check - by today I have to send this request as an email to the
   OSGeo board list.
  
   thanks
   Markus
   ___
   grass-psc mailing list
   grass-psc@lists.osgeo.org
   https://lists.osgeo.org/mailman/listinfo/grass-psc
  
 

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


[GRASS-PSC] Statement Peter Loewe

2021-01-15 Thread Peter Löwe

Hello GRASS community,

 

a big thanks to everybody who nominated me as a candidate for the next PSC term !

 

Over twenty years ago (1998) I discovered GRASS (4.2.1) to wrangle with weather radar data for a PhD project in South Africa. The PhD project led to one of first GRASS-centered LiveLinux CDs, to make scientific results, software, and data open, accessible and reusable [1]. In 2000 I joined the newly founded german GRASS Anwender Verein (now FOSSGIS), serving as Deputy Chair 2008 – 2009.

 

I have used GRASS professionally for the development of Tsunami early warning systems, satellite based remote sensing workflows, and cluster-based high performance computing. Currently I am responsible for the scientific infrastructure of the German Institute for Economic Research (DIW Berlin), where GRASS is used on a daily basis to process data from longitudinal surveys. DIW Berlin was also proud to host GRASS codesprint 2019.

 

GRASS has enabled me to explore new GIS use cases and to develop add-ons for GRASS 5.x/6.x, inluding expert system integration, 3d printing, and GRASS software citation, the latter with the support of Vaclav Petras.

 

Since 2007 I’ve been supporting OSGeo as an elected Charter member, becoming co-Chair of the Open Geoscience Committee (together with Maxi Cannata) in 2016, when the GRASS community also elected me to serve in the previous GRASS PSC term.

 

I advocate GRASS and OSGeo in the Earth and Space Informatics (ESSI) chapters of both the European Geoscience Union (EGU) and the American Geophysical Union (AGU), by organising annual Townhall events and have helped to negotiate a Memorandum of Understanding between OSGeo and AGU in 2017.

 

When working at the German National Library's of Science and Technology (TIB), I established the still continuing collection of OSGeo releated scientific videos and conference recordings in the TIB online collection for scientific video, beginning with the GRASS 1987 promotional video, narrated by William Shatner (-> Star Trek Original Series) [2][3].  Since then, every year over 100 hours of OSGeo-related video from FOSS4G conferences are now being preserved by TIB for education and research. This includes the beautiful renderings of the evolution of the GRASS codebase by Markus Neteler [4].


If I should be elected for the new PSC, I will push for these topics:

 

- Education and reach out to early career scientists to get new generations of users and developers on board, especially in developing nations.

 

- Professional recognition for GRASS related work by scientific citation and reference, both for new code but also maintenance of the codebase and generation of data.  

 

- Fostering exchange with organisations advancing the state-of-art of good scientific practice, like the FAIR prinicples (Findable, Accessible, Interoperable, Reusable) and Open Science. The GRASS community is a role model for this. They can learn from us and we can learn from them.

 

- Long term software curation and discovery: Now that the GRASS repo is git-based, we can tie into global repository infrastructures (Zenodo, re3data) for long term archiving and code preservation.

 

- Improving the discoverability and fostering reuse of the growing GRASS-/OSGeo-related video "library".

 

- A „historical“-section in the GRASS web presence to provide information about GRASS-related real-world memorabilia and artifacts of the last 37 years, including the GRASS manual signed by William Shatner, historic tape reels, T-Shirt designs from the 1980s, etc. 

 

Best,

Peter

 

[1] https://doi.org/10.5281/zenodo.1164724

[2] https://doi.org/10.5446/12963

[3] https://doi.org/10.5281/zenodo.1420936

[4] https://doi.org/10.5446/14652

 




 

 


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


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

2020-12-23 Thread Peter Löwe
Hernán,

 

thanks for being our CRO !

 

Happy holidays & stay healthy,

Peter

 



 
 

Gesendet: Mittwoch, 23. Dezember 2020 um 09:31 Uhr
Von: "Chief Return Officer (CRO) - GRASS GIS election 2020" 
An: grass-psc@lists.osgeo.org
Betreff: Re: [GRASS-PSC] [GRASS GIS Elections 2020] Current members of the PSC willing to stand up for reelection?


Thank you Margherita and Peter.

I can now count 7 votes in favor of the proposal (Markus, Moritz, Anna, Helena, Margherita, Peter and Michael) from a total of 9 possible.

I will then write this in the wiki and after that inform everyone on the lists:

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

Have a nice Christmas Holidays everyone.

Hernán (CRO)

On 2020-12-23 09:25, Peter Löwe wrote:



+1 for proposal #2: "GRASS GIS PSC members are to be nominated for re-election in the same
way by the community as possible new candidates"

 

Best,

Peter

 



 
 

Gesendet: Mittwoch, 23. Dezember 2020 um 08:19 Uhr
Von: "Chief Return Officer (CRO) - GRASS GIS election 2020" 
An: "GRASS-PSC" 
Betreff: Re: [GRASS-PSC] [GRASS GIS Elections 2020] Current members of the PSC willing to stand up for reelection?


On 2020-12-22 17:43, Michael Barton wrote:

I have no issue with either proposal. I did not respond because I never saw a notification, even though I was looking for it.
 

 


If I counted correctly, it seems then that at this point we will need one more PSC vote to approve proposal #2.

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

Anyone?

 

Hernán (CRO)

 

 

 





On Dec 22, 2020, at 6:48 AM, Markus Neteler <nete...@osgeo.org> wrote:
 


On Tue, Dec 22, 2020 at 12:34 PM Chief Return Officer (CRO) - GRASS
GIS election 2020 <variablestarli...@gmail.com> wrote:

On 2020-12-22 12:08, Markus Neteler wrote:
On Tue, Dec 22, 2020 at 10:28 AM Moritz Lennert

...



But I agree with Hernán that we should have discussed this earlier.
Still it is not too late, say, "nothing lost".

Marcus, what do you say on this?

What I tried to say is that we might quickly modify our procedure to
Helli's suggestion as no PSC member had answered yet (hence, no
conflict arises so far).
 
What do other PSC members say? Shall
the PSC make a consensus on these proposals? In that case it would be
nice to have the matter resolved rather sooner than later.

Definitely.

@PSC: do you agree to change our procedure to

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

?

Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!LXnc6cuCYMYT1IyIMAPQJ9fyf7msoxybE0_ekbTQIbJHMx8vCcfIl-5hyOavwxwa7AcwZNw$





___ 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] [GRASS GIS Elections 2020] Current members of the PSC willing to stand up for reelection?

2020-12-23 Thread Peter Löwe
+1 for proposal #2: "GRASS GIS PSC members are to be nominated for re-election in the same
way by the community as possible new candidates"

 

Best,

Peter

 



 
 

Gesendet: Mittwoch, 23. Dezember 2020 um 08:19 Uhr
Von: "Chief Return Officer (CRO) - GRASS GIS election 2020" 
An: "GRASS-PSC" 
Betreff: Re: [GRASS-PSC] [GRASS GIS Elections 2020] Current members of the PSC willing to stand up for reelection?


On 2020-12-22 17:43, Michael Barton wrote:

I have no issue with either proposal. I did not respond because I never saw a notification, even though I was looking for it.
 

 


If I counted correctly, it seems then that at this point we will need one more PSC vote to approve proposal #2.

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

Anyone?

 

Hernán (CRO)

 

 

 





On Dec 22, 2020, at 6:48 AM, Markus Neteler  wrote:
 


On Tue, Dec 22, 2020 at 12:34 PM Chief Return Officer (CRO) - GRASS
GIS election 2020  wrote:

On 2020-12-22 12:08, Markus Neteler wrote:
On Tue, Dec 22, 2020 at 10:28 AM Moritz Lennert

...



But I agree with Hernán that we should have discussed this earlier.
Still it is not too late, say, "nothing lost".

Marcus, what do you say on this?

What I tried to say is that we might quickly modify our procedure to
Helli's suggestion as no PSC member had answered yet (hence, no
conflict arises so far).
 
What do other PSC members say? Shall
the PSC make a consensus on these proposals? In that case it would be
nice to have the matter resolved rather sooner than later.

Definitely.

@PSC: do you agree to change our procedure to

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

?

Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!LXnc6cuCYMYT1IyIMAPQJ9fyf7msoxybE0_ekbTQIbJHMx8vCcfIl-5hyOavwxwa7AcwZNw$





___ 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] Proposing Nicklas Larsson as a new core developer

2020-12-16 Thread Peter Löwe
+1 !

Best,
Peter




> Gesendet: Mittwoch, 16. Dezember 2020 um 15:19 Uhr
> Von: "Markus Neteler" 
> An: "GRASS-PSC" 
> Cc: "Nicklas Larsson" 
> Betreff: [GRASS-PSC] Proposing Nicklas Larsson as a new core developer
>
> Dear PSC,
>
> Let me propose Nicklas Larsson (https://github.com/nilason) to be
> accepted as a new core developer.
>
> Nicklas has impressively contributed to various parts of the source code:
>
> - in "core": as of today 40 accepted/approved pull requests in the
> main repo [1],
> - in "addons": as of today 1 accepted pull requests in addons [2],
> - and he offers support, especially for the packaging on Mac.
>
> I have asked him off-list and he would be happy to join the core team
> with write access to the main repository.
>
> According to RFC1 [1] all PSC members need to vote on this proposal.
>
> Best,
> Markus
>
>
> [1] 
> https://github.com/OSGeo/grass/pulls?q=is%3Apr+is%3Aclosed+author%3Anilason
> [2] 
> https://github.com/OSGeo/grass-addons/pulls?q=is%3Apr+is%3Aclosed+author%3Anilason
> [3] https://trac.osgeo.org/grass/wiki/RFC/1_ProjectSteeringCommitteeGuidelines
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
>
___
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

2020-11-21 Thread Peter Löwe


 
 +1Peter-- Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 20.11.20, 23:17 schrieb Markus Neteler :

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

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


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

2020-09-28 Thread Peter Löwe
+1,
Peter




> Gesendet: Sonntag, 27. September 2020 um 21:03 Uhr
> Von: "Markus Neteler" 
> An: "GRASS-PSC" 
> Cc: "Nicolas Bozon" 
> Betreff: [GRASS-PSC] [Motion] Second payment for new GRASS GIS Hugo based web 
> site
>
> Dear PSC,
>
> The new, shiny GRASS GIS website is up and running for some time at
> https://grass.osgeo.org/ with its code base available at
> https://github.com/OSGeo/grass-website .
>
> In the last weeks, the main developer, Nicolas Bozon
> (https://github.com/nbozon) has done further developments, esp. fixes.
>
> This motion is to vote on the second (and last) payment of 2000 USD
> (out of the budgeted 6000 USD [1]) to Nicolas Bozon.
> The money transfer can then be directly done from OSGeo to the
> developer (already clarified with the OSGeo treasurer).
>
> Motion:
> I hereby start with a +1.
>
> Best,
> Markus
>
> [1] https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2020
> ___
> 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] GitHub sponsors

2020-05-26 Thread Peter Löwe
+1

Peter

> Gesendet: Montag, 25. Mai 2020 um 15:18 Uhr
> Von: "Luca Delucchi" 
> An: "Moritz Lennert" 
> Cc: "GRASS-PSC" 
> Betreff: Re: [GRASS-PSC] Fwd: [Board] GitHub sponsors
>
> On Mon, 25 May 2020 at 15:10, Moritz Lennert
>  wrote:
> >
> >
> > So, that means that only people on github can sponsor ? And that
> > sponsorship necessarily means a "recurring monthly payment" ? If any of
> > those two are true, then I think this would be a possible complement to,
> > not a replacement of our current PayPal money pool.
> >
>
> +1
>
> > Moritz
> >
>
>
> --
> ciao
> Luca
>
> www.lucadelu.org
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

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

2020-04-22 Thread Peter Löwe
Helmut, all,

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

If that has been the case (and there was no feedback) I'd propose to 
discontinue winGRASS 32bit by July 31 2020, as was announced (documentation 
about the build process should be preserved, for the case that winGRASS 32bit 
builds might be needed in the future).

Otherwise I'd advise another announcement in the OSGeo-announce list 
(mentioning the July 31 deadline).

Cheers from Potsdam,
Peter




> Gesendet: Dienstag, 21. April 2020 um 21:30 Uhr
> Von: "Helmut Kudrnovsky" 
> An: grass-psc@lists.osgeo.org
> Betreff: Re: [GRASS-PSC] proposal: winGRASS 32bit versions - phasing out in 
> 2020
>
> Helmut Kudrnovsky wrote
> > dear GRASS PSC,
> >
> > a few days ago, I've asked in the GRASS user ML following question [1]:
> >
> > *winGRASS - still a need for 32bit versions?*
> >
> > reasoning:
> >
> > - 64bit computer architecture and 64bit windows operating systems are very
> > common
> > - 32bit computer architecture and 32bit windows operating systems will
> > find
> > their EOL
> >
> > and the important reasons:
> >
> > - reduce the high maintenance burden to keep 2 build environments of
> > winGRASS (32bit, 64bit) alive
> > - facilitate to find possible (automatic) alternatives of winGRASS build
> > environments beside the actual MSYS2/OSGeo4W workflow
> >
> > so far, no feedback by the community that there is still a need for a
> > winGRASS 32bit version.
> >
> > thus I propose:
> >
> > * phasing out of winGRASS 32bit versions in 2020
> > * communicate early and communicate often ;-) about this phasing out
> >
> > in my original post, I've suggested  'middle next year (2020 July 31)'
> >
> > it can be discussed if it should happen at middle next year (2020 July 31)
> > or end of year 2020; though IMHO it should happen... ;-)
> >
> > any feedback? any suggestions?
> >
> > [1]
> > http://osgeo-org.1560.x6.nabble.com/winGRASS-still-a-need-for-32bit-versions-td5424586.html
> >
> >
> >
> > -
> > best regards
> > Helmut
> > --
> > Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
> > ___
> > grass-psc mailing list
>
> > grass-psc@.osgeo
>
> > https://lists.osgeo.org/mailman/listinfo/grass-psc
>
> Coming back to this? Any opinions? Any suggestions?
>
> Citing here https://trac.osgeo.org/osgeo4w/ticket/627#comment:3
>
> 
>
> The current idea is to switch to 5.14 and use the occasion to upgrade
> compilers and drop 32bit (according to the latest qgis survey only 7% of the
> participants still use it).
> 
>
> I still think we should phase out wingrass 32bit  in 2020 ;-)   and
> should announce it earlier than later.
>
>
>
>
> -
> best regards
> Helmut
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-PSC-f4051248.html
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
___
grass-psc 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

2020-02-18 Thread Peter Löwe
+1

Peter
 



 
 

Gesendet: Dienstag, 18. Februar 2020 um 09:19 Uhr
Von: "Margherita Di Leo" 
An: "Markus Neteler" 
Cc: GRASS-PSC 
Betreff: Re: [GRASS-PSC] [Motion] First payment for new GRASS GIS Hugo based web site


+1
 

Kind regards,

 

madi

 


On Mon, Feb 17, 2020 at 1:58 PM 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

 

 
--









Margherita Di Leo








___ 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

2020-02-16 Thread Peter Löwe
+1 for printing more stickers.

 

Cheers,

Peter
 



 
 

Gesendet: Samstag, 15. Februar 2020 um 17:00 Uhr
Von: "Veronica Andreo" 
An: "Vaclav Petras" 
Cc: GRASS-PSC 
Betreff: Re: [GRASS-PSC] GRASS GIS stickers reloaded




Hola :)



El dom., 2 feb. 2020 a las 22:11, Vaclav Petras () escribió:





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?








 

+1 for printing more stickers (i.e., a total of 1000 or so), maybe in different orders so to send them to different locations. In that way, all of us get some and can then take to local events.

 

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

Re: [GRASS-PSC] [MOTION] Prague 2019 Community Sprint Reimbursements

2020-01-07 Thread Peter Löwe

+1

 

Happy new year, y'all !

Cheers,

Peter

 



 
 

Gesendet: Dienstag, 07. Januar 2020 um 14:28 Uhr
Von: "Margherita Di Leo" 
An: "Martin Landa" 
Cc: "GRASS PSC list" 
Betreff: Re: [GRASS-PSC] [MOTION] Prague 2019 Community Sprint Reimbursements



 
 


On Tue, Jan 7, 2020 at 2:22 PM 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 .

 

+1.

 

Happy new year everybody!

Cheers,

 

Madi 


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

 

 
--









Margherita Di Leo









___ 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] GRASS GIS budget 2020 - was: Re: [Board] OSGeo Budget 2020

2019-12-27 Thread Peter Löwe
Hello Markus, hi PSC,

 

regarding our surplus from 2019, does the item "Travel grants for community sprints: 1043.09 EUR" summarize all costs for both events in Berlin and the Prague (including food, drinks, etc.) ? If the numbers for 2019 are complete, it seems like we only spent 20% of the requested budget.

 

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

 

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 


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] stickers for FOSS4G in Bucharest

2019-06-26 Thread Peter Löwe
+1 provided that budget is available.

 

Peter

 


 



 
 

Gesendet: Dienstag, 25. Juni 2019 um 21:20 Uhr
Von: "Helena Mitasova" 
An: "Moritz Lennert" 
Cc: grass-psc@lists.osgeo.org
Betreff: Re: [GRASS-PSC] stickers for FOSS4G in Bucharest


+1 assuming we have it in the budget, 
 

Helena
 

 


On Jun 25, 2019, at 2:16 PM, Moritz Lennert  wrote:
 


+1

Moritz
 
Am 25. Juni 2019 20:12:19 MESZ schrieb Veronica Andreo :



Dear PSC

 

I was thinking that we should definitely print some stickers to bring to the OSGeo booth at FOSS4G in Bucharest, as we have done in the past. I think stickers give us some visibility, everyone likes them and no folding is needed as compared to flyers :p

 

I ordered from Stickermule last time and the quality was much better than that of sticker-app. I thought of ordering 500 die cut stickers (same as last year) with GRASS logo (https://www.stickermule.com/products/die-cut-stickers). Choosing the smallest dimension (also as last year), it's something like ~150 dollars. However, since our logo is not exactly 2x2 inches, price is a bit less IIRC.

 

If PSC agrees, I can assist with the ordering process, but cannot really pay with my credit card this time. So, it would be great if we can pay directly from GRASS bank account.

 

What do you say?

 

Best,

Vero




___
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] git migration / going Zenodo

2019-04-23 Thread Peter Löwe
Hi Markus, PSC,

 

apologies for following up on this so late.

The grass-legacy structure in GitHub is fine, of course.

Regarding the options how to integrate with Zenodo, I believe we're on the right track. There is an alternative option by manual/Zebodo-API-based integration, but I don't believe this makes sense. All feedback from the Zenodo helpdesk on this has been included in the "future plans" section of the wiki page: https://trac.osgeo.org/grass/wiki/GitMigration

 

best,

Peter

 

 



 
 

Gesendet: Mittwoch, 17. April 2019 um 16:29 Uhr
Von: "Markus Neteler" 
An: "\"Peter Löwe\" (peter.lo...@gmx.de)" 
Cc: GRASS-PSC 
Betreff: Re: git migration: Zenodo and versioned DOI for GRASS releases



Hi Peter,
 
 


"Peter Löwe" <peter.lo...@gmx.de> schrieb am Mi., 17. Apr. 2019, 12:15:

Hi Markus, hi PSC,

the reason why I believe we should consider the Zenodo option (for long term archiving and DOI-based scientific recognition/citation) before making the switch to GitHub is the DOI versioning capability of Zenodo (https://blog.zenodo.org/2017/05/30/doi-versioning-launched/). This is similar to the mechanism implented for the GRASS module manual pages, where references from outdated versions point to the current release of the module (and man page). The DOI-versioning mechanism in Zenodo additionally implements a version history as a hsitorical sequence of releases. This means that the DOI version for GRASS 4.2.1 predates GRASS 4.3, which predates GRASS5.x, etc. etc. and all also point to the latest release.



 

 

Yes: each release is a point in time.

 



The GRASS SVN contains the release branches dating back to GRASS 5. In addition there are tarballs from the GRASS 4.x era (-> what about GRASS 3.x or earlier ?).



 

Please check our work already done:

I have reconstructed the releases back to 3.2 including time stamps at file level.

 

 

https://github.com/grass-svn2git/grass-legacy

 

Note that the URL will change to OSGeo organization soon.

 

 



Making all these releases available for scientific citation (and recognition) through one versioned DOI in the described "timely sequence" is a more complex task than what's covered in the how-to guides for GitHub-Zenodo-integration (https://genr.eu/wp/cite/).



 

We have all branches there, since 1987.

 

 



I've contacted the Zenodo helpdesk for advice how this should be approached and will report back ASAP.

It would be a pity (and waste of ressources) if we make the effort to create a GitHub repo for GRASS once and then having to redo it because of some pecularities of the DOI-versioning mechanism.



 

 

Still I don't see why we should redo it.

Does the new structure not address it?

Did you check it?

 

Best,

Markus





___
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

2019-04-18 Thread Peter Löwe
+ 1
Peter
-- 
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 18.04.19, 22:22, Markus Neteler  schrieb:
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.

best regards,
Markus

[1] https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
___
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] git migration

2019-04-09 Thread Peter Löwe
Hi Markus, all,

> Gesendet: Sonntag, 07. April 2019 um 22:02 Uhr
> Von: "Markus Neteler" 
> An: "GRASS PSC list" 
> Betreff: Re: [GRASS-PSC] git migration
>
> Hi PSC,
>
> a months has passed since the publication of the draft
>
> RFC 6: Migration from SVN to GitHub
> https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
>
> Since then comments have been received and integrated into the document.
>
> Let me suggest to come to a vote in the next days in order to move on
> with the SVN to git migration.
>

+ 1 (we should not forget about the Zenodo option)

> I would also suggest to postpone
> - label details in the issue tracker (can be done later)
> - trac wiki migration (can be done later)
> to a date after the git migration has been done, otherwise we remain stuck.

+ 1
> In a nutshell: RFC6 proposes to migrate to github under OSGeo
> organization. It also proposes an exit strategy incl. to implement a
> continuous mirror on GitLab.com.

+1

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

[GRASS-PSC] git migration: Zenodo optionS

2019-04-02 Thread Peter Löwe
Hi Markus, hi list,

I was raising the Zenodo-topic, since this might strategically affect how we 
need to structure the GRASS repository / repositories on GitHub, so we can make 
the most out of Zenodo for scientific citation later.

Zenodo currenlty mints for EACH SINGLE GitHub-project which is checked in 
EXACTLY ONE persistent identifier ("unbreakable Web-link"), a Digital Object 
Identifier (DOI). DOI have become crucial for scientific citation and 
indirectly also for the careers of early career scientists (who need lots a 
citations to eventually get tenure/rich)

Whenever there's a new release of the project repo on GitHub, the corresponding 
repo- instance in Zenodo is updated accordingly and the DOI is also updated to 
a new version (note: it's the same DOI, NOT a new/different DOI). This compares 
to the update note on GRASS man pages ("Note: A new GRASS GIS stable version 
has been released: GRASS GIS 7.6, available here. Updated manual page: here").

In this manner we're dealing with two different flavours of DOI-based 
reference: 1.) The "overall" DOI for the archived (GRASS-)software repo and 2.) 
the continuously increased version/release numbers (e.g. citing "GRASS GIS" 
versus a particular release "GRASS 4.2.1"; "GRASS 5.3", "GRASS 7.4", etc.). 

So from the Zenodo/DOI perspective need to consider (at least) two options for 
using GitHub:

a) We could _SPLIT_ the overall GRASS repo and create individual GitHub repos 
for each currently existing GRASS release, so each gets its own distinct DOI 
(this would allow for backports to be considered new (DOI)versions of the 
particular GRASS releases).

b) We keep __ONE__ GRASS project GUI, and get __ONE__ DOI for the greater GRASS 
project wich has LOTS of versions. Suggestion: We could start filling the repo 
(already linked with Zenodo) consecutively, beginning with the oldest archived 
GRASS releases, minting a DOI-version for each one. In this manner, each old 
GRASS release will receive it's own  distinct __version__ of the overall DOI. 
Things could get messy lateron, when backports to previous releases are made, 
which will also cause DOI version updates, but AFAIK there's no way yet to sort 
through all DOI versions (just) for a specific GRASS release.

We also should consider that Zenodo currently can't handle fine-grained DOI, to 
cite a particular GRASS module within a certain GRASS release. There's still a 
lot of development going on both in the DOI infrastructure and Zenodo, so this 
might come as a later step.

Another interesting aspect is the issue of ownership and due credit: Both the 
GRASS repo(s) on GitHub and the corresponding Zendo-archive(s) must have 
owners. This should be IMHO the "GRASS Development Team". Therefore the 
GRASS-related DOI(s) will be attributed to the GRASS Developer Team. We should 
think about a way, to link the ORCIDs of team members ("persitent identifiers 
for individual persons" https://orcid.org) to the GRASS DOI(s). This is not 
trivial (but innovative), but can be tackled later.  

best,
Peter




> Gesendet: Montag, 01. April 2019 um 11:13 Uhr
> Von: "Markus Neteler" 
> An: "Peter Löwe" 
> Cc: GRASS-PSC 
> Betreff: Re: git migration: the Zenodo option
>
> Hi Peter,
> 
> On Mon, Apr 1, 2019 at 9:35 AM "Peter Löwe"  wrote:
> >
> > Hello PSC,
> >
> > before we actually venture into GitHub, I propose we should consider 
> > beforehand how the GRASS repo(s) *could* make use  of the Zenodo archive in 
> > the future, so we can set up things in a way that this option can be used 
> > (setting up of credentials, etc.). Zenodo is a open-access long term 
> > scientific archive (https://en.wikipedia.org/wiki/Zenodo), operated and 
> > maintained by CERN. The Zenodo software itself is also FOSS.
> > Connecting repos on GitHub with Zenodo is easy: 
> > https://guides.github.com/activities/citable-code/
> >
> > IMHO we could use this mechanism to provide scientific citability and long 
> > term preservation for the old stable releases GRASS 4.x, 5.x and 6.x.
> 
> A very good idea.
> Just curious: why is this needed to be done (?) *before* migrating to
> GitHub? I'd rather get that done first, then put cool stuff on top.
> 
> Best
> Markus
>
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

[GRASS-PSC] git migration: the Zenodo option

2019-04-01 Thread Peter Löwe
Hello PSC,

 

before we actually venture into GitHub, I propose we should consider beforehand how the GRASS repo(s) *could* make use  of the Zenodo archive in the future, so we can set up things in a way that this option can be used (setting up of credentials, etc.). Zenodo is a open-access long term scientific archive (https://en.wikipedia.org/wiki/Zenodo), operated and maintained by CERN. The Zenodo software itself is also FOSS.

Connecting repos on GitHub with Zenodo is easy: https://guides.github.com/activities/citable-code/

 

IMHO we could use this mechanism to provide scientific citability and long term preservation for the old stable releases GRASS 4.x, 5.x and 6.x.

 

best,

peter

 

 



 
 

Gesendet: Dienstag, 26. März 2019 um 12:28 Uhr
Von: "Markus Neteler" 
An: GRASS-PSC 
Betreff: Re: [GRASS-PSC] git migration


Hi all,
 

where do we stand here at time?
 


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

[GRASS-PSC] git migration: software citation 101

2019-03-08 Thread Peter Löwe
Hi PSC,

to follow up on the software citation topic, here's a short tutorial which 
describes how guthub and Zenodo can be linked:
https://genr.eu/wp/cite/

IMHO it would make a lot of sense to provide proper scientific citation for 
GRASS releases 4.x - 6.x. Backports to these releasess will still be feasible.

best
peter





> Gesendet: Mittwoch, 06. März 2019 um 17:55 Uhr
> Von: "Peter Löwe" 
> An: "GRASS PSC list" 
> Betreff: [GRASS-PSC] git migration: Opportunity for DOI citation
>
> Dear PSC,
> 
> please be aware that IF we decide to migrate to gitHub, this would provide an 
> opportunity to introduce digital object identifiers (DOI) for scientific 
> citation on the level of individual GRASS releases (and possibly individual 
> add-on modules) if we interface with the Zenodo digital archive (which is a 
> non-propietary science infrastructure service operated be the EU). More info 
> here: https://guides.github.com/activities/citable-code/
> 
> 
> best,
> 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

[GRASS-PSC] git migration: Opportunity for DOI citation

2019-03-06 Thread Peter Löwe
Dear PSC,

please be aware that IF we decide to migrate to gitHub, this would provide an 
opportunity to introduce digital object identifiers (DOI) for scientific 
citation on the level of individual GRASS releases (and possibly individual 
add-on modules) if we interface with the Zenodo digital archive (which is a 
non-propietary science infrastructure service operated be the EU). More info 
here: https://guides.github.com/activities/citable-code/


best,
Peter

___
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

2019-01-20 Thread Peter Löwe
+1 peter
-- 
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 20.01.19, 00:53, Helena Mitasova  schrieb:
+1 Helena
> On Jan 19, 2019, at 6:44 PM, Markus Neteler  wrote:
> 
> Dear PSC,
> 
> please vote (in a timely manner) on granting GRASS-core write access
> to Ondřej Pešek:
> 
> On Sat, Jan 12, 2019 at 8:53 PM Markus Neteler  wrote:
>> On Thu, Jan 10, 2019 at 11:37 AM Ondřej Pešek  wrote:
>>> 
>>> Dear GRASS,
>>> 
>>> I already have the access to GRASS addons repository (mainly because of my master's thesis [1]), but with my Ph.D. supervisor Martin Landa we decided that it might be useful to have the access also to normal trunk. Now, I mostly work on the modeler (parameterization in the Python export [2], which should be followed by still-not-finished PyWPS export [3] - but before this one, we should wait for one GRASS-related fix in PyWPS) and I test some python3 functionalities with my ANN AddOns.
>>> 
>>> I have read and accepted the legal aspects of code contributions (RFC2).
>>> 
>>> My osgeo_id is "pesekon2".
>>> 
>>> Many thanks for considering my request,
>>> 
>>> Kind regards,
>>> 
>>> Ondrej Pesek
>>> 
>>> [1] https://trac.osgeo.org/grass/browser/grass-addons/grass7/imagery/i.ann.maskrcnn
>>> [2] https://trac.osgeo.org/grass/ticket/3669
>>> [3] https://github.com/ctu-yfsg/2017-d-grass-modeler-pywps
>> 
>> Thanks for your request!
>> 
>> According to RFC1 [1] and "HowToContribute" [2] we need to vote for a
>> new core developer [3].
>> I have added this topic to the PSC Agenda [4].
>> 
>> Motion timeline:
>> - proposal published: 12 Jan 2019
>> - voting to be opened on 19 Jan 2019
> 
> I start with a
> +1
> 
> Markus
> 
>> [1] https://trac.osgeo.org/grass/wiki/RFC/1_ProjectSteeringCommitteeGuidelines
>> [2] https://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheMainGRASS-SVNrepository
>> [3] https://trac.osgeo.org/grass/wiki/RFC/3_PSCVotingProcedures
>> [4] https://trac.osgeo.org/grass/wiki/PSC/Agenda
> ___
> grass-psc mailing list
> grass-psc@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc

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

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

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

Re: [GRASS-PSC] Enabling FAIR Data project commitment statement: Feedback, please.

2018-09-24 Thread Peter Löwe
Hello Helena, Moritz, PSC,

here's the feedback from the Enabling FAIR Project:

"“Legal entity” is not required.  Think of it more as the “decision maker” for 
the organization.  The person (or committee)  who will be ensuring and 
enforcing the changes within the organization to meet the elements of the 
criteria."

best,
Peter




> Gesendet: Montag, 24. September 2018 um 16:22 Uhr
> Von: "Helena Mitasova" 
> An: "Peter Löwe" 
> Cc: "Moritz Lennert" , grass-psc@lists.osgeo.org
> Betreff: Re: [GRASS-PSC] Enabling FAIR Data project commitment statement: 
> Feedback, please.
>
> Peter,
> 
> I think that GRASS support for this initiative is covered by the OSGeo 
> foundation as organization which has agreed to sign it. I am not sure we need 
> a separate signature from each project, but that is just my opinion, let us 
> see what Enabling FAIR Project says about it,
> 
> Helena
> 
> 
> > On Sep 24, 2018, at 8:29 AM, Peter Löwe  wrote:
> > 
> > Hi Moritz, PSC,
> > 
> > that's a good point. I will ask the ENabling FAIR Project and will report 
> > back.
> > 
> > best,
> > Peter
> > 
> > 
> > 
> > 
> >> Gesendet: Montag, 24. September 2018 um 14:08 Uhr
> >> Von: "Moritz Lennert" 
> >> An: grass-psc@lists.osgeo.org
> >> Betreff: Re: [GRASS-PSC] Enabling FAIR Data project commitment statement: 
> >> Feedback, please.
> >> 
> >> Hi Peter,
> >> 
> >> On 21/09/18 09:12, "Peter Löwe" wrote:
> >>> Dear PSC members,
> >>> I would like to ask you for feedback regarding the proposal from 
> >>> September 10th, to sign the online commitment statement of the Enabling 
> >>> FAIR Data project on behalf of the GRASS GIS project.
> >>> 
> >>> Is a motion for this needed/appropriate ?
> >> 
> >> I have no specific objections to signing the commitment statement, but I 
> >> am wondering: does the GRASS PSC qualify as an organisation ? We do not 
> >> have any legal status.
> >> 
> >> 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
> 
> 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

Re: [GRASS-PSC] Enabling FAIR Data project commitment statement: Feedback, please.

2018-09-24 Thread Peter Löwe
Hi Moritz, PSC,

that's a good point. I will ask the ENabling FAIR Project and will report back.

best,
Peter




> Gesendet: Montag, 24. September 2018 um 14:08 Uhr
> Von: "Moritz Lennert" 
> An: grass-psc@lists.osgeo.org
> Betreff: Re: [GRASS-PSC] Enabling FAIR Data project commitment statement: 
> Feedback, please.
>
> Hi Peter,
> 
> On 21/09/18 09:12, "Peter Löwe" wrote:
> > Dear PSC members,
> > I would like to ask you for feedback regarding the proposal from September 
> > 10th, to sign the online commitment statement of the Enabling FAIR Data 
> > project on behalf of the GRASS GIS project.
> > 
> > Is a motion for this needed/appropriate ?
> 
> I have no specific objections to signing the commitment statement, but I 
> am wondering: does the GRASS PSC qualify as an organisation ? We do not 
> have any legal status.
> 
> 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] Opportunity: Enabling FAIR Data project commitment statement

2018-09-20 Thread Peter Löwe
Hello Stefan, PSC,

sorry for answering so late.

The trend towards Open Science and FAIR ("requires less openness as Open 
Science, but is much better than closed/inaccessible data") is affecting the 
fields of science in parallel, but at different velocities. Up to my knowledge 
there is yet no world standard for FAIR except for the definition of the FAIR 
principles (https://www.force11.org/group/fairgroup/fairprinciples) by the 
FORCE11 community.

There are various entities who "approve" and "collect" repositories:

The re3data project/portal (Registry of Research Data Repositories 
https://www.re3data.org/), which is synced with DataCite (DOI: "weblinks for 
data-citation which will never expire/outdate") and ORCID ("unique digital IDs 
for researchers"), currently gives an overview over 2000 different 
repositories, which meet their minimal requirements (be run by a legal entity, 
such as a sustainable institution (e.g. library, university) AND clarify access 
conditions  to the data and repository as well as the terms of use AND have 
focus on research data).

Another effort on the national level is the german council for social- and 
economic data, which is a federation of approved repositories in the social 
sciences (https://www.ratswd.de/en ) 

The new GO FAIR initiative (currently involved: Netherlands, France, Germany - 
intends to include as many european nations and neighbouring nations as 
possible) is just emerging They are also applying the FORCE11/FAIR-principles: 
https://www.go-fair.org/fair-principles/).

Does this help ?

best,
Peter




> Gesendet: Mittwoch, 12. September 2018 um 18:10 Uhr
> Von: "Stefan Blumentrath" 
> An: "Peter Löwe" 
> Cc: "GRASS PSC list" 
> Betreff: RE: [GRASS-PSC] Opportunity: Enabling FAIR Data project commitment 
> statement
>
> Hei Peter,
> 
> Good initiative!
> 
> I will also forward this to my institute...
> 
> I am curious about one thing, though. The statement says:
> "These data should, to the greatest extent possible, be shared, open, and 
> stored in community-approved FAIR-aligned repositories. Leading repositories 
> provide additional quality checks around domain data and data services and 
> (...)."
> 
> My question is, what are "community-approved FAIR-aligned repositories"? What 
> does that mean, who approves and is there a list of "approved repos"?
> And finally, how would/could institutional repositories fit into that?
> 
> Anyway, interesting stuff!
> 
> Kind regards,
> Stefan
> 
> -Original Message-
> From: grass-psc  On Behalf Of "Peter Löwe"
> Sent: mandag 10. september 2018 09:09
> Cc: GRASS PSC list 
> Subject: [GRASS-PSC] Opportunity: Enabling FAIR Data project commitment 
> statement
> 
> Hello PSC,
> I would like to propose that the PSC signs the online commitment statement 
> provided by the Enabling FAIR Data project on behalf of the GRASS GIS project.
> 
> Background:
> The Enabling FAIR project is funded by the Arnold Foundation (comparable to 
> the Gates Foundation. Details: 
> https://en.wikipedia.org/wiki/Laura_and_John_Arnold_Foundation) and managed 
> by AGU, the American Geophysical Union (OSGeo has a MOU with AGU. Details: 
> https://www.osgeo.org/foundation-news/osgeo-and-agu-sign-a-memorandum-of-understanding/).
> 
> The project goal is to create an initial critical mass of researchers, 
> research institutes and organisations, publishers, data repositories und 
> funding agencies to establish the FAIR principles (Findable, Accessible, 
> Interoperable, Reusable) as best practices in the (Geo-)Sciences.
> 
> Since last year I have been representing the OSGeo within the project.
> 
> The project has now released an online commitment statement, which IMHO is of 
> interest for the GRASS community.
> The full text (& online signing opportunity) of the commitment statement is 
> available here: 
> http://www.copdess.org/enabling-fair-data-project/commitment-to-enabling-fair-data-in-the-earth-space-and-environmental-sciences/
> 
> The core statement is:
> 
> --snip--
> we commit to these goals:
> Ensuring that Earth, space, and environmental science research outputs, 
> including data, software, and samples or standard information about them, are 
> open, FAIR, and curated in trusted domain repositories whenever possible and 
> that other links and information related to scholarly publications follow 
> leading practices for transparency and information.
> 
> This means that:
> Publication of scholarly articles in the Earth, space, and environmental 
> science community is conditional upon the concurrent availability of the data 
> underpinning the research finding, with only 

[GRASS-PSC] Opportunity: Enabling FAIR Data project commitment statement

2018-09-10 Thread Peter Löwe
Hello PSC,
I would like to propose that the PSC signs the online commitment statement 
provided by the Enabling FAIR Data project on behalf of the GRASS GIS project.

Background:
The Enabling FAIR project is funded by the Arnold Foundation (comparable to the 
Gates Foundation. Details: 
https://en.wikipedia.org/wiki/Laura_and_John_Arnold_Foundation) and managed by 
AGU, the American Geophysical Union (OSGeo has a MOU with AGU. Details: 
https://www.osgeo.org/foundation-news/osgeo-and-agu-sign-a-memorandum-of-understanding/).

The project goal is to create an initial critical mass of researchers, research 
institutes and organisations, publishers, data repositories und funding 
agencies to establish the FAIR principles (Findable, Accessible, Interoperable, 
Reusable) as best practices in the (Geo-)Sciences.

Since last year I have been representing the OSGeo within the project.

The project has now released an online commitment statement, which IMHO is of 
interest for the GRASS community.
The full text (& online signing opportunity) of the commitment statement is 
available here: 
http://www.copdess.org/enabling-fair-data-project/commitment-to-enabling-fair-data-in-the-earth-space-and-environmental-sciences/

The core statement is:

--snip--
we commit to these goals:
Ensuring that Earth, space, and environmental science research outputs, 
including data, software, and samples or standard information about them, are 
open, FAIR, and curated in trusted domain repositories whenever possible and 
that other links and information related to scholarly publications follow 
leading practices for transparency and information.

This means that:
Publication of scholarly articles in the Earth, space, and environmental 
science community is conditional upon the concurrent availability of the data 
underpinning the research finding, with only a few, standard, widely adopted 
exceptions, such as around privacy for human subjects or to protect heritage 
field samples.

These data should, to the greatest extent possible, be shared, open, and stored 
in community-approved FAIR-aligned repositories. Leading repositories provide 
additional quality checks around domain data and data services and facilitate 
discovery and reuse of data and other research outputs.
--snap--

The statement has already been signed by the gvSig project and will be signed 
by the OSGeo board soon.

To my understanding, the goals of the project and GRASS GIS are highly 
compatible and we're actually already on track to establish a open source 
infrastructure for FAIR. Because of this I would like to propose that PSC signs 
the commitment statement on behalf of the GRASS GIS Project.

Overview over all signatories so far: 
http://www.copdess.org/enabling-fair-data-project/commitment-to-enabling-fair-data-in-the-earth-space-and-environmental-sciences/signatories/

Please note that the commitment statement can be signed both by organisations 
and individuals. I would like encourage everybody to sign the statement 
personally. 

Best,
Peter



___
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

2018-06-01 Thread Peter Löwe
Kudos for being lame:

+1 !
Peter




> Gesendet: Donnerstag, 31. Mai 2018 um 22:27 Uhr
> Von: "Markus Neteler" 
> An: "Peter Löwe (peter.lo...@gmx.de)" , "Margherita Di 
> Leo" 
> Cc: "GRASS PSC list" 
> Betreff: Re: [GRASS-PSC] [motion] Bonn Community Sprint funding
>
> Hi Peter, Margherita,
> 
> please vote.
> 
> Markus
> 
> 
> On Fri, May 18, 2018 at 5:11 PM, 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/1BgFMiYlLosFjsVUlUCWwssoxiQB_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
> 
> 
> 
> -- 
> 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] Figures/numbers describing the increase of GRASS modules / Addons over time ?

2018-03-18 Thread Peter Löwe
Dear PSC,

I'm currently working on a poster about GRASS as a project (Research Data 
Alliance conference): Do we already have numbers/figures/tables summarizing the 
total growth of GRASS modules / addons over the years ?


best,
peter
___
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

2018-01-31 Thread Peter Löwe
+1 to invite Stefan Blumentrath as a core developer

Peter




> Gesendet: Dienstag, 30. Januar 2018 um 23:02 Uhr
> Von: "Markus Neteler" 
> An: GRASS-PSC 
> Betreff: [GRASS-PSC] [Motion] Proposing Stefan Blumentrath as a new core 
> developer
>
> 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_ProjectSteeringCommitteeGuidelines
> >
> > --
> > 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

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

2017-10-01 Thread Peter Löwe
Markus, PSC,

good idea. Which people do you have in mind ?

best,
Peter




> Gesendet: Samstag, 30. September 2017 um 21:23 Uhr
> Von: "Markus Neteler" 
> An: GRASS-PSC 
> Betreff: Re: [GRASS-PSC] Let's approve new core developers
>
> PSC,
> 
> On Tue, Jun 13, 2017 at 8:59 AM, Markus Neteler  wrote:
> > PSC,
> >
> > we didn't invite new core developers for a while, I think this should
> > be done asap.
> >
> > Again a somewhat sensitive topic, how shall we proceed? I have some
> > ideas but did not approach those people yet.
> >
> > Open discussion without names :-)
> 
> Time for a new round!
> We have great Addon developers, power users and more.
> 
> Let's get more people directly involved, i.e. grant write access to trunk.
> 
> Opinions?
> 
> thanks,
> 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] [voting] printing of stickers and flyers for FOSS4G Europe

2017-07-24 Thread Peter Löwe
+1

peter
 




Gesendet: Sonntag, 23. Juli 2017 um 11:02 Uhr
Von: "Margherita Di Leo" 
An: GRASS-PSC 
Betreff: Re: [GRASS-PSC] [voting] printing of stickers and flyers for FOSS4G Europe



+1 , margherita
 


Il giorno dom 23 lug 2017 alle 00:03 Helena Mitasova  ha scritto:


+1, Helena
 



 
On Sat, Jul 22, 2017 at 11:37 AM, Michael Barton  wrote:


+1















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 Jul 22, 2017, at 9:44 AM, Vaclav Petras  wrote:
 


+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://urldefense.proofpoint.com/v2/url?u=https-3A__lists.osgeo.org_mailman_listinfo_grass-2Dpsc=DwIGaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=r2mIZCf-sP69gLJNyjiZ8w8Jcnv0GLJMnTGQdr5SFC4=JDFFu9LnjlMGlSuzoa6ix74jLvbKOHXXWaIwZrmA59Y=




___
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

North Carolina State University

1125 Jordan Hall

NCSU Box 8208

Raleigh, NC 27695-8208

http://www4.ncsu.edu/~hmitaso/

http://geospatial.ncsu.edu/

 

email: hmit...@ncsu.edu

ph: 919-513-1327 (no voicemail)

fax 919 515-7802







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



--









Margherita Di Leo








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



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

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

2017-06-16 Thread Peter Löwe
>2017-06-16 8:38 GMT+02:00 Markus Neteler :
>> Yes: I would like to propose Veronica Andreo
>> (https://veroandreo.wordpress.com ;
>> https://www.researchgate.net/profile/Veronica_Andreo2).

 

+1

Peter
 



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

[GRASS-PSC] new core developers: past procedures ?

2017-06-13 Thread Peter Löwe
Hi Markus, hi PSC,

are there already some kind of time-honored requirements against which 
potential core developer candidates could be gauged, or were gauged in the past 
?

best,
Peter







> Gesendet: Dienstag, 13. Juni 2017 um 08:59 Uhr
> Von: "Markus Neteler" 
> An: GRASS-PSC 
> Betreff: [GRASS-PSC] Let's approve new core developers
>
> PSC,
> 
> we didn't invite new core developers for a while, I think this should
> be done asap.
> 
> Again a somewhat sensitive topic, how shall we proceed? I have some
> ideas but did not approach those people yet.
> 
> Open discussion without names :-)
> 
> Markus
> 
> 
> -- 
> 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] Again: Jim Westervelt retirement: May 2017

2017-04-25 Thread Peter Löwe
Dear all,

 

since May is just about to start, I would like to reiterate the question of short term actions for Jim Westervelts upcoming retirement. Can we do a greeting card/flowers, or similar prior to the actions discussed earlier ? Anybody willing to take the lead ?

 

Best,

Peter
 

<peter.lo...@gmx.de>

 
 

Gesendet: Montag, 27. März 2017 um 10:53 Uhr
Von: "Peter Löwe" <peter.lo...@gmx.de>
An: GRASS-PSC <grass-psc@lists.osgeo.org>
Betreff: [GRASS-PSC] Jim Westervelt retirement: May 2017



Hi all,

 

FYI: Jim will transition into retirement /free-agent mode in May (not April), so we have some more time to decide on how to proceed.

 

Best,

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

[GRASS-PSC] Jim Westervelt: Sol Katz nominee

2017-03-24 Thread Peter Löwe
Hi,

 

does anyone have contact details for Jims family (wife) ? It would be handy to ensure that "someone" blocks relevant dates in his calendar ahead of time. How is this is usually handled for Sol Katz nominees ?

 

Cheers,

Peter
 








 





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

[GRASS-PSC] Request for Opinions: Preservation of video footage from Trento 2002

2017-01-23 Thread Peter Löwe
Dear PSC,

TIB Hannover (german national lib for sci & tech) continues to archive both 
recent and past scientific videos from OSGeo and especially GRASS GIS. In this 
vein, the video recordings from the Trento 2002 Meeting are currently ingested. 
Good news: All footage has been preserved, bad news: the quality is by modern 
standards pretty poor (RealMedia format). 
An example of the video quality is available here (beware: it runs 2hours -> 
1.7 Gb !!): 
http://178.248.245.19/mfc/medialink/6/m6462/Applications_and_techniques.mpg 
[listen to Helena at 21:00 minutes, Markus at 1:15 hours, etc .etc.]

TIB is capable to publish the Trento 2002 recordings on its AV-portal, 
including DOIs for each video. However, TIB wants to reconfirm that these 
low-quality videos actually do have value/significance for the OSGeo/GRASS 
community (I strongly believe they do). An alternative approach would be to 
only keep a still image for each video, plus the audio tracks. The decision how 
the videos should be made available will not influenced by costs, but rather 
significance of the content.
Since the recordings are pretty long (2 hours) and cover mutliple presentations 
within a session, it could be a challenge to determine a "fitting" still frame. 
DOI-links, as they are enabled via the TIB AV-portal (using DOI plus "media 
fragment identifiers" MFIDs) are a great way to cite or refer smaller outtakes 
of these lengthy recordings, like individual presentations or specific quotes. 

Your feedback would be much appreciated.

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

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

2016-09-06 Thread Peter Löwe
Hi all,

 

I also second Markus' nomination.

 

Best,

Peter


 



 
 

Gesendet: Dienstag, 06. September 2016 um 10:03 Uhr
Von: "Margherita Di Leo" 
An: "Helena Mitasova" 
Cc: GRASS-PSC 
Betreff: Re: [GRASS-PSC] [GRASS-announce] PSC election 2016 Result


Hi,
 
On Mon, Sep 5, 2016 at 8:34 PM, Helena Mitasova  wrote:

I strongly support nomination of Markus as PSC chair.

 



I support Markus' nomination, both for the priceless work done so far as chair and also for the fact that he received highest number of votes, as _expression_ of the recognition by the whole community. Markus, I hope you are willing to continue.

 

Regards, 

 

 
--









Margherita Di Leo










___ 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