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

[Vaclav Petras]

Dear all,

Zenodo-GitHub link is enabled. There is nothing to see or customize on
Zenodo.org until a release happens. It is important that every release is a
GitHub release rather than just a tag, but other than that, it will work
automatically.

I won't be creating .zenodo.json right away, but will probably wait until
7.8.6 or 8.0.alpha happens to see how good or bad the metadata is. Then we
will see what priority to assign to creating .zenodo.json.

Best,
Vaclav

On Mon, May 24, 2021 at 9:06 PM Vaclav Petras <wenzeslaus at gmail.com> wrote:

> Thanks everyone for the support.
>
> I was able to identify some potential issues. Namely, the auto-generated
> metadata on Zenodo does not seem to be that great and that includes basic
> things like title and license. How an author list will look is hard to say
> without trying, but it is promised to be sensible. It seems that a lot of
> projects just solve this using a .zenodo.json configuration file which
> includes this info, e.g. a full author list.
>
> Although these metadata issues are certainly visible, a DOI will be
> generated and usable by itself in any case. Additionally, metadata can be
> edited manually after the publishing/release. Finally, having .zenodo.json
> is doable (probably through CITATION.cff which would be good to have
> anyway). Thus, I don't see this as a blocker, just as something to resolve
> on the way.
>
> On Mon, May 24, 2021 at 1:27 PM Stefan Blumentrath <
> Stefan.Blumentrath at nina.no> wrote:
>
>
>> 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...
>>
>
> There seems to be exactly n-1 GRASS-related records not in the community
> (where n is all the GRASS-related records). Are we looking at the same one?
>
> https://zenodo.org/communities/grass/
>
>
>>
>> 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>
>> 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
>> <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
>> 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>
>>
>> _______________________________________________
>> 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/20210531/2583b5eb/attachment.html>