[Pkg-exppsy-maintainers] Licensing

Christoph T. Weidemann ctw at cogsci.info
Tue Feb 26 01:09:44 UTC 2008


Hi all!

Maybe I'm missing something, but NiPy has some interfaces to GPL'ed
code (at least that's what they claim on the website), so it seems
that there is a way to call GPL'ed code from non-GPL'ed code. It's
easy to think of many examples where GPL'ed software is called from
and interacts with non-GPL'ed software -- I guess it all depends on
the details.

Be that as it may, unless the nipy or scipy folks want to wrap or
incorporate pymvpa (instead of just providing a GPL-compatible
interface to or ignoring pympa), I don't see how choosing the GPL
would slow down the overall development process or otherwise produce
problems.

I don't mean to belabor my preference for the GPL, I'm just genuinely
confused because it seems to me that
(a) we all prefer the GPL,
(b) there's no non-GPL'ed project which wants to incorporate pymvpa or
otherwise would likely run into problems if pymvpa were to switch to
GPL, and
(c) none of the reasons that scipy cite as their rationale for
choosing the MIT license apply to pymvpa.

Anyway, as others have pointed out, we don't have to rush this
decision, and I'm curious to hear what the nipy folks think.

Cheers,
Christoph



More information about the Pkg-exppsy-maintainers mailing list