[GRASS-dev] [release planning] Enable Zenodo before 7.8.6 and 8.0.0

Stefan Blumentrath Stefan.Blumentrath at nina.no
Mon May 24 10:27:14 PDT 2021


Sonds like a very good plan. Appreciate the effort.

There is already a GRASS GIS community on Zenodo, managed by Pietro.

There are way more GRASS related records in zenodo than registered in that community. Wound probably be useful to register relevant entries in a GRASS community...

Would it be an option to develop the community in that direction, Pietro? If others too think that's useful ...

Cheers
Stefan
________________________________
From: grass-dev <grass-dev-bounces at lists.osgeo.org> on behalf of Veronica Andreo <veroandreo at gmail.com>
Sent: Monday, May 24, 2021 1:48:21 PM
To: Moritz Lennert <mlennert at club.worldonline.be>
Cc: grass-dev <grass-dev at lists.osgeo.org>; Peter Löwe <peter.loewe at gmx.de>
Subject: Re: [GRASS-dev] [release planning] Enable Zenodo before 7.8.6 and 8.0.0

+1 from my side too

El lun., 24 may. 2021 03:23, Moritz Lennert <mlennert at club.worldonline.be<mailto:mlennert at club.worldonline.be>> escribió:
Clear +1 from me.

Moritz

Le 24 mai 2021 03:08:06 GMT+01:00, Vaclav Petras <wenzeslaus at gmail.com<mailto:wenzeslaus at gmail.com>> a écrit :
Hi all,

Let's enable the Zenodo link before 7.8.6 and 8.0(.0?) releases to get DOIs and Zenodo records.

Solving the whole DOI linking and Zenodo archiving for the old versions may be complex [1], but enabling the link between GitHub and Zenodo is trivial (one click) and every newly created GitHub release (we do those) will be automatically registered and receive DOI.

Zenodo uses a system of DOI versions and a main DOI (Concept DOI). Whether it is an ideal system, that's a question, but it is currently the expected one since it is the same for everything on Zenodo. It is used automatically when using the GitHub-Zenodo integration.

It seems I have the permissions to enable it for GRASS GIS. The one who enables that becomes a maintainer of it. I'm fine with that, but I won't be uploading any older versions. The maintainer can be changed later by contacting Zenodo support [2].

Although there are things to figure out in terms of next steps, I don't see much risk in enabling it. There are no choices available in the setup or in terms of alternatives. DOI and some kind of registration are expected more and more.

Thoughts?

Vaclav

[1] https://grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgrasswiki.osgeo.org%2Fwiki%2FGitHub-Zenodo_linkage&data=04%7C01%7C%7Cfba8a69fdf764573335708d91ea9dec9%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637574537213313936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hCfCxTMHSG5PluYrYfies7ZWg9F3hCSM%2B1aC8WzgD4E%3D&reserved=0>
[2] https://github.com/zenodo/zenodo/issues/826<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fzenodo%2Fzenodo%2Fissues%2F826&data=04%7C01%7C%7Cfba8a69fdf764573335708d91ea9dec9%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637574537213313936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=SHGhq70btcEWoFgXiip%2FKVGKfKAy3K8B1pen%2BjIG13Q%3D&reserved=0>
_______________________________________________
grass-dev mailing list
grass-dev at lists.osgeo.org<mailto:grass-dev at lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/grass-dev<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Fgrass-dev&data=04%7C01%7C%7Cfba8a69fdf764573335708d91ea9dec9%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637574537213323931%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1Bk3qlRhlR5jphU%2BlBob9UyY%2BxStFXFXS%2FREBYn5JVk%3D&reserved=0>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20210524/a77bd190/attachment-0001.html>


More information about the grass-dev mailing list