|
Sort Order:
[
Permalink
| « Hide
]
marc antoine garrigue added a comment - 23/Sep/05 06:42 PM
update license, will move package lateer
Marc,
I cannot find any discussion as to why this was done on the mailing list, Confluence or JIRA - just this single issue. I can only advise that it is a _bad idea_. Open Source licensing is a tricky area to start with, but the GPL is the death of a Java infrastructure project - especially one like JCaptcha. Why? Simply put, we cannot use it. Confluence is using RC2.0.1, we looked at upgrading to 1.0-RC3 but we can't. We must now seek other ways to do captcha as there is no longer an upgrade path from the LGPL version we're using (1.0-RC2.0.1). Any other company will feel the same way, even extremely Open Source friendly ones like us. GPL is simply to be avoided, BSD is good, LGPL is fine (we just need to be careful to contribute any patches we might make, but that's not a problem). Can you give me any guidance as to why this decision was made and how likely it is that will be reversed? (if indeed that is legally possible? Who owns the copyright for all the code in JCaptcha? Have you got assignments from all the contributors?) Cheers, Mike Hi Mike,
>I cannot find any discussion as to why this was done on the mailing list, Confluence or JIRA - just this single issue. We had this discussion with the team in private, originaly because of the LGPL-apache compatibility issues. We also like very much the GPL 3. >Can you give me any guidance as to why this decision was made and how likely it is that will be reversed? Many other open source project report me the same concern. I assume this was a bad choice. We will have another round table with the team about it. Rollback!
We decided to move back to LGPL. |
||||||||||||||||||||||||||||||||||
Task
Resolved
Critical
Move to GPL