-
Notifications
You must be signed in to change notification settings - Fork 74
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
Clarify open-source license type #284
Comments
As one of the maintainers of this project, I agree and hereby second this motion. 👍 While I am normally partial to (A)GPL licenses, in this case I do not have a strong opinion regarding which OSI-compliant license is selected. |
Isn't this a pretty established license? https://opensource.org/license/bsd-3-clause I would have probably chosen MIT if given the choice, but we are pretty much stuck since there are too many contributors to relicense. |
I had no idea the current That said, I think there are some changes I would suggest to improve the current situation:
As to why the "All rights reserved" line was removed from modern versions of the BSD license, and why I think it should be removed from this project's license, please read: https://opensource.stackexchange.com/questions/2121/mit-license-and-all-rights-reserved/4403#4403 @Teemu: Do you have any objections if I make the above change, bringing the project's Update: I took the liberty of submitting a pull request with this change, as seen in the PR link below. |
Could you consider using an established open-source license for this project? Pytest uses the MIT license, which might be a suitable option. With the current license, I am unable to use this project in my work. I understand that the library code will not be used in production directly (as it is a development dependency), but the current licensing still limits users who are bound by company policies that mandate the use of open-source software only.
Thank you for your consideration.
The text was updated successfully, but these errors were encountered: