Re: [release planning] Enable Zenodo before 7.8.6 and 8.0.0

--===============0528740287019432046==
Content-Type: multipart/alternative; boundary="00000000000023e06a05c311fd0a"

--00000000000023e06a05c311fd0a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

+1 from my side too

El lun., 24 may. 2021 03:23, Moritz Lennert <[email protected]>
escribi=C3=B3:

> Clear +1 from me.
>
> Moritz
>
> Le 24 mai 2021 03:08:06 GMT+01:00, Vaclav Petras <[email protected]> a
> =C3=A9crit :
>>
>> 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 th=
e
>> 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 setu=
p
>> or in terms of alternatives. DOI and some kind of registration are expec=
ted
>> 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
> [email protected]
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>

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

<div dir=3D"auto">+1 from my side too</div><br><div class=3D"gmail_quote"><=
div dir=3D"ltr" class=3D"gmail_attr">El lun., 24 may. 2021 03:23, Moritz Le=
nnert &lt;<a href=3D"mailto:[email protected]">[email protected]=
ldonline.be</a>&gt; escribi=C3=B3:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div>Clear +1 from me. <br><br>Moritz<br><br><div class=3D"gmail_quote">Le =
24 mai 2021 03:08:06 GMT+01:00, Vaclav Petras &lt;<a href=3D"mailto:wenzesl=
[email protected]" target=3D"_blank" rel=3D"noreferrer">[email protected]</a=
>&gt; a =C3=A9crit=C2=A0:<blockquote class=3D"gmail_quote" style=3D"margin:=
0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<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>maintainer</span> can be changed la=
ter 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 muc=
h risk in enabling it. There are no choices available in the setup or in te=
rms of alternatives. DOI and some kind of registration are expected more an=
d more.<br></div><div><br></div><div>Thoughts?</div><div><br></div><div>Vac=
lav<br></div><div><br></div><div>[1] <a href=3D"https://grasswiki.osgeo.org=
/wiki/GitHub-Zenodo_linkage" target=3D"_blank" rel=3D"noreferrer">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" rel=3D"noref=
errer">https://github.com/zenodo/zenodo/issues/826</a></div></div>
</blockquote></div></div>_______________________________________________<br=
>
grass-dev mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank" rel=3D"noref=
errer">[email protected]</a><br>
<a href=3D"https://lists.osgeo.org/mailman/listinfo/grass-dev" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://lists.osgeo.org/mailman/listinf=
o/grass-dev</a><br>
</blockquote></div>

--00000000000023e06a05c311fd0a--

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

--===============0528740287019432046==--