It seems that this argument has already been hashed out on the LKML as well, with Linus coming down squarely against GPL v3. I'm not saying that that means we shouldn't do it, but in my mind, it raises a large red flag. I don't think the advantages are as cut and dried as the FSF would have us believe. GPL v2 is a well-understood and well-tested license, and I don't think enough projects have adopted GPL v3 yet to be able to fully explore its ramifications. In particular, none of our parent projects (RealVNC, TightVNC, etc.) or similar remote display projects (NX) are using GPL v3. I'm not comfortable putting this project out at the forefront on that.
King InuYasha wrote: > I do not see any real valid reason for moving from the GPLv2+ to > GPLv3+. Generally, switching licenses can cause a lot of problems, it > is even worse for any VNC system in a Linux distro because there are a > lot of apps that use GPLv2 and legally you throw a lot of apps in hot > water. I would strongly suggest that we leave the licensing as-is, and > if anyone wants to use it as GPLv3, they can upgrade to that license > at their prerogative, but leave the main project code under its > current licensing scheme. The Tivoization and the patent deal stuff is > a load of crock (I would use worse, but this is a public mailing list) > and Ourborous of FUD. Tivoization is not really a problem with VNC, > especially since to a certain extent, TigerVNC would really be immune > to such an issue. The patent deal thing is a huge overreaction. And it > is overreactions like these that cause more FUD than Microsoft could > ever produce. > > On Fri, Mar 20, 2009 at 12:15 PM, DRC > <dcomman...@users.sourceforge.net > <mailto:dcomman...@users.sourceforge.net>> wrote: > > The main sections that I'm concerned about are the TightVNC codec > sections, so leaving those as GPL v2 would be a compromise. I still > don't really see any need for GPL v3 on the project as a whole, > though, > and I would vote against it until more of the OSS community is > standardized around GPL v3. > > > Peter Åstrand wrote: > > I agree with what Pierre said in his earlier mail, but I like to add > > that for specific parts, we always have the possibility of making > > exceptions: We could mark specifik files or modules as GPLv2+, while > > upgrading the rest to GPLv3. And of course, for things that we have > > the copyright for, we can grant usage with other licenses, even > > commercial ones. GPLv2 projects can also copy our source code as > it is > > today. > > > > So I believe we should migrate to GPLv3. > > > > Best regards, --- > > Peter Åstrand ThinLinc Chief Developer > > Cendio AB http://www.cendio.com > > Wallenbergs gata 4 > > 583 30 Linköping Phone: +46-13-21 46 00 > > > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex > Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. > Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based > development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Tigervnc-devel mailing list > Tigervnc-devel@lists.sourceforge.net > <mailto:Tigervnc-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/tigervnc-devel > > ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
