Fix author names in zenodo record
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 171
- Forks
- 75
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 20
Description
I'm in the process of citing https://zenodo.org/records/14755802, and I noticed that some of the author names need fixing. For the existing record, I think this can/has to be manually done. In the future I'm not 100% sure how to fix this. There are some fixes that could be done by using a git mailmap file, but the git shortlog output shows some names that are correct (e.g., Matthew Hartley) that are not correct on the zenodo record.
% git shortlog -sn
438 Josh Moore
130 Sébastien Besson
118 Johannes Soltwedel
93 William Moore
89 Jonas Windhager
63 Norman Rzepka
36 Constantin Pape
28 Juan Nunez-Iglesias
25 John Bogovic
25 Matt McCormick
22 David Stansby
15 Yaroslav Halchenko
13 Melissa Linkert
7 Virginia Scarlett
6 giovp
5 Jean-Marie Burel
4 Wouter-Michiel Vierdag
3 Matthew McCormick
3 Tommaso Comparin
2 Chris Barnes
2 Davis Vann Bennett
2 Guillaume Gay
2 Jan Eglinger
2 Kevin Yamauchi
2 Tiago Lubiana
2 bugraoezdemir
1 Alan Watson
1 Draga Doncila Pop
1 Dženan Zukić
1 Giovanni Palla
1 Isaac Virshup
1 Joel Lüthi
1 JulianHn
1 Matthew Hartley
1 Sricharan Reddy Varra
1 Tom Boissonnet
1 Virginie
1 Xiao Gui
1 huxfo013
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Zenodo record at https://zenodo.org/records/14755802 and compare its author metadata with the git shortlog shown in the issue. Check whether the repository contains release or publication metadata and review how a git mailmap could affect future records. Done means the existing names are corrected and a documented, repeatable future process is agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100