[Insight-developers] [ITK Community] Remote modules License

[Brian Helba]

Hi all,

Part B of the license in question (
http://www.rad.upenn.edu/sbia/software/license.html ) is what applies to
taking their code and using it as part of an ITK remote module. It appears
at first glance to be a permissive open-source license, but I think someone
certainly needs to examine a diff between it and Apache 2.0.

I'm wondering about a possible complication from Part A, which is a
contributor license agreement (CLA) for contributing code back upstream. If
improvements to the library in question are made by ITK, it would be best
if those could be easily contributed back upstream; if we can't do this,
then the library gets forked and it's much more difficult to incorporate
updated versions from upstream. From the text of Part A, it looks as though
any of ITK's modifications, being Apache 2.0 is enough per se to meet the
requirements of their CLA. However, if their CLA requires an individual to
sign any documents (it doesn't appear to) or for some entity to provide the
code with a warranty (which section 6 does) beyond Apache 2.0's "no
warranty whatsoever", there could be problems.

Perhaps I'm being too pedantic, but it's an angle that I think should be
evaluated. For a remote module, I think ITK could include it regardless,
but it would be good to know the answers to these questions.

Brian


On Thu, Jan 30, 2014 at 5:26 PM, Luke Bloy <luke.bloy at gmail.com> wrote:

> Thanks Matt,
>
> Do people think this license (
> http://www.rad.upenn.edu/sbia/software/license.html ) would have any
> issues? My belief is that it is based strongly off apache 2.
>
> Thanks again.
> Luke
>
>
> On Thu, Jan 30, 2014 at 12:30 PM, Matt McCormick <
> matt.mccormick at kitware.com> wrote:
>
>> Hi Luke,
>>
>> There has been considerable work into keeping the repository
>> patent-free and minimize copyleft licenses (see the CMake warning when
>> FFTW support is enabled, which is off by default).
>>
>> The preferred license is Apache 2.0 with copyright assigned to the
>> Insight Software Consortium, like the rest of the toolkit.  Other
>> BSD-style licenses should well work, too.
>>
>> I personally would be fine with most other licenses, too, for a Remote
>> Module, but it also depends on the input of other members of the
>> community.
>>
>> Thanks,
>> Matt
>>
>> On Wed, Jan 29, 2014 at 9:29 PM, Luke Bloy <luke.bloy at gmail.com> wrote:
>> > Are there any license requirements for being considered for inclusion
>> as a
>> > remote module?
>> >
>> > Luke
>> >
>> > _______________________________________________
>> > Powered by www.kitware.com
>> >
>> > Visit other Kitware open-source projects at
>> > http://www.kitware.com/opensource/opensource.html
>> >
>> > Kitware offers ITK Training Courses, for more information visit:
>> > http://kitware.com/products/protraining.php
>> >
>> > Please keep messages on-topic and check the ITK FAQ at:
>> > http://www.itk.org/Wiki/ITK_FAQ
>> >
>> > Follow this link to subscribe/unsubscribe:
>> > http://www.itk.org/mailman/listinfo/insight-developers
>> >
>> > _______________________________________________
>> > Community mailing list
>> > Community at itk.org
>> > http://public.kitware.com/cgi-bin/mailman/listinfo/community
>> >
>>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Kitware offers ITK Training Courses, for more information visit:
> http://kitware.com/products/protraining.php
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-developers
>
> _______________________________________________
> Community mailing list
> Community at itk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/community
>
>


-- 
Brian Helba
Medical Imaging
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/pipermail/insight-developers/attachments/20140130/7edcc11b/attachment.html>