-
Notifications
You must be signed in to change notification settings - Fork 3
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 needed #24
Comments
It looks like the Was that intentional? |
Thank you for catching that. It looks like my snippet for inserting the license language in the code reverted to a backup. The correct License is GNU Lesser General Public License v3.0 (LGPLv3). I'll update all the individual files. Best, |
Thanks. I will apply the patch when it's ready. But maybe this warrants a new release on PyPI? Either way, thank you for clarifying. |
Addressed by PR#27. Will be in 0.1.1 release. |
Thanks for fixing that. 👍 Are you planning on releasing 0.1.1 soon? If so, I wait. Otherwise, I'll grab the patch. |
Yup, looking to release before the end of the weekend. I just have to run tests over my corpus of test emails with all the changes in place to make sure I didn't break anything. |
Excellent! Well, have a good weekend then. ;) |
Addressed in Release 0.1.1 |
The license referenced in the
LICENSE
file is for LGPL-3.0-only (LGPLv3). However the preambles in the python files inRTFDE/
as well as files indocs/RTFDE/
andscripts/
state the applicable license as GPL-3.0-or-later.It appears the latter is the effective license. If so, could the
LICENSE
file as well assetup.py
be updated to reflect the actual license that applies to the code?I can supply a PR to that extent once it is clear which license applies to the code. The issue came to light during package review. I would like to package
RTFDE
for Fedora.The text was updated successfully, but these errors were encountered: