On Mon, Feb 7, 2011 at 16:14, Marc-André Moreau <marcandre.mor...@gmail.com> wrote: >> Personally I as a minor contributor is fine with relicensing my >> contributions under other open source licenses. FWIW I would prefer a >> license that allowed integration in non-GPL projects but required all >> changes to FreeRDP code itself to be given back to open source. I guess >> that would mean LGPL. > > Yes... LGPL allows people to use the library without the viral effect, but > code within the library suffers from the same viral effect as the GPL. I > want to get rid of the chilling effect.
I don't. That is my main concern about Apache/MIT or BSD like license. >> However, IANAL, but I am convinced that we can't legally change the >> license to anything but GPL without getting explicit permission from >> everybody who has ever contributed to rdesktop or FreeRDP. People own >> the copyright to their changes even if they not are listed as copyright >> holders in the file. GPL is viral and also applies to derived products, >> so even original code that we have written in a GPL context might be >> tied to the GPL license. Changing every line manually or rewriting the >> code piece by piece doesn't necessarily prevent it from being derived >> code. >> > We will also need to ask people from rdesktop. I think Jay has compiled a > list of contributors from rdesktop that we should contact. Worst case > scenario is that we need to rewrite the code from people who disagree with a > license change. One reason why I put resources at O.S. Systems to work at FreeRDP is because we gain with sharing code with the project. If we don't have the enforcement of sharing the code we will gain not making the code public (that is worse for us and for the project). >> GPL rdesktop code is already on app store. FWIW. > > GPL in the app store is in the "gray zone" right now. Apple will accept > them, but if someone files a complaint such as in the case of VLC, Apple > will simply remove the app. Since "app stores" are growing in popularity, I > would expect such cases to grow in number with the years. Gray zones are > never good, they leave a false sense of security but anytime someone might > just pop up and claim it's a violation of the license. Unfortunately, the > people who need to address licensing issues in their "app store" often just > remove the infringing application. I don't use "app stores" and I don't care about them. I prefer the profit for gaining code contribution that having it outside of gray zone. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
