-
Notifications
You must be signed in to change notification settings - Fork 9
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 inconsistencies and future #10
Comments
Following the issue... I've been looking to the mailing list archives and found a part of the answer, quoting Jost Boekmeier reply from 2007: *But I prefer to keep the .java files
Going for MIT ? |
Even a more complete thread: https://sourceforge.net/p/php-java-bridge/mailman/message/22988622/ Especially this one:
So it looks good for me to MIT license the src (.java) code. The "./unsupported" directory containing various libs (Birt...) will be removed soon. |
@cplerch Can I have your idea on this ? |
MIT licenced where applicable |
Reopened because of two files:
|
launcher.c had been moved to legacy folder, see #16 ... |
Note about Apache License V2 and the Base64EncodingOutputBuffer.java... Instead a dual licensing, it's possible to move to Apache V2 - http://apache.org/legal/resolved.html#category-a. Apache v2 can contain MIT (the opossite not true). |
The original project seems to be dual licensed (MIT/LGPL) as stated on the sourceforge page:
The original CVS repo contains reference to the GPL (in the file COPYING) which I believe was let in the repo but seems not to reflect authors updated views... see the website ((LGPL/MIT) or comments in sources or the website:
With an exception of the file Base64EncodingOutputBuffer.java which refers to Apache License 2.0.
Not a lawyer, but I guess being clear on that is important. So keeping a LICENSE.md with either the the LGPLv2 or MIT (keeping copyright to Jost Boekemeier) should be included in the project.
Anyone on this ?
PS: see also https://en.wikipedia.org/wiki/Comparison_of_free_and_open-source_software_licenses
The text was updated successfully, but these errors were encountered: