On 27 November 2013 at 08:34, Alan G Isaac wrote: | On 11/27/2013 7:58 AM, Luca Beltrame wrote: | > I'd prefer strong licenses like the LGPL or the GPL (but I'm an | > academic), regardless of which is more "comfortable" for a given community. | | I am also an academic. I think the implications of my | word "comfortable" have been misunderstood. What is | "comfortable" to a community determines usage patterns. | Presumably, all else equal, more people using your code | is a good thing. For one thing, over time it results | in more code contributions. I think a look at the Python | scientific community (for example, the re-licensing of | Matplotlib as BSD) will show you what I'm talking about.
I am aware of similar recent discussions between the Python side (ie Wes and pandas) and the R side (ie Hadley) with respect to dplyr and reuse of common code for transformation. It is a no-starter as far as we can see, for exactly the reasons given by Laurent: a "tight coupling" of RPy2 with R itself, both an run-time (linking) and compile time (headers). And for what it is worth, I do the same for my projects: "GPL (>= 2)". I like the GPL. It means I am assured that noone is profiting from my work without sharing (code) back. That the GPL is viral is still a feature and not a bug. Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com ------------------------------------------------------------------------------ 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
