Markus Kühn wrote:
Easy, easy!
I said in general, not specific, that code does not need to include
GPL-code to create - let's be more specific - a license violation.
Or in other words, an ASF project should not actively support (e. g. by
API) GPL-covered code.
If none of it involves your plans, that is fine. And if you are 100 %
sure what you are doing won't create problems, even better; so you only
have to convince ASF-members.
Markus
I'm ok with that. I just wanted to be sure you were speaking in general
and not about this specific contribution.
I'm not 100% sure: in fact you can NEVER been 100% sure that any code
submitted, even if the submitter grant you the rights, even if he added
the license, even if he send you a signed fax granting you the rights,
that he has the full trasferrable copyrights for the code he submit.
This is not an issue with GPL itself: this is an issue with *every*
commit made.
If tomorrow I steal some code somewhere and I commit it to the apache
repository you cannot find out this so easily and, even if Apache
Foundation can sue me for this, this will not protect the project from
the copyright law.
Opensource is an hard world, it's easier "to steal" when you hide your
sources and you can show to the world only your binary side ;-)
Turning back to our issue: the contribution is about the support of a
SUN API, that we already have dependencies on (javamail), and the fact
that the submitter is testing this code against a GPL implementation of
that code does not activate the virality of the GPL.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
