<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Great, thank you Alessandro. <br>
</p>
<p>Would it be too inappropriate to squeeze in a "release" to
trigger the DOI creation so that we could manage Peter's deadline?
<br>
</p>
<p>I noticed that Jürgen announced that 3.16.16 is the last release
of this LTR. Maybe we could create a copy of the 3.16.16 release
called something like 3.16.16-final just to trigger the DOI? Or
would that cause some other unwanted effects?<br>
</p>
<p>Regards,</p>
<p>Anita<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 17.01.2022 16:33, Alessandro Pasotti
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAL5Q671raSTY5-NNc_gJnF57Lg=XOGz=Xo8cRLFWD1kCiSZvuQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hi Anita,</div>
<div><br>
</div>
<div>I followed the instructions and we should be good, but as
far as I know we would need to wait until the next release is
created in github to get the webhook triggered and the DOI
created.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Jan 17, 2022 at 4:20
PM Anita Graser <<a href="mailto:anitagraser@gmx.at"
moz-do-not-send="true" class="moz-txt-link-freetext">anitagraser@gmx.at</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Hi Alessandro,</p>
<p>That doesn't seem to be enough, unfortunately.<br>
</p>
<p>But the guide is really straightforward, so anyone with
sufficient privileges should be able to do it rather
quickly: <a
href="https://guides.lib.berkeley.edu/citeyourcode"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://guides.lib.berkeley.edu/citeyourcode</a></p>
<p>Regards,</p>
<p>Anita</p>
<p><br>
</p>
<div>On 17.01.2022 12:48, Alessandro Pasotti wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>Hi Anita,</div>
<div><br>
</div>
<div>I added you to the "maintain" role on qgis/QGIS ,
please let me know if it's enough.</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Jan 17, 2022
at 12:27 PM Anita Graser <<a
href="mailto:anitagraser@gmx.at" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">anitagraser@gmx.at</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px
0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
I have a Zenodo DOI for MovingPandas and it works
great. I checked if I<br>
can take care of it but I don't seem to have the
necessary rights to add<br>
qgis/QGIS repo to Zenodo. The only qgis repo where I
have sufficient<br>
rights is qgis/PSC.<br>
<br>
Anita<br>
<br>
<br>
On 17.01.2022 10:38, Peter Löwe wrote:<br>
> Dear QGIS Board, dear QGIS Developers,<br>
><br>
> this is very gentle reminder following up to my
mail to the QGIS Board from last week (see below): The
deadline to include a DOI for QGIS in the Springer
Handbook of Geographic Information is coming up on
Thursday. I just want to make sure that all software
projects covered in the Open Source chapter can make
an informed decision whether they want to have their
DOI referenced in the Handbook. Otherwise, the project
URL will be used for reference.<br>
><br>
> Currently the second Edition of the Springer
Handbook for Geographic Information (<a
href="https://link.springer.com/book/10.1007/978-3-540-72680-7"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://link.springer.com/book/10.1007/978-3-540-72680-7</a>)
is being finalised.<br>
><br>
> QGIS is covered in the chapter on Open Source GIS
(thanks to the volunteer work of Marco Hubentobler !).
Neither the Editors nor the Authors receive any pay
from Springer for their work and won't benefit from
the volumes sold.<br>
><br>
> Recently, new workflows for scientific citation
of software projects are becoming state of the art.
This includes references by persistent digital object
identifiers (DOI) to software projects instead of
URLs. DOI have several benefits over URLs, the biggest
advantage for this community might be that DOI-based
references allow to give due credit to the whole
project team, including first authors, developers, but
also maintainers and people in other roles.<br>
><br>
> The Springer Handbook will be around for at least
five, maybe ten years. One reason for DOI (which will
keep pointing to the latest QGIS release, and maybe
more up to date content (see #5 below) is to give
added value to the readers and not to bog them down
with obsolete information.<br>
><br>
> Until now, eight OSGeo projects will have their
DOI referenced in the Open Source Chapter, while six
more are in the process to register their DOI,
hopefully before Thursday (details here: <a
href="https://wiki.osgeo.org/wiki/DOI"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://wiki.osgeo.org/wiki/DOI</a>)<br>
><br>
> The QGIS community can of course register a DOI
whenever it decides to do so.<br>
><br>
> Some reasons for DOI for the QGIS community might
be:<br>
><br>
> 1) Little effort, no cost and significant
benefits for everybody who's involved in QGIS and can
use scientific credit for their careers (->
students, early career scientists, people on tenure
track).<br>
> 2) preservation of all code releases in an open
access long term repository (<a
href="https://en.wikipedia.org/wiki/Zenodo"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://en.wikipedia.org/wiki/Zenodo</a>),
free of charge and effortless for the project
community (bzw: NASA is also using this approach for
their data publishing: <a
href="https://earthdata.nasa.gov/collaborate/doi-process"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://earthdata.nasa.gov/collaborate/doi-process</a>)<br>
> 3) Reference by DOI is the way to go when citing
anything with a long list of authors/committers: QGIS
has about _1001_ committers according to GitHub,
that's a lot.<br>
> 4) When ORCIDs (<a href="https://orcid.org/"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://orcid.org/</a>)
for persons serving as developers, maintainers, etc.
are included into the committer - metadata
(GitHub-sided), the DOI workflows will pick this up
and will add due credit by reference to their citation
lists.<br>
> 5) DOI can be used to link information, inclduing
video recordings and presentations. Videos from FOSS4G
events can now be linked to software project DOI and
vice versa (and also linked to ORCIDs of real people),
like this one: Dobias, Martin: State of QGIS 3D, QGIS
ACoruña Conference 2019. <a
href="https://doi.org/10.5446/40791"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://doi.org/10.5446/40791</a><br>
><br>
> Registering a DOI for software projects takes
only a few minutes and is described here:<br>
> - Howto mit Screenshots: <a
href="https://guides.lib.berkeley.edu/citeyourcode"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://guides.lib.berkeley.edu/citeyourcode</a><br>
> - Youtube Howto Video: <a
href="https://www.youtube.com/watch?v=A9FGAU9S9Ow"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://www.youtube.com/watch?v=A9FGAU9S9Ow</a><br>
> - Inclusion of a CFF and a JSON file in the
codebase for automated GitHub-Zenodo integration: <a
href="https://wiki.osgeo.org/wiki/Persistent_identifiers(pid)#Howto_2"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://wiki.osgeo.org/wiki/Persistent_identifiers(pid)#Howto_2</a><br>
><br>
> Please contact me if you have any questions on
this.<br>
><br>
> Best regards,<br>
> Peter<br>
> <a
href="https://wiki.osgeo.org/wiki/User:Peter_Loewe"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://wiki.osgeo.org/wiki/User:Peter_Loewe</a><br>
><br>
>> Gesendet: Dienstag, 11. Januar 2022 um 12:57
Uhr<br>
>> Von: "Peter Löwe" <<a
href="mailto:peter.loewe@gmx.de" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">peter.loewe@gmx.de</a>><br>
>> An: <a href="mailto:board@qgis.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">board@qgis.org</a>, <a
href="mailto:psc@qgis.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">psc@qgis.org</a><br>
>> Betreff: DOI for QGIS project / Springer
Handbook of Geoinformatics<br>
>><br>
>> Dear QGIS community,<br>
>><br>
>> I'm reaching out to you because of an
opportunity for the QGIS project, which surfaced
recently:<br>
>> The upcoming second edition of the Springer
Handbook of Geoinformatics will cover the QGIS
project. The Handbook project has been delayed due to
the Pandemic, but will be completed in a few weeks. I
am serving as the editor of the Handbook chapter about
Open Source Geoinformatics.<br>
>><br>
>> Recently, new workflows for scientific
citation of software projects have emerged and are
becoming state of the art. This includes references by
persistent digital object identifiers (DOI) to
software projects instead of URLs. DOI-based
references allow to give due credit to the whole
project team, including first authors, developers, but
also maintainers and people in other roles.<br>
>><br>
>> The OSGeo projects GRASS GIS, GMT, MapServer,
MOSS and rasdaman have already registered their own
DOI, OSGeoLive will follow soon.<br>
>> Hands on information how to register a DOI
for a OSGeo project are available here: <a
href="https://wiki.osgeo.org/wiki/Persistent_identifiers(pid)"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://wiki.osgeo.org/wiki/Persistent_identifiers(pid)</a>:<br>
>><br>
>> As an example, this is the DOI for GRASS GIS:
<a href="https://doi.org/10.5281/zenodo.5810537"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://doi.org/10.5281/zenodo.5810537</a><br>
>><br>
>> The Editors of the Springer Handbook agree
that including DOI references for Open Source projects
is a win-win-scenario for the upcoming book and also
the OSGeo project communities. They have extended the
production deadline until January 20 to give
additional software projects the opportunity to
register a DOI to be included in the book chapter.<br>
>><br>
>> If the QGIS project registers a DOI (takes
only a few minutes) before the deadline of January 20,
I would gladly include it in the Open Source
Geoinformatics chapter reference section.<br>
>><br>
>><br>
>> Please let me know if you have any questions.<br>
>><br>
>> Best,<br>
>> Peter<br>
>> <a
href="https://wiki.osgeo.org/wiki/User:Peter_Loewe"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://wiki.osgeo.org/wiki/User:Peter_Loewe</a><br>
>><br>
><br>
> _______________________________________________<br>
> Qgis-psc mailing list<br>
> <a href="mailto:Qgis-psc@lists.osgeo.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">Qgis-psc@lists.osgeo.org</a><br>
> <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-psc"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a><br>
_______________________________________________<br>
Qgis-psc mailing list<br>
<a href="mailto:Qgis-psc@lists.osgeo.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">Qgis-psc@lists.osgeo.org</a><br>
<a
href="https://lists.osgeo.org/mailman/listinfo/qgis-psc"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a><br>
</blockquote>
</div>
<br clear="all">
<br>
-- <br>
<div dir="ltr">
<div dir="ltr">
<div>Alessandro Pasotti</div>
<div>QCooperative: <a
href="https://www.qcooperative.net"
target="_blank" moz-do-not-send="true">www.qcooperative.net</a><br>
</div>
ItOpen: <a href="http://www.itopen.it"
target="_blank" moz-do-not-send="true">www.itopen.it</a></div>
</div>
</blockquote>
</div>
</blockquote>
</div>
<br clear="all">
<br>
-- <br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>Alessandro Pasotti</div>
<div>QCooperative: <a href="https://www.qcooperative.net"
target="_blank" moz-do-not-send="true">www.qcooperative.net</a><br>
</div>
ItOpen: <a href="http://www.itopen.it" target="_blank"
moz-do-not-send="true">www.itopen.it</a></div>
</div>
</blockquote>
</body>
</html>