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

Veronica Andreo veroandreo at gmail.com
Mon May 24 04:48:21 PDT 2021


+1 from my side too

El lun., 24 may. 2021 03:23, Moritz Lennert <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> 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
>> [2] https://github.com/zenodo/zenodo/issues/826
>>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20210524/016563fe/attachment.html>


More information about the grass-dev mailing list