-
Notifications
You must be signed in to change notification settings - Fork 235
Description
Description of the desired feature
The PyGMT project started by @leouieda in 2017 is gaining quite some traction, and it's time to come up with a good system to assign authorship as we work towards more releases and perhaps a paper (#677) in the future!
Originally raised by @leouieda at #677 (comment):
It's really important that we agree on this before doing any work a paper. See the Fatiando policy which was generated after long discussion and research into similar policies.
Also mentioned at #683 (comment)_
To begin, I think https://github.com/fatiando/contributing/blob/master/AUTHORSHIP.md is a nice starting template to use, and so is the original discussion at fatiando/community#13. The TLDR of it I think is:
- Changelog: If you made a commit as a contributor, we'll mention your Github
@handle (at the very minimum) or your full name in our changelog for a particular version - Zenodo: Your full name must be in AUTHORS.md, (+ Affiliation and ORCID). See also https://doi.org/10.5281/zenodo.3781524.
- Paper: Have made a 'significant' contribution to the PyGMT project (which can be more than just coding) and you are involved in the writing of the manuscript.
And just to link to a few useful references from #677 (comment)_:
- FORCE11 Software Citation Implementation Working Group at https://github.com/force11/force11-sciwg.
- CRediT – Contributor Roles Taxonomy at https://casrai.org/credit/
Are you willing to help implement and maintain this feature? Yes