On Fri, 20 Mar 2009 06:08:28 -0500 DRC <dcomman...@users.sourceforge.net> wrote:
> But I am correct in my assertion that GPL v3 code cannot be used by GPL > v2 projects? Yes, unless they also upgrade. > That seems to be cutting off the hand that fed us, in a > way. There are a lot of GPL v2 projects that currently take advantage > of the TightVNC extensions, and we want those projects to likewise be > able to take advantage of our codec. I'm not as much concerned about > TurboVNC specifically as the notion in general that other projects that > currently use the Tight encoder will be stuck. > I think we should primarily strive for good, well documented protocols more than having people copying code. As part of that we should minimise the use of tight's custom extension system and work more in line with the regular RFB protocol. And in reality, how many projects can actually take our code? The code isn't exactly general, so I would assume it's primarily any other direct forks of TightVNC that could use it. And IMO we should work to merge any such forks into TigerVNC. Rgds -- Pierre Ossman OpenSource-based Thin Client Technology System Developer Telephone: +46-13-21 46 00 Cendio AB Web: http://www.cendio.com
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ 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
