-
Notifications
You must be signed in to change notification settings - Fork 224
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
Distinguish PyGMT Team, Developers and Contributors #3375
Comments
I agree regarding the "copyright holder".
I agree, that "Contributors" is more sutible and fair here (https://github.com/GenericMappingTools/pygmt/blob/main/AUTHORSHIP.md#the-authorsmd-file).
Sounds good to me. |
From reading https://softwareengineering.stackexchange.com/questions/308909/how-to-manage-copyright-notices-from-contributors-to-a-bsd-licensed-project, I'm not sure if it's that straightforward to re-assign copyright to the just the PyGMT Team. Legally speaking, old versions of PyGMT (up to v0.12.0) would still be copy-rightable by 'PyGMT Developers'. We don't have a Contributor License Agreement (CLA) in place either (nor do I really fancy adding one), so I think we might be stuck with PyGMT developers here unless we 1) ask everyone on the list if they're ok with reassigning copyright for new PyGMT versions (v0.13.0 and newer) and 2) enforce a CLA going forward so that contributors would assign copyright to the PyGMT team. See also https://dev.to/oborys/complete-guide-to-open-source-licenses-for-developers-3j5e#about-changing-the-license
Project authorship should still be based on names in AUTHORS.md (which is used on Zenodo). I don't think that should be restricted to just PyGMT team.
See above note on 'PyGMT Developers' being copyright holder. We might need to keep it as 'Developers'
Yep, sounds good. |
Btw, the title says 'Project Contributors', not 'PyGMT Contributors', which is just a generic term so I don't think that is too confusing. The sentence below the title uses 'PyGMT Developers'. |
https://opensource.guide/legal/#what-if-i-want-to-change-the-license-of-my-project I think @weiji14 is right that changing the copyright holder requires agreement from all current contributors, which is a complicated thing that I never want to do. So let's keep using "PyGMT Developers" everywhere. |
Currently, we have three different terms about people who make contributions to PyGMT:
AUTHORS.md
file.LICENSE.txt
file, and the project metadata keyauthors
inpyproject.toml
. Refer to https://github.com/search?q=repo%3AGenericMappingTools%2Fpygmt+%22PyGMT+Developers%22&type=code for a more complete search.Looking at the git history, the term "PyGMT Contributors" was added in 2017 (#56), then "PyGMT Developers" in 2019 (#284), and finally "PyGMT Team" in 2021 (#1308).
Personally, I feel it's weird to assign the copyright holder and project authorship to "PyGMT Developers" who perhaps only make a PR fixing a typo. So I propose:
AUTHORS.md
AUTHORS.md
and vice versaPing @GenericMappingTools/pygmt-maintainers for comments
The text was updated successfully, but these errors were encountered: