Policy regarding external / other licensed code?
Mark Wielaard
mark at klomp.org
Mon Jul 4 00:22:47 PDT 2011
Hi Clemens,
On Sun, July 3, 2011 22:56, Clemens Eisserer wrote:
> 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
>
> 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?
I tried to bring this up a couple of times, as there are some
external code bases in the repositories, but it is unclear how
new external code bases can be added. But as far as I know there
never has been a resolution to this issue. If you are blocked while
this is being resolved please feel free to request a repository
on icedtea.classpath.org. As long as what you want to hack on
is free software it can be hosted there for now. All the above
seems just fine.
Cheers,
Mark
More information about the caciocavallo-dev
mailing list