OTB Project Incubation Status

From OSGeo
Revision as of 17:40, 17 December 2013 by Surveyor (talk | contribs)
Jump to navigation Jump to search


  1. Has the project been approved for incubation by the OSGeo board?

Yes. Announcement was made publicly on December 17, 2013.

  1. Has an Incubation Mentor been assigned to the project?

Yes. Landon Blake.

Infrastructure Transition

  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?

No. An existing web page exists: http://orfeo-toolbox.org/otb/

  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?

No. An existing bug tracker is being used by the project.

  1. Is the OSGeo SVN being used for the project? If not, why?

No. An existing version control system is being used for the project: http://hg.orfeo-toolbox.org/OTB

  1. Are binary and source downloads available from http://download.osgeo.org ? If not, why?

No. Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html

Community Functioning

  1. Is there a functioning user support mechanisms (ie. mailing list)?
  2. Are source and binary downloads for the package available?
  3. Has a Project Steering Committee been formed, and given control of the project?
  4. Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines?
  5. How many active developers are there? Are they from multiple organizations? Indicate number and some organizations involved.

Foundation Membership

  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.
  2. 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

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