[Insight-developers] COPYRIGHTS / BACKWARD COMPATABILITY / RELEASE ITK 2.6 / New Candidate Directory

[Luis Ibanez]

I agree with Jim,

The code in this directory shouldn't stay there for
more than one release iteration. (e.g. 90 days).


We will make the compilation of this directory to
be off by default in the CMake configuration, just
like we do with the "Patented" directories.


We will also add warnings notes regarding the exclusion
of this directory from the Backward compatibility and
Copyright policies.




Now we just need to agree in a directory name...

        [ How hard can that be ?    :-)   ]



Here are some suggested candidates for the name
(in no particular order):


       1) Insight/Code/Incoming
       2) Insight/Code/Tentative
       3) Insight/Code/Transition
       4) Insight/Code/InsightJournal
       5) Insight/Code/Incubator
       6) Insight/Code/Incubation
       7) Insight/Code/Nursery
       8) Insight/Code/Board
       9) Insight/Code/Quarantine
      10) Insight/Code/Evolving
      11) Insight/Code/Sandbox
      12) Insight/Code/IncomingContributions
      13) Insight/Code/Trenches
      14) Insight/Code/Oven
      15) Insight/Code/Candidate
      16) Insight/Code/Beta
      17) Insight/Code/OnDeck
      18) Insight/Code/FeshMeat
      19) Insight/Code/Tentative
      20) Insight/Code/Preliminary



Any preferences, or other suggestions ?



    Thanks



       Luis


----------------------------------------
Miller, James V (GE, Research) wrote:

 > Just to add to the discussion....
 >
 > The original idea was that items could only spend 1 release in the 
on-deck
 > circle.  After that period, the code would either have to move into ITK
 > proper or out of the repository.
 >
 > What we don't want to promote is prolonge use of code that is not 
truly "blessed".
 >
 > Jim
 >
 > -----Original Message-----
 > From: Stephen R. Aylward [mailto:Stephen.Aylward at Kitware.com]
 > Sent: Monday, February 20, 2006 3:53 PM
 > To: Luis Ibanez
 > Cc: Lorensen, William E (GE, Research); Miller, James V (GE, Research);
 > Joshua Cates; Lydia Ng; Julien Jomier; Ross Whitaker; Hans Johnson;
 > Vincent A. Magnotta
 > Subject: Re: COPYRIGHTS / BACKWARD COMPATABILITY / RELEASE ITK 2.6
 >
 >
 > Seems okay with me.
 >
 > I guess the CMake default would be to not build into that directory, 
and it would have to be specifically turned-on to use.   Perhaps even a 
pop-up could be used to warn about licensing and API changes....
 >
 > I actually really like this idea....more than a contrib directory it 
is a candidate directory or a beta directory...
 >
 > Stephen
 >
 > Luis Ibanez wrote:
 >
 >> Hi Stephen,
 >>
 >> We are running behind schedule with the insertion
 >> of IJ contributions into the ITK repository.
 >>
 >> Partly because we missed to consider the time
 >> required for obtaining copyright transfers from
 >> the authors of papers in the Insight Journal.
 >>
 >>
 >> Since this policy was voted in the recent ISC
 >> meeting, we are trying to find a compromise that
 >> could allow us to:
 >>
 >>
 >> 1) Have an Agile (Extreme) development of the toolkit.
 >> 2) Satisfy the backward compatibility policy.
 >> 3) Respect our intellectual property policy.
 >>
 >>
 >>
 >> At the last tcon, Bill suggested that we could add a
 >> new directory to the ITK repository. This directory
 >> will be excluded from the Backward compatibility promise
 >> given to the users (meaning, the API of classes in this
 >> directory may change over time, or the classes may even
 >> disappear). The directory will also be excluded from the
 >> copyright policy.
 >>
 >> The idea is to have a place that plays the role of a
 >> Sandbox. In this directory we will be able to make
 >> experiments on the API of new contributions, make sure
 >> that they compile in all the supported platforms, and
 >> gather feedback from the community.
 >>
 >> Once the classes in that directory have matured, and we
 >> have secured copyright transfers for them, we will move
 >> them to a final location in the toolkit.
 >>
 >>
 >> Please let us know what you think about this option.
 >>
 >>
 >> In the meantime, I will suggest that we delay the
 >> release of ITK 2.6 for at least one week, since we
 >> already put int the CVS repository some classes for
 >> which we have not received copyright transfers.
 >>
 >>
 >>
 >>   Thanks
 >>
 >>
 >>
 >>     Luis
 >>
 >>
 >>
 >>
 >> BTW: Josh: Could you please let us know what copyright
 >>           transfers have you received ?
 >>
 >>           Maybe we should create a Wiki page with a table
 >>           listing the copyright transfers that we have
 >>           received, so we don't have to bother you with
 >>           the same question over and over again.
 >>
 >>
 >>
 >>
 >
 >