<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi,</p>
<p>Just to mention that GDAL, PROJ and GRASS rely on the
zenodo-github integration, so that when a github release is
published, zenodo automatically creates a new DOI for it (as a
"child" under the generic DOI for the software). GRASS has notes
about that in
<a class="moz-txt-link-freetext" href="https://grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage">https://grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage</a><br>
</p>
<p>Even<br>
</p>
<div class="moz-cite-prefix">Le 30/05/2024 à 17:26, Daniel Baston a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CA+K_q_rHg11+WtTuTPzF2nq2Q+7s6ecUrNUPFuOcueOAyPehyA@mail.gmail.com">
<div dir="ltr">
<div>Hello,</div>
<div><br>
</div>
<div>Would there be any objection to me uploading the most
recent release of GEOS to <a href="http://zenodo.org"
moz-do-not-send="true">zenodo.org</a>? Uploading a release
generates a digital object identifier (DOI) that can be used
to cite a specific release of GEOS, as well as a "concept" DOI
that can be used to cite GEOS in general. At least in the US
government, having a persistent identifier for software
citation is becoming a requirement for funding.</div>
<div><br>
</div>
<div>As an example, here is the <a href="http://zenodo.org"
moz-do-not-send="true">zenodo.org</a> entry for GDAL: <a
href="https://zenodo.org/records/11175199"
moz-do-not-send="true" class="moz-txt-link-freetext">https://zenodo.org/records/11175199</a></div>
<div><br>
</div>
<div>Dan<br>
</div>
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.spatialys.com">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
</body>
</html>