FDO Incubation Status

From OSGeo
Jump to navigation Jump to search


Has the project been approved for incubation by the OSGeo board?
Yes, FDO is a board approved project.
Has an Incubation Mentor been assigned to the project?
Yes, Daniel Morissette is assigned as mentor.

Infrastructure Transition

Note, for each of the following it isn't necessary to move to foundation infrastructure, but if you aren't a reason should be provided.

Has the projectname.osgeo.org domain been populated with the projects web presence?
Yes. http://fdo.osgeo.org/ has been established and populated with project content
Is the OSGeo bug tracker being used for the project?
Yes. Refer to http://trac.osgeo.org/fdo
Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project?
Yes. All FDO mailing lists are now listed at http://lists.osgeo.org. They include 'fdo-announce', 'fdo-internals', 'fdo-users', 'fdo-trac' and 'fdo-commits'
Is the OSGeo SVN being used for the project?
Yes. Refer to http://trac.osgeo.org/fdo/browser
Are binary and source downloads available from http://download.osgeo.org ?
Yes. Refer to http://download.osgeo.org/fdo

Community Functioning

Is there a functioning user support mechanisms (ie. mailing list)?
Yes. There is a well established developer community and user community.
The mailing lists are in place and are functioning well. Issues raised on the internals and users mailing lists are being addressed in a timely manner. The available FDO mailing lists can be found at http://lists.osgeo.org/mailman/listinfo. They include 'fdo-announce', 'fdo-internals', 'fdo-users', 'fdo-trac' and 'fdo-commits'.
User support is also available using trac at http://trac.osgeo.org/fdo and though irc at irc://irc.freenode.net/#fdo
Project stats are also available on ohloh.net: http://www.ohloh.net/projects/4662
Are source and binary downloads for the package available?
Binary, Source code and Documentation downloads are available for multiple FDO releases. Refer to http://fdo.osgeo.org/content/downloads. Currently binary support is limited to release builds on Windows XP and Redhat EL 4.
Has a Project Steering Committee been formed, and given control of the project?
Yes. Refer to http://fdo.osgeo.org/psc.html. The committee was formed in October 2006. The current PSC members include Greg Boone (chair), Frank Warmerdam, Robert Bray, Jason Birch, Orest Halustchak, Haris Kurtagic and Mateusz Loskot.
The FDO PSC came into being in October 2006. Bob Bray initially organized Greg Boone and Orest Halustchak from Autodesk, as well as Frank Warmerdam from the GDAL project, Jason Birch from the City of Nanaimo, and Mateusz Loskot a freelance GIS software consultant to meet and form the FDO PSC. Haris Kurtagic was subsequently added as a member. The minutes of that first PSC meeting can be found at : http://trac.osgeo.org/fdo/wiki/PscMeeting20061030. The OSGeo Board subsequently approved the application by the FDO project to enter incubation in March 2007. Further details on the history of FDO and the associated software releases can be found at http://fdo.osgeo.org/history.html and http://fdo.osgeo.org/roadMap.html
Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
Yes. Refer to http://fdo.osgeo.org/psc.html
How many active developers are there? Are they from multiple organizations?
12 developers from Autodesk and at least 3 external developers.

Foundation Membership

Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
Yes - The FDO site (http://fdo.osgeo.org) content inherits and uses the styles defined by the osgeo site.

Code Copyright Review

Has a Code Provenance Review document been prepared for the project?
Yes it can be found at: http://wiki.osgeo.org/index.php/FDO_Provenance_Review
Have issues raised in the provenance review been adequately addressed?
  • Yes. A full source code review has been completed.
    • The origins of the FDO source code have been identified
    • All Third-Party code dependencies have been identified and documented
    • All Third-Party licence agreements have been identified and documented
    • All source files have been checked for the appearance of the GNU GPL copyright text
    • All source files have been copyright reviewed and the copyright(s) holders specified
    • All data files have been copyright reviewed and the copyright(s) holders specified
Are Commiter Responsibilities Guidelines covering legal issues in place?
Refer to the FDO Individual Contributor Agreement: http://fdo.osgeo.org/files/Individual%20Contributor%20Agreement%20-%20FDO.pdf
Refer to the FDO Corporate Contributor Agreement: http://fdo.osgeo.org/files/Corporate%20Contributor%20Agreement%20-%20FDO.pdf