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

License unification #62

Merged
merged 3 commits into from
May 20, 2024
Merged

License unification #62

merged 3 commits into from
May 20, 2024

Conversation

julianstirling
Copy link
Collaborator

Unifying the project to one license to avoid the confusion of multiple-probably incompatible licenses.

Removing SPDX copyright header as these are always out of date as new people add to the code. Git BLAME is a more reliable way to see who contributed to a file and when.

@julianstirling julianstirling marked this pull request as ready for review May 20, 2024 09:03
@drayde
Copy link
Contributor

drayde commented May 20, 2024

okh.toml was created by Robin and CC0.
Can we simply remove the license info on that file?

@julianstirling
Copy link
Collaborator Author

CC0 and unlicense are both public domain so can be use in other code under other licenses. In theory just relicensing the CC0 to CERN-OHL-S is a bit rude, but as soon as we modify it then we are 100% free to be doing so under our license, and it is out of date so we will be modifying it very soon. The other one of Robin's public domain files is already heavily modified by me.

Copy link
Contributor

@drayde drayde left a comment

Choose a reason for hiding this comment

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

Ok, thanks for the clarification 👍

@julianstirling julianstirling merged commit 83f355c into master May 20, 2024
4 checks passed
@jmwright
Copy link
Contributor

I realize that the LICENSES directory had several licenses in it. However, I and others use a LICENSES directory for hardware projects because there is no single license that properly covers documentation, hardware, and software. So you end up with three licenses for the project, with a clarification in the README.

Example LICENSES directory

Mention of multiple licenses in the readme (scroll down to bottom of the readme for the licenses section)

People also seem to be passionate about licenses, and license changes can be contentious.

@julianstirling julianstirling mentioned this pull request May 20, 2024
@julianstirling
Copy link
Collaborator Author

Thanks @jmwright I have moved this to an open issue as I don't want this important discussion to get lost in a closed PR See #63

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.

3 participants