All right, that is yes for ORCiD IDs. Next question: Are we putting them to contributors.csv as a new column or doing something else?
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. 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 for citation. How do you qualify for the list? You get to the top N committers on GitHub? Once we decide where the ORCIDs should go, we can start to collect them with PRs. On Thu, Jan 13, 2022 at 9:46 AM Michael Barton <[email protected]> wrote: > I agree about including ORCID ID. > > Here is mine: 0000-0003-2561-1927 > > Michael Barton > School of Human Evolution &Social Change > School of Complex Adaptive System Science > Center for Social Dynamics & Complexity > Arizona State University > > ...Sent from my iPad > > On Jan 13, 2022, at 7:30 AM, Huidae Cho <[email protected]> wrote: > > > All, > > I agree with Peter. +1 for ORCIDs. > > Best, > Huidae > > On Thu, Jan 13, 2022 at 9:23 AM Peter Löwe <[email protected]> wrote: > >> Hi all, >> I'm not part of the PSC but would like to strongly encourage to >> include ORCIDs. >> Once this is achieved, credit for each following GRASS release will >> automatically be transferred to all ORCID accounts in the commiters list. >> Commiters without an ORCID will still benefit from the citation options >> ("Cite as") on the GRASS landing page at Zenodo. >> >> Seems like none of the other OSGeo projects using DOI has implemented >> that (except for an early proof of content for the ploewe/MOSS github repo >> -> https://doi.org/10.5281/zenodo.4931427 >> <https://urldefense.com/v3/__https://doi.org/10.5281/zenodo.4931427__;!!IKRxdwAv5BmarQ!JZ25YcMjdi1ZLlqFRywxJVJPUTzsYYdqel0skeCmzfSIPcLofjQy9rYoSegCL7oIH0s$> >> :-) ). >> Could be another first for the GRASS project ! >> >> Best, >> Peter >> >> <[email protected]> >> >> >> *Gesendet:* Donnerstag, 13. Januar 2022 um 14:28 Uhr >> *Von:* "Veronica Andreo" <[email protected]> >> *An:* "Vaclav Petras" <[email protected]> >> *Cc:* "GRASS-PSC" <[email protected]> >> *Betreff:* Re: [GRASS-PSC] GRASS DOI >> >> >> El jue, 13 ene 2022 a las 3:19, Vaclav Petras (<[email protected]>) >> escribió: >> >>> >>> On Wed, Jan 12, 2022 at 4:40 PM Markus Neteler <[email protected]> >>> wrote: >>> >>>> >>>> FYI: GDAL started just today to generate a Zenodo entry. Even took the >>>> top 16 commiters [3] according to GitHub and created a .zenodo.json >>>> file to control authorship: >>>> >>>> https://github.com/OSGeo/gdal/pull/5101/files >>>> <https://urldefense.com/v3/__https://github.com/OSGeo/gdal/pull/5101/files__;!!IKRxdwAv5BmarQ!JZ25YcMjdi1ZLlqFRywxJVJPUTzsYYdqel0skeCmzfSIPcLofjQy9rYoSegC6o2eHgE$> >>> >>> >>> .zenodo.json or CITATION.cff both should work now with Zenodo. >>> CITATION.cff is new, but it works as far as I know. .zenodo.json allows you >>> to set some Zenodo specific info. CITATION.cff is picked by other systems >>> such as GitHub or FAIR systems. We could generate one from the other (that >>> was recommended practice before Zenodo started to support CITATION.cff. >>> >>> In case we generate the file from the existing contributors.csv, we can >>> generate both. Adding ORCiDs there would be nice. >>> >> >> +1 for adding ORCiD for those that have it >> >> >>> >>> Is contributors.csv or starting a new list with the GitHub committers >>> like what GDAL did more appropriate? >>> >> >> Maybe a new one is better. It will probably also depend if we want to >> list all ppl in the contributors.csv or the main xx as in gdal. >> >> Vero >> _______________________________________________ grass-psc mailing list >> [email protected] >> https://lists.osgeo.org/mailman/listinfo/grass-psc >> <https://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!JZ25YcMjdi1ZLlqFRywxJVJPUTzsYYdqel0skeCmzfSIPcLofjQy9rYoSegCvdpqFxo$> >> _______________________________________________ >> grass-psc mailing list >> [email protected] >> https://lists.osgeo.org/mailman/listinfo/grass-psc >> <https://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!JZ25YcMjdi1ZLlqFRywxJVJPUTzsYYdqel0skeCmzfSIPcLofjQy9rYoSegCvdpqFxo$> >> > > > -- > Huidae Cho, Ph.D., GISP, /hidɛ > <https://urldefense.com/v3/__http://ipa-reader.xyz/?text=hid**A__;yZs!!IKRxdwAv5BmarQ!JZ25YcMjdi1ZLlqFRywxJVJPUTzsYYdqel0skeCmzfSIPcLofjQy9rYoSegCEPvay40$> > t͡ɕo/, 조희대, 曺喜大 > GRASS GIS Developer > https://idea.isnew.info/ > <https://urldefense.com/v3/__https://idea.isnew.info/__;!!IKRxdwAv5BmarQ!JZ25YcMjdi1ZLlqFRywxJVJPUTzsYYdqel0skeCmzfSIPcLofjQy9rYoSegCq1om_4c$> > _______________________________________________ > grass-psc mailing list > [email protected] > > https://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!JZ25YcMjdi1ZLlqFRywxJVJPUTzsYYdqel0skeCmzfSIPcLofjQy9rYoSegCvdpqFxo$ > > _______________________________________________ > grass-psc mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/grass-psc >
_______________________________________________ grass-psc mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-psc
