FDO Provenance Review

Introduction

Last Updated: 26 September 2006.

This page details information from files in the OSGeo FDO Subversion repository and its Subprojects located at:

https://fdo.osgeo.org/

https://fdocore.osgeo.org/

https://fdoarcsde.osgeo.org/

https://fdogdal.osgeo.org/

https://fdoogr.osgeo.org/

https://fdordbms.osgeo.org/

https://fdosdf.osgeo.org/

https://fdoshp.osgeo.org/

https://fdowfs.osgeo.org/

https://fdowms.osgeo.org/

This page documents the results of a License audit of the OSGeo FDO project and its SubProjects. It is done in accordance with the OSGEO Foundation guidelines at:

http://wiki.osgeo.org/index.php/Code_Provenance_Review

Goal

To establish a reasonable comfort level that projects going through incubation do not have improperly contributed code, and that the code is all under the project license.

A code provenance review is desirable because it reduces the risk of the foundation, project developers or software users becoming involved in a legal action or having their use of the software disrupted by sudden removal of improperly contributed code. In particular, many enterprises will not build on open source software projects without some degree of assurance that care is being taken to avoid improper contributions.

It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on us to prove there are no problem. However we want to ensure we do not release code with provenance issues that we could have identified and corrected with a reasonable effort.