[Insight-developers] Copyright changes...

[Miller, James V (CRD)]

We should also add the PNG and ZLIB copyrights

-----Original Message-----
From: Will Schroeder [mailto:will.schroeder@kitware.com]
Sent: Thursday, January 10, 2002 9:18 AM
To: Bill Lorensen; Lorensen, William E (CRD)
Cc: insight-developers@public.kitware.com
Subject: RE: [Insight-developers] Copyright changes...


Hi Bill-

I know what you're saying but I'm trying to do the correct thing: if we use 
code from another system that is copyrighted, we should do what the 
copyright asks. In the case of VTK, there are many classes (look at the 
mutex stuff, itk::object, itk:TimeStamp, itkIndent, and dozens of others) 
that are nearly direct copies. One thing we could do is identify those 
classes that are derivations of systems with copyright, and then add the 
copyright into them on a per class basis. I choose not to do that to keep 
things uniform but that may have been a bad choice.

This goes for any algorithms/filters that other folks have written: if they 
are direct derivations of existing code with copyright, then that should be 
acknowledged in that particular class, or in some other way.

Comments? Should we talk on Friday?

Will


At 06:34 PM 1/9/2002 -0500, Bill Lorensen wrote:
>Will,
>I am as vtk positive as you are, but there is a lot of code in itk derived 
>from a lot of systems. Do we need to add pointers to them also. (Maybe 
>lymb? ;) ).
>As for vnl, we are using it directly.
>
>Bill
>
>At 03:44 PM 1/9/02 -0500, Will Schroeder wrote:
> >Hi Bill-
> >
> >VTK is mentioned in the copyright because some of the code is derived 
> from VTK (modified from the original VTK), and according to the VTK 
> copyright, it is okay to redistribute the modified code as long as you 
> include the VTK copyright with the changes, and do not misrepresent the 
> modified code as VTK. Similar for VXL....we have modified some of the vnl 
> as well and are redistributing it. VNL also requires keeping tracking of 
> what has changed (we do this through CVS).
> >
> >Will
> >
> >At 03:31 PM 1/9/2002 -0500, you wrote:
> >>Why is vtk mentioned in the copyright?
> >>
> >>-----Original Message-----
> >>From: Will Schroeder [mailto:will.schroeder@kitware.com]
> >>Sent: Wednesday, January 09, 2002 2:58 PM
> >>To: insight-developers@public.kitware.com
> >>Subject: [Insight-developers] Copyright changes...
> >>
> >>
> >>Hi Folks-
> >>
> >>I'd like to clean up the copyright prior to the public release. I'd like to
> >>follow the lead of VXL and eliminate most of the copyright language from
> >>the source code, and refer to the full text elsewhere. I'd also like to
> >>acknowledge VXL/VNL and VTK, and do what their copyrights ask us to
> >>do.  The result is shown below. It is a bit shorter and I think better.
> >>
> >>/*=========================================================================
> >>
> >>   Program:   Insight Segmentation & Registration Toolkit
> >>   Module:    $RCSfile: $
> >>   Language:  C++
> >>   Date:      $Date: 2001/11/30 14:29:19 $
> >>   Version:   $Revision: 1.1 $
> >>
> >>   Copyright (c) 2002 Insight Consortium. All rights reserved.
> >>   See ITKCopyright.txt or http://www.itk.org/HTML/Copyright.htm for 
> details.
> >>
> >>   Portions of this code are covered under the VTK copyright.
> >>   See VTKCopyright.txt or http://www.kitware.com/VTKCopyright.htm for 
> details.
> >>
> >>   Portions of this code are covered under the VXL copyright.
> >>   See VXLCopyright.txt or http://vxl.sourceforge.net/ for details.
> >>
> >>      This software is distributed WITHOUT ANY WARRANTY; without even
> >>      the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
> >>      PURPOSE.  See the above copyright notices for more information.
> >>
> >>=========================================================================*/
> >>
> >>Please yell if you have a problem. Otherwise I'll make the changes and
> >>check them in.
> >>
> >>Will
> >>
> >>_______________________________________________
> >>Insight-developers mailing list
> >>Insight-developers@public.kitware.com
> >>http://public.kitware.com/mailman/listinfo/insight-developers
> >>_______________________________________________
> >>Insight-developers mailing list
> >>Insight-developers@public.kitware.com
> >>http://public.kitware.com/mailman/listinfo/insight-developers
> >
> >_______________________________________________
> >Insight-developers mailing list
> >Insight-developers@public.kitware.com
> >http://public.kitware.com/mailman/listinfo/insight-developers
>
>
>_______________________________________________
>Insight-developers mailing list
>Insight-developers@public.kitware.com
>http://public.kitware.com/mailman/listinfo/insight-developers

_______________________________________________
Insight-developers mailing list
Insight-developers@public.kitware.com
http://public.kitware.com/mailman/listinfo/insight-developers