-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PyGMT authorship policy for Changelog, Zenodo and Publications #691
Comments
The policy sounds good to me. Let's hear more voices from @GenericMappingTools/python @GenericMappingTools/python-contributors |
Just to add a little bit of background, the reason for that policy was to create a clear document we can point to as both an incentive for new contributors and to avoid toxic discussions that can arise about authorship. Our goal was to be as inclusive as possible and very generous with respect to credit. The policy does that with a 3 tier system: changelog, Zenodo, paper. Each has more "prestige" than the previous and so we can also expect more effort from people. To get into the changelog, you only need to make a PR. To go into Zenodo, you need to edit the Authors file as well. To get into the paper, you need to read/revise the paper and add yourself as author on top of the previous requirements. |
I just opened a PR (#726) to push it forward. |
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):
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:
@
handle (at the very minimum) or your full name in our changelog for a particular versionAnd just to link to a few useful references from #677 (comment)_:
Are you willing to help implement and maintain this feature? Yes
The text was updated successfully, but these errors were encountered: