On Tue, Jan 4, 2022 at 4:39 PM Vaclav Petras <[email protected]> wrote:
>
> Dear Helena and all,
>
> Yes, it is auto-generated by Zenodo. It was the first step - to get a DOI 
> (main one and one for each release). Now we need to decide what is right for 
> the authors list.
>
> The current one looks messy. That is true. However, is it wrong? Or, in what 
> way is it wrong?
>
> GitHub handles might be appropriate when that's all people choose to reveal 
> on GitHub, although it looks wrong in academia. However, looking at the list, 
> it is likely that some people just never came around to adding their name to 
> GitHub (while having it in the source code). Some others have just part of 
> their name, all-caps name, and yet some others have their name in two 
> languages.
>
> Author order is derived from GitHub > Insights > Contributors [1] which is 
> mostly good from a software maintenance perspective (recency and line 
> volume). How well it represents the order of contributors in terms of credit 
> is a question related to the whole "academic credit for software" debate. The 
> whole auto-generated list can be in this case replaced by a CITATION.cff file 
> which Zenodo will now pick up and use.
>
> Action item 1: Add or improve your name on GitHub. Use whatever you would use 
> when authoring a paper or a book. This name may also show in your commits. 
> See also what `git config --get user.name` gives you.
>
> Action item 2: See where you are in the list or if you are even there. 
> Discuss on the grass-dev mailing list or complain to me privately how to 
> better represent your contribution.
>
> I would be happy to discuss other ideas people have. Just let me know, e.g., 
> on grass-dev.

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

Perhaps interesting for us as well.

Best,
Markus

[3] Even's email on the matter:
https://lists.osgeo.org/pipermail/gdal-dev/2022-January/055236.html

> Best,
> Vaclav
>
> [1] https://github.com/OSGeo/grass/graphs/contributors
> [2] https://doi.org/10.5281/zenodo.5176030
_______________________________________________
grass-psc mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-psc

Reply via email to