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

OSS License compatibility question #379

Open
Ashley123456789 opened this issue Jan 29, 2023 · 1 comment
Open

OSS License compatibility question #379

Ashley123456789 opened this issue Jan 29, 2023 · 1 comment

Comments

@Ashley123456789
Copy link

There’s possible confusion on the license of your repository when you combine other open-source code.

The modules opennre/tokenization/word_piece_tokenizer.py, opennre/tokenization/word_tokenizer.py, opennre/tokenization/basic_tokenizer.py, and opennre/tokenization/bert_tokenizer.py claim their licenses as Apache-2.0.
However, the license of your whole project is shown as the MIT license in LICENSE, i.e., less strict than Apache-2.0 on license terms, which may impact the whole license compatibility in your repository, thus confusing subsequent users and bringing possible legal and financial risks.

If possible, you can fix them in one of the following ways:

  • select another proper license for your repository, e.g., Apache-2.0
  • update this license with term exceptions added for specific modules
  • remove these modules if they are not actually useful
@naoki623
Copy link

naoki623 commented Jan 29, 2023 via email

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

2 participants