On 27 November 2013 12:09, Alex Mandel <tech_...@wildintellect.com> wrote:
> FYI, if changes are required to rmagic from the rpy2 side, just
> contribute it directly to rmagic and pull a new copy back to rpy2 no
> license change required.
>
We'll probably drop rmagic from IPython once it's in a released version of
rpy2, so it's not a big concern. I just mentioned it as an example of how
code moves between related projects. Using a more permissive license makes
that kind of movement among Python projects easier.
So I'd be +1 to changing the main license of rpy2 from AGPL to GPL, and
also +1 to dual licensing with a BSD style license (or +0.5 to dual
licensing with LGPL).
Thomas
------------------------------------------------------------------------------
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
