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 https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
