<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi Vero, PSC, all,</div>
<div> </div>
<div>this discussion might get us to the current edge of software citation best practices: this topic is not (yet) mentionend in the FAIR Principles for Research Software (https://rd-alliance.org/group/fair-research-software-fair4rs-wg/outcomes/fair-principles-research-software-fair4rs)</div>
<div> </div>
<div>IMHO, updating the contributor list for every release compares to a new volume of a Journal Publication (as an analogy for the GRASS project with its Concept DOI).</div>
<div> </div>
<div>I propose to reach out to the RDA / FORCE 11 communities on this, which should be quick & easy.</div>
<div> </div>
<div>Best,</div>
<div>Peter</div>
<div><br/>
</div>
<div class="signature"><peter.loewe@gmx.de></div>
<div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Dienstag, 21. Juni 2022 um 11:35 Uhr<br/>
<b>Von:</b> "Veronica Andreo" <veroandreo@gmail.com><br/>
<b>An:</b> "Markus Neteler" <neteler@osgeo.org><br/>
<b>Cc:</b> "GRASS-PSC" <grass-psc@lists.osgeo.org><br/>
<b>Betreff:</b> Re: [GRASS-PSC] GRASS DOI</div>
<div name="quoted-content">
<div>
<div>Hi Markus, all</div>
<div class="gmail_quote">
<div class="gmail_attr">El mar, 7 jun 2022 a las 11:42, Markus Neteler (<<a href="mailto:neteler@osgeo.org" onclick="parent.window.location.href='mailto:neteler@osgeo.org'; return false;" target="_blank">neteler@osgeo.org</a>>) escribió:</div>
<blockquote class="gmail_quote" style="margin: 0.0px 0.0px 0.0px 0.8ex;border-left: 1.0px solid rgb(204,204,204);padding-left: 1.0ex;">Hi PSC,<br/>
<br/>
On Sun, Feb 6, 2022 at 9:55 PM Markus Neteler <<a href="mailto:neteler@osgeo.org" onclick="parent.window.location.href='mailto:neteler@osgeo.org'; return false;" target="_blank">neteler@osgeo.org</a>> wrote:<br/>
> On Thu, Jan 13, 2022 at 4:26 PM Vaclav Petras <<a href="mailto:wenzeslaus@gmail.com" onclick="parent.window.location.href='mailto:wenzeslaus@gmail.com'; return false;" target="_blank">wenzeslaus@gmail.com</a>> wrote:<br/>
> ><br/>
> > All right, that is yes for ORCiD IDs.<br/>
> ><br/>
> > Next question: Are we putting them to contributors.csv as a new column or doing something else?<br/>
><br/>
> In pull request<br/>
> <a href="https://github.com/OSGeo/grass/pull/2177" target="_blank">https://github.com/OSGeo/grass/pull/2177</a><br/>
> I have added a new orcid column (<a href="https://orcid.org/" target="_blank">https://orcid.org/</a>) to the file.<br/>
><br/>
> I have also made a quick round of searches to identify some ORCIDs.<br/>
> Please review.<br/>
<br/>
Still valid :-)<br/>
<br/>
> > In case we create another file (CITATION.cff or .zenodo.json) with a list of names from GitHub, it seems we have two different lists of authors.<br/>
> > Or is that what we want? A list of all authors/contributors including the very historical ones and another shorter list of people which is used<br/>
> > for citation. How do you qualify for the list? You get to the top N committers on GitHub?<br/>
><br/>
> Perhaps something like<br/>
> - list from <a href="https://github.com/OSGeo/grass/graphs/contributors" target="_blank">https://github.com/OSGeo/grass/graphs/contributors</a><br/>
> - order by commits<br/>
> - consider the last 12 months.<br/>
<br/>
What do you think? IMHO the CITATION.cff / .zenodo.json could change<br/>
from release to release since the contributors per release are<br/>
changing.</blockquote>
<div> </div>
<div>I personally like this idea as it seems fair to those contributing more in each release.</div>
<div> </div>
<div>Vero</div>
</div>
</div>
_______________________________________________ grass-psc mailing list grass-psc@lists.osgeo.org <a href="https://lists.osgeo.org/mailman/listinfo/grass-psc" target="_blank">https://lists.osgeo.org/mailman/listinfo/grass-psc</a></div>
</div>
</div>
</div></div></body></html>