OTB Project Incubation Status

General
Yes. Announcement was made publicly on December 17, 2013. Yes. Landon Blake.
 * 1) Has the project been approved for incubation by the OSGeo board?
 * 1) Has an Incubation Mentor been assigned to the project?

Infrastructure Transition
No. An existing web page exists: http://orfeo-toolbox.org/otb/ No. An existing bug tracker is being used by the project: http://bugs.orfeo-toolbox.org No. An existing version control system is being used for the project: http://hg.orfeo-toolbox.org/OTB No. Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html
 * 1) Has the projectname.osgeo.org domain been populated with the projects web presence? If not why, and has the project page got a prominent link to the real home?
 * 1) Is the OSGeo bug tracker being used for the project? If not, why? Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project? If not, why?
 * 1) Is the OSGeo SVN being used for the project? If not, why?
 * 1) Are binary and source downloads available from http://download.osgeo.org ? If not, why?

Community Functioning
The project currently provides support through a mailing list, managed using Google Groups. Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html The project doesn't currently have a PSC. There are plans to form one and to have control passed from CNES to the PSC. This should take place by the early summer of 2014. The ohloh page of the Orfeo ToolBox provides a comprehensive view of contributors activity:
 * 1) Is there a functioning user support mechanisms (ie. mailing list)?
 * 1) Are source and binary downloads for the package available?
 * 1) Has a Project Steering Committee been formed, and given control of the project?
 * 1) Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines?
 * 2) How many active developers are there? Are they from multiple organizations? Indicate number and some organizations involved.

http://www.ohloh.net/p/otb/contributors?sort=latest_commit

There were around 15 commiters over the last year.

The "Contributors" chapter of the Software Guide gives a complete listing of all contributors and their affiliations from the beginning of the project :

http://orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech35.html#x64-52100035

Very active users and occasional contributors include:


 * Jordi Inglada from CESBIO/CNES is the creator of OTB and as such wrote a lot of OTB code in the past. He still actively uses and promotes it, with a lot of client codes, testing, bug reports, phd and intern works ...
 * Gregoire Mercier from Télécom Bretagne wrote the entire wavelet transform code as well as other codes, and currently has a phd working with OTB,
 * Angelos Tzotzos from National Technical University of Athens is actively packaging OTB for OpenSuse. He also contributed code for a pan-sharpening algorithm and integrated some OTB in the Gnorasi project,
 * Agustin Lobo, who I believe is with CSIC, is a very active user that benchmarked some of OTB functions and makes insightful comments on improving documentation for instance,
 * Julien Radoux (UCL) has contributed some algorithms by the past and is still very active on the users list,
 * Emmanuel Christophe, currently with Google, who wrote a great deal of OTB code by the past, under CNES and Crisp affiliations.

Foundation Membership
Changes will be made to project documentation in Fall 2014. Changes will be made to the website as part of a website redesign before the end of 2014.
 * 1) Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation? If not, indicate when this will occur.
 * 1) Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks? If not, indicate what is planned.

Code Copyright Review
OTB Code Provenance Review
 * 1) Has a Code Provenance Review document been prepared for the project?
 * 1) Have issues raised in the provenance review been adequately addressed? Indicate outstanding issues.
 * 2) Are Commiter Responsibilities Guidelines covering legal issues in place?