[Insight-developers] ITKv4 : LICENSE Changed to Apache 2.0
Tom Vercauteren
tom.vercauteren at m4x.org
Thu Oct 7 14:40:34 EDT 2010
Hi Luis,
Excuse my ignorance about licenses but I have a few questions
regarding this change.
1) Does the redistribution clause 4.2 requires that if someone
distributes some binary software that uses a patched ITK, this someone
has to mention the names of all patched files? This is what I
understand from
http://www.apache.org/licenses/LICENSE-2.0.html#redistribution
but the FAQ seems to say otherwise
http://www.apache.org/foundation/licence-FAQ.html#WhatDoesItMEAN
I hope the FAQ has it right because it seems a bit cumbersome to list
all modified files in a place accessible to the end user. Not that I
keep ITK patches privately but I often have some ITK patches in my
software before they make it to ITK proper.
2) Regarding the code that lies in Code/Patented. Did any of the
inventors actually contributed to it? If so, I guess that we need to
get rid of it before making the license change effective.
http://www.apache.org/licenses/LICENSE-2.0.html#patent
Am I understanding it correctly?
3) In two words (if that is possible) what is the rationale for making
this change?
As far as the header is concerned, I also like to have a simple header.
Tom
On Thu, Oct 7, 2010 at 19:41, Luis Ibanez <luis.ibanez at kitware.com> wrote:
>
> Hi Stephen,
>
>
> You were right at the tcon, in that the license change
> was not applied yet to the top of the ITK source tree.
>
>
> I thought we have actually done so back in July...
> My mistake.
>
>
> -------------------------------------------------------------
>
>
> To All:
>
>
> We have now proceeded to change the license from
> BSD to Apache 2.0, as agreed by the Board of the
> Insight Software Consortium, back in Januay 2010.
>
>
> The change applies to ITKv4 and does not affect
> previous releases of the toolkit.
>
>
> Full Details are in the following Wiki page:
> http://www.itk.org/Wiki/ITK_Release_4/Licensing
>
> That is linked from:
> http://www.itk.org/Wiki/ITK_Release_4.0#LICENSE_Change
>
>
> In Summary:
>
>
> 1) A file "LICENSE" has been added at the top of the
> ITK Source tree, containing the full text of the
> Apache 2.0 license:
>
> http://itk.org/gitweb?p=ITK.git;a=commit;h=a0ff25c3fec0911f948f9bbb7a3ec684f2926e46
>
>
> 2) A file "NOTICE" is now at the top of the ITK source tree,
> containing a manifesto of the copyright and licenses of
> third party files that are distributed along with the toolkit,
> and/or section of code that have been integrated with
> the ITK toolkit. (in the same commit).
>
>
> 3) The File: ITK/Copyright/ITKCopyright.txt
> is now pointing to the files: LICENSE and NOTICE
>
>
>
>
> Pending:
> =======
>
>
> A) We must now change the text of the license and copyright notice in
>
> http://www.itk.org/ITK/project/license.html
>
> that is the alias for
>
> http://www.itk.org/HTML/Copyright.htm
>
> B) We must apply the change to the headers of all ITK files.
>
> The proposed new header is shown here:
>
> http://www.itk.org/Wiki/ITK_Release_4/Licensing#File_Header_Changes
>
>
> Comments are welcome.
>
>
>
> C) The subdirectory "ITK/Copyright" (and its content) must be
> removed, since now all its information is contained in the
> LICENSE and NOTICE files.
>
>
> =================================================
>
>
>
> There are probably modifications that must be applied in other
> places in the toolkit, and its related documentation, so if you find
> any, please point them out to us so we can fix them promptly.
>
>
>
> Thanks
>
>
>
> Luis
>
>
>
>
>
>
> _______________________________________________
> 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.html
>
> 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
>
>
More information about the Insight-developers
mailing list