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

--===============5305316280712020815==
Content-Type: multipart/alternative; boundary="000000000000f416a205c4109507"

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

Hi Peter, all, thanks for the answers. I have more questions assuming
that's okay.

On Fri, Jun 4, 2021 at 2:57 AM Peter L=C3=B6we <[email protected]> wrote:

> =3D=3D> the CodeMeta-Project is currenlty pushing software citation stand=
ards:
> https://codemeta.github.io/
>

Thanks. The roles there seem to be more clear. Any opinion on CodeMata
versus CFF (see also below)?


>
>> 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).
>>
>
> Any opinions on how useful this is? We want a good archive of old
> versions, but does someone need DOIs for old releases?
>
> =3D=3D> This depends on wether the community wants to give due credit by
> citation to the persons which were involved in the previous releases.
>

Currently, the author list maintained in the source code is cumulative as
far as I know, so old authors are still included as authors, so only use
cases for that would be citing old releases in paper or by the new versions
of software software. None seem likely to me. What do you think?


> Any suggestions on includings DOI into source code? It seems to me that
> you can only use the generic/concept one and tell people to get the recen=
t
> one. I didn't figure out the DOI reservation for GitHub repos.
>

Rather than where to put it - although that's important, too - my question
is about which DOI? The main one everywhere or somehow try to put there the
version specific one if that's even possible. It seems to me that the main
DOI is the only feasible option.


> =3D=3D> A JSON file could be included. This way, the information is both
> readable for humans and automated access:
> https://codemeta.github.io/codemeta-generator/
>

I was thinking about the Citation File Format as I have seen it used quite
a bit. Any opinions on that?

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

<div dir=3D"ltr"><div>Hi Peter, all, thanks for the answers. I have more qu=
estions assuming that&#39;s okay.<br></div><br><div class=3D"gmail_quote"><=
div>On Fri, Jun 4, 2021 at 2:57 AM Peter L=C3=B6we &lt;<a href=3D"mailto:pe=
[email protected]">[email protected]</a>&gt; wrote: <br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><div><div style=3D"font-family:Verdana=
;font-size:12px"><div><div name=3D"quote" style=3D"margin:10px 5px 5px 10px=
;padding:10px 0px 10px 10px;border-left:2px solid rgb(195,217,229)"><div na=
me=3D"quoted-content"><div class=3D"gmail_quote"><div>=3D=3D&gt; the CodeMe=
ta-Project is currenlty pushing software citation standards:=C2=A0<a href=
=3D"https://codemeta.github.io/" target=3D"_blank">https://codemeta.github.=
io/</a></div>

</div></div></div></div></div></div></blockquote><div><br></div><div>Thanks=
. The roles there seem to be more clear. Any opinion on CodeMata versus CFF=
 (see also below)?<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div><div style=3D"font-family:Verdana;font-size:12px">=
<div><div name=3D"quote" style=3D"margin:10px 5px 5px 10px;padding:10px 0px=
 10px 10px;border-left:2px solid rgb(195,217,229)"><div name=3D"quoted-cont=
ent"><div class=3D"gmail_quote">



<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">=C2=A0<div><div style=3D"=
font-family:Verdana;font-size:12px"><div>BTW, ways to retro-provide=C2=A0DO=
I versioning for previous GRASS releases would be an rewarding topic to dis=
cuss with Data Cite (the DOI infrastructure community).</div>
</div>
</div>
</blockquote>

<div>=C2=A0</div>

<div>Any opinions on how useful this is? We want a good archive of old vers=
ions, but does someone need DOIs for old releases?</div>

<div>=C2=A0</div>

<div>=3D=3D&gt; This depends on wether the community wants to give due cred=
it by citation to the persons which were involved in the previous releases.=
</div></div></div></div></div></div></div></blockquote><div><br></div><div>=
Currently, the author list maintained in the source code is cumulative as f=
ar as I know, so old authors are still included as authors, so only use cas=
es for that would be citing old releases in paper or by the new versions of=
 software software. None seem likely to me. What do you think?<br></div><di=
v>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div s=
tyle=3D"font-family:Verdana;font-size:12px"><div><div name=3D"quote" style=
=3D"margin:10px 5px 5px 10px;padding:10px 0px 10px 10px;border-left:2px sol=
id rgb(195,217,229)"><div name=3D"quoted-content"><div class=3D"gmail_quote=
">



<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div style=3D"font-family:Verdana;font-size:12px">
<div></div>
</div>
</div>
</blockquote>



<div>Any suggestions on includings DOI into source code? It seems to me tha=
t you can only use the generic/concept one and tell people to get the recen=
t one. I didn&#39;t figure out the DOI reservation for GitHub repos.</div><=
/div></div></div></div></div></div></blockquote><div><br></div><div>Rather =
than where to put it - although that&#39;s important, too - my question is =
about which DOI? The main one everywhere or somehow try to put there the ve=
rsion specific one if that&#39;s even possible. It seems to me that the mai=
n DOI is the only feasible option.<br></div><div>=C2=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex"><div><div style=3D"font-family:Verdana;=
font-size:12px"><div><div name=3D"quote" style=3D"margin:10px 5px 5px 10px;=
padding:10px 0px 10px 10px;border-left:2px solid rgb(195,217,229)"><div nam=
e=3D"quoted-content"><div class=3D"gmail_quote">



<div>=3D=3D&gt; A JSON file could be included. This way, the information is=
 both readable for humans and automated access:=C2=A0<a href=3D"https://cod=
emeta.github.io/codemeta-generator/" target=3D"_blank">https://codemeta.git=
hub.io/codemeta-generator/</a>=C2=A0</div>

</div></div></div></div></div></div></blockquote><div><br></div><div>I was =
thinking about the Citation File Format as I have seen it used quite a bit.=
 Any opinions on that?<br></div><div>=C2=A0</div></div></div>

--000000000000f416a205c4109507--

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

--===============5305316280712020815==--