Add authorship policy #726
Conversation
|
"We aim to write academic papers for most of your software packages" Shouldn't that be "most of our software packages" instead? |
Co-authored-by: Wei Ji <[email protected]>
seisman
added
good first issue
|
@GenericMappingTools/python In preparation for the v0.3 release, is the plan to have @leouieda as first author and @PaulWessel as last author, and then all of the contributors listed on AUTHORS.md in the order of numbers of commits? That makes the most sense to me, but I also don't feel strongly about a particular order. |
I think that's the best way to handle the order @willschlitzer since in most scientific papers the order represents some kind of "workload" 😅. |
Number of commits isn't perfect, but as long as we communicate about this in good faith, I think we'll be ok. Specifically would like to mention Liam's work on the ROSES and upcoming Scipy2021 stuff which is super valuable but not tracked on git. So this metric should serve as a rough guideline and not be set in stone. |
* Get a copy of the authorship policy from https://github.com/fatiando/contributing * Change the project name to PyGMT * Update AUTHORSHIP.md * Update contribution explanations Co-authored-by: Wei Ji <[email protected]> Co-authored-by: Will Schlitzer <[email protected]>
Description of proposed changes
The aurthorship policy is copied from https://github.com/fatiando/contributing/blob/master/AUTHORSHIP.md, with tiny changes.
Fixes #691
Reminders
make formatandmake checkto make sure the code follows the style guide.doc/api/index.rst.Notes
/formatin the first line of a comment to lint the code automatically