-
Notifications
You must be signed in to change notification settings - Fork 389
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!? #25
Comments
Yes, MIT license is prefered. |
Is the license supposed to be just a copy of the OCRad's license: https://github.com/antimatter15/ocrad.js/blob/master/ocrad-0.24/COPYING ? I just realized that is GPL2. If that is the case, may be we just need to have a separate project as a port of Tesseract and deal with it. (I did see the note about your attempt for porting Tesseract by the way). |
+1 for the license update. But since OCrad is GPLv2, that means this ocrad.js could be GPLv2 as well. AFAIK, GPLv2 is a bit more permissive than GPLv3 with regards to original work -- especially for Web applications. If that is correct, I would suggest changing ocrad.js to GPLv2. |
Can't use this for my commercial project :( |
You can, GPL doesn't stop you from taking payments. Write your own OCR if your commercial project cannot be open source (or use tesseract which has a more permissive license) |
Hi!!
GPL license for a client side javascript application? Oh that's so sad. What that means is that, for commercial proprietary software developers, this wouldn't be of any help, as they wont be able to use it, at all! This seriously diminishes the potential of the application to reach a wide range of people!
Why not BSD or MIT, or Apache 2.0 perhaps??! ( Tesseract is under Apache 2.0 )
The text was updated successfully, but these errors were encountered: