On 11/26/2013 11:35 PM, Nathaniel Smith wrote: > I believe R is dual licensed GPLv2 and GPLv3. So it is > legally possible to take the GPLv3 option and then license > rpy2 as AGPLv3, because GPLv3 has an > exception to make it compatible with AGPLv3. But just > releasing rpy2 with the same (dual) license as R seems > simpler
What is the R License? http://cran.r-project.org/doc/FAQ/R-FAQ.html#Legalese How Permissive? This conversation started asking about the LGPL (more permissive) and has moved to talking about the AGPL (less permissive). That suggests that the licensing goals are not very clear. For a project like RPy, adding restrictions is unlikely to prove beneficial. And it would be more than odd for the license to be more restrictive than R's license. On this basis, one would say GPL 2 is the least permissive license RPy should consider. (Although naturally license choice is up to whoever produces the code.) Is RPy a Derivative Work? Ask a lawyer, but probably not. In my opinion, the LGPL (or even BSD) is available as a choice, if the project wants it. Personally, I would encourage BSD as most likely to generate code contributions for this project. It is also most comfortable for the Python scientific computing community, in my view. Cheers, Alan Isaac ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ rpy-list mailing list rpy-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rpy-list
