Re: [release planning] Enable Zenodo before 7.8.6 and 8.0.0
Peter Löwe <[email protected]> Tue, 25 May 2021 14:30:40 +0200
| Newsgroups | gmane.comp.gis.grass.devel |
|---|---|
| Message-ID | <trinity-c2e88e91-d1e1-4330-b29f-bcb5d17faf21-1621945840276@3c-app-gmx-bap10> |
--===============3662360935681051361== Content-Type: text/html; charset=UTF-8 <html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi Vaclav, all,</div> <div> </div> <div>it's great to hear that the GRASS project is about to embrace DOI and long term archiving by Zenodo.<br/> </div> <div>The MOSS project minted its first DOI as a proof concept in the process of becoming a OSGeo heritage project (https://zenodo.org/record/4719685#.YKzpGKgzaUk). For this, we used stakeholders roles according to MARC21 like the R project does: https://journal.r-project.org/archive/2012-1/RJournal_2012-1_Hornik~et~al.pdf</div> <div> </div> <div>BTW, ways to retro-provide DOI versioning for previous GRASS releases would be an rewarding topic to discuss with Data Cite (the DOI infrastructure community). DOI for software versioning is is still a developing topic. Feedback from the GRASS community would be valuable to push this forward.</div> <div> </div> <div>Best,</div> <div>Peter</div> <div> </div> <div class="signature"><[email protected]></div> <div> <div> <div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);"> <div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Montag, 24. Mai 2021 um 04:08 Uhr<br/> <b>Von:</b> "Vaclav Petras" <[email protected]><br/> <b>An:</b> "[email protected]" <[email protected]><br/> <b>Cc:</b> "Peter Löwe" <[email protected]><br/> <b>Betreff:</b> [release planning] Enable Zenodo before 7.8.6 and 8.0.0</div> <div> <div> <div>Hi all,</div> <div> </div> <div>Let's enable the Zenodo link before 7.8.6 and 8.0(.0?) releases to get DOIs and Zenodo records.</div> <div> </div> <div>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.</div> <div> </div> <div>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.</div> <div> </div> <div>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 <span class="gmail-ng">maintainer</span> can be changed later by contacting Zenodo support [2].</div> <div> </div> <div>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.</div> <div> </div> <div>Thoughts?</div> <div> </div> <div>Vaclav</div> <div> </div> <div>[1] <a href="https://grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage" target="_blank">https://grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage</a></div> <div>[2] <a href="https://github.com/zenodo/zenodo/issues/826" target="_blank">https://github.com/zenodo/zenodo/issues/826</a></div> </div> </div> </div> </div> </div></div></body></html> --===============3662360935681051361== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ grass-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-dev --===============3662360935681051361==--