Re: Policy regarding external / other licensed code?

[neugens.limasoftware@gmail.com]

We cannot have any external dependency that did not sign the OCA in the main repository.

We can, however, host a secondary repository with the code upon which Cacio depends, and explicitly state the various licenses.

I don't know if this repository can reside side by side with cacio, be a sub repo of it, or even just a separate source tree, I think that as soon as:

1. The license is compatible and clear for each source file
2. Files are completely separate from the main line

There is no problem, but we need to ask Oracle if we can use their infrastructures or we need an external repo for this.

In general we need to follow the GB rules.

Can you please prepare a mail for Mark and Dalibor, we review it when I'm back tomorrow and we solve this? I think is less of an issue as we think, but better to be on the safe side.

Cheers,
Mario
-- 
Sent from HTC Desire...

pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF
Fingerprint: BA39 9666 94EC 8B73 27FA  FC7C 4086 63E3 80F2 40CF

http://www.icedrobot.org

Proud GNU Classpath developer: http://www.classpath.org/
Read About us at: http://planet.classpath.org
OpenJDK: http://openjdk.java.net/projects/caciocavallo/

Please, support open standards:
http://endsoftpatents.org/


----- Reply message -----
Da: "Clemens Eisserer" <linuxhippy at gmail.com>
Data: dom, lug 3, 2011 22:56
Oggetto: Policy regarding external / other licensed code?
A: <caciocavallo-dev at openjdk.java.net>

Hi,

The current cacio-web implementation uses quite a bit of external code:
- Some keyboard-handling code from noVNC (with the permission of the
author, licensed as LGPL)
- Base64 encoder (licensed as BSD, LGPL, ...)
- PngEncoder - LGPL

The Base64 encoder was slightly modified, as some browsers had
problems with the encoding it used.
The PngEncoder is a generic png encoder, much faster than what is
provided by ImageIO.

The keyboard-handling code is really tightly integrated with the
current code (which is quite a bit of a mess anyway), but it should be
possible to factor it out - at least into its own independent
JavaScript file.

What is the current policy regarding such external code?
As far as I've seen external libraries code is not included in the
mercurial tree, however what should I do in this case?

Thanks, Clemens
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/caciocavallo-dev/attachments/20110703/9309980d/attachment.html