Skip to content
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 license as BSD 3-Clause License #285

Merged
merged 1 commit into from
Dec 28, 2024
Merged

Conversation

justinmayer
Copy link
Collaborator

@justinmayer justinmayer commented Jun 20, 2024

I followed the process for adding a license to an existing repository, and then I copied and pasted the license that GitHub generates for the BSD 3-Clause License type into the existing LICENSE file.

Other than the removal of the "All rights reserved" line, the rest should mostly be formatting changes.

Resolves #284

Copy link
Owner

@Teemu Teemu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry to be pedantic but this includes changes that are not just formatting.

"IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE" turns into "IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE"

@justinmayer
Copy link
Collaborator Author

justinmayer commented Jun 20, 2024

No need to be sorry — I don’t think you are being pedantic.

But now it is my turn to actually be pedantic: I said that the rest should mostly be formatting changes. 😉

I am aware of this other, very minor addition. An addition that was not made by me, mind you — all the changes here were entirely copy-pasted from GitHub's license generation tool, as noted in the PR description.

Moreover, the text in this PR is exactly — verbatim — what appears in the BSD 3-Clause License. If we do not use the exact same language, then it is not really the same license, which relates to the issue @mociepka originally raised.

Finally, wouldn’t we want to extend the same release from liability to folks who graciously volunteer to contribute to the project?

@justinmayer
Copy link
Collaborator Author

Hey Teemu. Is it okay if we proceed and merge this PR?

@auvipy auvipy merged commit 69989eb into main Dec 28, 2024
8 checks passed
@auvipy auvipy deleted the bsd-3-clause-license branch December 28, 2024 10:27
@auvipy
Copy link
Collaborator

auvipy commented Dec 28, 2024

Merging the change as it reflects the current maintainers/contributors as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarify open-source license type
3 participants