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

Need separate license for Rust code? #1

Closed
sts10 opened this issue Mar 31, 2023 · 1 comment
Closed

Need separate license for Rust code? #1

sts10 opened this issue Mar 31, 2023 · 1 comment

Comments

@sts10
Copy link
Owner

sts10 commented Mar 31, 2023

Currently, this project is licensed under Creative Commons 3.0 Unported. This is solely because that's how Google Ngram data is licensed. I did this because this project, obviously, contains lots of words that originally came from Google Ngram data.

However, this repo/project also contains non-trivial Rust code in it (about 180 lines of code). In my understanding, Creative Commons licenses aren't really made to cover code. For that reason, I think I should license the Rust code of this project under a different license, such as the MIT License or the Blue Oak Model License.

My questions are (1) Whether this is a good idea, and (2) how I might practically go about doing this. For example, should copies of both licenses be in the repo, and explain what work falls under which license in the README? What should I name the two license files?

I'm sure there are examples of this to follow?

@sts10
Copy link
Owner Author

sts10 commented Mar 31, 2023

I slept on this and decided to merge #2 . Still open to comments on this though!

@sts10 sts10 pinned this issue Mar 31, 2023
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

No branches or pull requests

1 participant