What good is VNC's GPL?
angelosarto "at" gmail.com
Tue Apr 5 13:39:01 2005
I will not comment at this point about the merits of this either way.
However, if this matter is a violation then the orginazation that initates
the action has to be the copyright holder whos licensing is being violated
In this case this would be the tightvnc group, who can choose to ask the FSF
for help if necessary. Source:
The gpl is benneficial for end users, however its main objective is to
protect the development community that created "the work" in copyright
I wish all parties luck in resolving this.
On Apr 4, 2005 10:34 PM, Bob Smith <sendjunkmailshere "at" gmail.com> wrote:
> So, since they refuse to release it despite all of this, who is to
> enforce it? The last word that I have from Yury is that we will never
> see the source code. I'm not out to get him at all! I do think that
> he is being a bit shady here, though.
> I would steer clear of his vnc products if I where you, though. Who
> knows what other unethical coding is going on in there? Look at what
> happened to all of the SCO users! I wouldn't subject my company to
> that sort of uncertainty after seeing how this issue has been treated
> by the owner of Smart Code.
> I can't even find a physical address on their website. Does the
> company even exist as an entity outside of the web?? Where do they
> operate out of?
> On Apr 4, 2005 3:35 PM, Kyle McDonald <Kyle.McDonald "at" sun.com> wrote:
> > Yury Averkiev wrote:
> > > So called "Bob Smith" you have been told already that the control is a
> > > (set of hooks around TightVNC files) - so it doesn't violetes GPL.
> > Is the tightVNC (or other GPL) code linked together in the same
> > DLL with your new 'wrapper' code??
> > Did you have to edit any tightVNC (or other GPL) code to create a
> > DLL version of tightVNC?
> > If the answer to either of these questions is 'yes' then I'm sorry
> > to inform you that your product *does* violate the GPL.
> > If your code is in a seperate DLL from the the tightVNC (and other
> > GPL) code, then you *might* (I'm not lawyer ;) ) have an argument.
> > I think that would still require you to release any and all edits
> > you made to any tightVNC and other GPL source code files while you
> > were turning it into a DLL. (Does TightVNC provide a DLL already?)
> > Note: you actually need to release all the changed tightvnc files,
> > diffs and patches aren't enough - at least the last time I checked.
> > Also even to release your product in that fashion, tightVNC (and
> > the other code it includes) might (I'm not sure) actually need to
> > be licensed under the LGPL not the GPL by the copyright holder to
> > the public, and I doubt any of the VNC code has ever been licensed
> > with the LGPL.
> > There are alot of people in this world who like the GPL very much,
> > many beleive in it like a religion, and are very vehement in it's
> > enforcement. These people take alot of stands based just on the
> > principal of the thing. Many can be very vocal. I wouldn't assume
> > that someone who asks these questions is anyone in particular, or
> > is out to get you.
> > Complying with the GPL tends to get you much better press and
> > relations than thumbing your nose at it. That will get you a huge
> > amount of really *bad* press.
> > Personally I think the GPL has problems, I wouldn't use it on code
> > I invent, and I can't stand the way Richard Stallman (the author
> > of the GPL) thinks or speaks. But I personally am for all the
> > rules and licenses to be obeyed and enforced.
> > So I'm interested in the answers to those 2 questions (and then I
> > may have more) and I'm interested to see how this whole thing
> > turns out.
> > -Kyle
> > --
> > _
> > -------------------------ooO( )Ooo--------------------------------
> > Kyle J. McDonald (o o) Systems Support Engineer
> > Sun Microsystems Inc. ||||| Kyle.McDonald "at" Sun.COM
> > 1 Network Drive \\\// voice: (781) 442-2184
> > Burlington, MA 01803 (o o) fax: (781) 442-1542
> > --------------------------------ooO(_)Ooo-------------------------
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit: