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 clarification #27

Open
penguinpee opened this issue Jan 4, 2024 · 2 comments
Open

License clarification #27

penguinpee opened this issue Jan 4, 2024 · 2 comments

Comments

@penguinpee
Copy link

I stumbled upon pyuca as a dependency of version 6.0.0a3 (pre-release) of Spyder. I'm one of the maintainers of Spyder in Fedora.

While submitting pyuca as a new package for Fedora, the Unicode license(s) came up. The text in LICENSE-allkeys doesn't currently match any of the allowed Unicode license as defined in SPDX (search for Unicode) close enough.

The newest version of the license, Unicode-3.0, that has just been added, is not yet on the list mentioned above. However, that version of the license text is no close enough match either, but it comes closest to the current text.

Would it be possible to update LICENSE-allkeys to include the text of that license?

Then there is the question which licenses the older allkeys*.txt files refer to. The preambles differ per file. Going by the dates in the headers, they all refer to different versions of the Unicode license as it evolved over time. Unless, however, the newer license version supersedes older versions. I'm trying to get clarification on that from other sources as well as it would simplify the possible solution, e.g. one Unicode license file vs. several.

I'm aware this project is kinda hibernating. However, without clarification, pyuca cannot be included in official Fedora repositories and that might be the end of Spyder, a much loved IDE, in Fedora. I'd appreciate any response. I'd also be willing to submit a PR once the license question has been clarified.

@jtauber
Copy link
Owner

jtauber commented Jan 24, 2024

pyuca is only really hibernating in as much as the last release still does everything I need it to do. Updating to later versions of Unicode might be worth doing, though.

I certainly would welcome a PR on the licensing issues.

@penguinpee
Copy link
Author

Thank you! I'll look into it and consult with legal folks to get this right. Expect a PR soon(ish).

penguinpee added a commit to penguinpee/pyuca that referenced this issue Feb 23, 2024
- Include current text of Unicode-3.0 license
- Explain applicable licenses in COPYING
- Solves issue jtauber#27
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