-
Notifications
You must be signed in to change notification settings - Fork 225
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
Take co-authoring contributions into consideration #3746
Comments
Thanks, @seisman, for writing up this issue! I remember I recognized the difference between I agree on considering co-authorship as it is fair to acknowledge any kind of review (bringing up or participation in discussions, providing ideas, but also guidance during working on more complicated tasks / learning to work on new tasks). The number of additions and deletions may partly help to consider the different work loads of PRs. However, I am unsure, if it is possible to change the rules for the author order now, and if we have to contact and ask all (at least the affected) authors for their opinions or being OK with this? In case we keep |
Using
Then, for the authorship of Zenodo releases, the order should be (based on the counts only):
For comparison, the current author order of the latest release is: Lines 141 to 158 in b46274b
Leo was promoted for his early work on the project; Liam and JingHui were promoted for their works on the workshops/talks.
It seems only Michael and Will are affected. |
BTW, in the authorship guides, we already mentioned that reviewing PRs should be taken into considerations: Line 51 in b46274b
|
Continue discussions in #3730 (comment).
Currently, we use the
git shortlog -sne
command to count author contributions. Below is a trimmed output on 2025/01/05:The GitHub contributors page (https://github.com/GenericMappingTools/pygmt/graphs/contributors) shows totally different numbers of commits, likely because GitHub also considers co-authorship. I feel these numbers (including the number of additions and deletions) make more sense.
To consider co-authorship, we can use the following command:
The output is:
After merging the commits from the same author but with different git commit author names or emails, the numbers are the same as those of GitHub.
Currently, we count the contributions (using
git shortlog -sne
) in the following places (xref: https://github.com/GenericMappingTools/pygmt/blob/main/AUTHORSHIP.md):I think in all these cases, the co-authorship contributions should be considered.
The text was updated successfully, but these errors were encountered: