[X2Go-Dev] [pkg-x2go-devel] Bug#784565: Bug#784565: nx-libs-lite: parts are derived from non-free code

Kevin Vigor kevin at vigor.nu
Mon May 18 23:11:42 CEST 2015


By the way, poking around the interwebs I find there is an archive of the old DXPC mailing list available at:

http://marc.info/?l=dxpc&r=1&w=2

I think you will find this of particular interest:


http://marc.info/?l=dxpc&m=93093790813555&w=2


List:       dxpc
Subject:    Re: future tecnologies
From:       Brian Pane <brianp () cnet ! com>
Date:       1999-07-02 16:42:18
[Download message RAW]

Kevin Vigor <kvigor at eng.ascend.com> wrote:
> On 01-Jul-99 dxpc at mcfeeley.cc.utexas.edu wrote:
> > Speaking of licensing, are you putting your 3.8.0 changes to the dxpc
> > code itself under GPL, or are they going to use the original dxpc's
> > licensing?
>
> No, as you can probably guess, I am no fan of the GPL. For stuff on
> this level, where my hacking is pretty simple and probably devoid of
> commercial value, I'll just release my changes to the public domain and
> give up even a copyright interest in them.
>
> Your and Zach's copyrights still stand, of course.
>
> I *think* that fact that we use the LZO library and API, but do not
> directly incorporate the code, allows us to escape the clutch of the GPL
> virus.
>
> btw, is there an original dxpc license? I haven't seen anything but a
> copyright notice, which to my non-lawyerly mind translates as "free to
> all the world as is, negotiate with copyright owner if modifying or
> including in some other product".

The copyright banner in the Readme is all the documentation there's ever
been.  My intent was to allow _any_ distribution, use, and modification
of the source, without imposing restrictions on the licensing style of
any system into which others might incorporate the code.  We probably
should start stating this clearly in the distributions.

-brian

[prev in list] [next in list] [prev in thread] [next in thread]


More information about the x2go-dev mailing list