[release planning] Enable Zenodo before 7.8.6 and 8.0.0

--===============7448905365732453147==
Content-Type: multipart/alternative; boundary="0000000000004f163f05c309e21e"

--0000000000004f163f05c309e21e
Content-Type: text/plain; charset="UTF-8"

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

--0000000000004f163f05c309e21e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi all,<br></div><div><br></div><div>Let&#39;s enable=
 the Zenodo link before 7.8.6 and 8.0(.0?) releases to get DOIs and Zenodo =
records.<br></div><div><br></div><div>Solving
 the whole DOI linking and Zenodo archiving for the old versions may be=20
complex [1], but enabling the link between GitHub and Zenodo is trivial=20
(one click) and every newly created GitHub release (we do those) will be
 automatically registered and receive DOI.</div><div><br></div><div>Zenodo
 uses a system of DOI versions and a main DOI (Concept DOI). Whether it is =
an ideal=20
system, that&#39;s a question, but it is currently the expected one since i=
t
 is the same for everything on Zenodo. It is used automatically when=20
using the GitHub-Zenodo integration.</div><div><br></div><div>It seems I
 have the permissions to enable it for GRASS GIS. The one who enables=20
that becomes a maintainer of it. I&#39;m fine with that, but I won&#39;t be=
=20
uploading any older versions. The <span class=3D"gmail-ng">maintainer</span=
> can be changed later by contacting Zenodo support [2].<br></div><div><br>=
</div><div>Although there are things to figure out in terms of next steps, =
I don&#39;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 a=
re expected more and more.<br></div><div><br></div><div>Thoughts?</div><div=
><br></div><div>Vaclav<br></div><div><br></div><div>[1] <a href=3D"https://=
grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage" target=3D"_blank">https://g=
rasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage</a></div><div>[2] <a href=3D"=
https://github.com/zenodo/zenodo/issues/826" target=3D"_blank">https://gith=
ub.com/zenodo/zenodo/issues/826</a></div></div>

--0000000000004f163f05c309e21e--

--===============7448905365732453147==
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

--===============7448905365732453147==--