[Insight-developers] ITK 2.6 Release: Delay : Copyright : BCP :Review Directory

[Luis Ibanez]

Hi Bill,

Since nobody raised any objections to the proposal
of adding the "Review" directory, it seems to be
a good idea to proceed with it and move on with the
release process.

I just added both directories. So we can now move
the new classes during the weekend.

README.txt files were added in both directories
describing the purpose and status of the files to
be committed there.  Please feel free to edit the
README file as you consider appropriate.


      Luis


--------------------------------------------
Lorensen, William E (GE, Research) wrote:
> Luis,
> 
> We need to make a decision about the release. Should we move the new classes that do not have copyright trnasfers and go ahead and cut a release?
> 
> Bill
> 
> -----Original Message-----
> From: insight-developers-bounces+lorensen=crd.ge.com at itk.org
> [mailto:insight-developers-bounces+lorensen=crd.ge.com at itk.org]On Behalf
> Of Luis Ibanez
> Sent: Wednesday, March 01, 2006 5:10 PM
> To: Insight Developers List
> Subject: [Insight-developers] ITK 2.6 Release: Delay : Copyright : BCP
> :Review Directory
> 
> 
> 
> The ITK 2.6 release has been delayed due to some difficulties
> with the copyright status of new code contributed by authors
> through the Insight Journal.
> 
> 
> In the interest of untangling the situation, it has been proposed
> that we add to the CVS source tree of ITK a "neutral zone" directory
> that will be exempt of both the Copyright ISC policy and the Backward
> Compatibility Policy (BCP).
> 
> 
> 
> The current proposal is to create the following new directories:
> 
> 
>                Insight/Code/Review
> 
>                Insight/Testing/Code/Review
> 
> 
> Source code taken from contributions posted to the Insight Journal
> will be committed in these two directories, and in this way it will
> be tested in multiple platforms at the same time that developers
> have a chance to evaluate and review the code in a public and more
> efficient way.
> 
> Code committed in this directory will not stay there for more than
> one release cycle. As a result of the evaluation of the code in this
> directory, the files will be moved to a final destination inside the
> toolkit or they will be rejected and removed from the Review directory.
> 
> 
> We hope that this mechanism will provide a reasonable compromise
> between our commitment to the BCP, the Copyright policy and the
> methodology of Extreme Programming.
> 
> 
> 
> 
> Please let us know if you see any drawback in this approach, or
> if you have any suggestions for making it better.
> 
> 
> We plan to have a solution implemented by the end of the week so
> we can proceed with the release process.
> 
> 
> 
>     Regards,
> 
> 
> 
>        Luis
> 
> 
> 
> 
> _______________________________________________
> Insight-developers mailing list
> Insight-developers at itk.org
> http://www.itk.org/mailman/listinfo/insight-developers
> 
>