-
Notifications
You must be signed in to change notification settings - Fork 19
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
SvmHmm is not under Apache License #493
Comments
That shouldn't be an issue in this case because we do not really link to the code - we only call it. TreeTagger is also not license in an ASL-compatible way, but still the DKPro Core TreeTagger module is ASL. It only contains wrapper code which calls the external binary. The binary is not directly included in the module either. |
If we package pre-compiled binaries of svmhmm and distribute them, a permission from Thorsten Joachims would be required. Do we have that? If it is there, it should probably be in some README file in the module or in the binaries artifact (or both). |
We call the pre-compiled binaries via our wrapper code. The binaries are provided in Maven artifacts. I guess this would require an explicit permission then? But this line is counter-intuitive for ASL, isn't ? |
As far as I can see, the SVMHMM license is not reciprocal (like GPL), thus it does not enforce a particular license on the calling code. Even if it were GPL, because we call it as an external process, the reciprocal terms shouldn't not trigger. So the DKPro TC code is not affected by the license. According to the license terms, for the redistribution of the pre-compiled binaries via Maven artifacts, a permission from the author would be required, yes. And in fact, we have that permission: https://github.com/dkpro/dkpro-tc/blob/master/dkpro-tc-ml-svmhmm/src/main/scripts/LICENSE.txt The user of the module is affected by the SVMHMM license as it cannot be used in particular cases without permission of the author. For this reason, the DKPro TC website says:
So - IMHO we are all good here. |
Ah, good :D - I think I will leave this issue open as 'won't fix' as a reminder. This is not as clearly visible as it should be. |
Using SvmHmm for commerical purposes is at the moment not possible. This probably requires permission on a case-to-case basis by the author of SvmHmm. |
The license of SvmHmm is not Apache compatible but currently a 'Apache' project in TC.
The text was updated successfully, but these errors were encountered: