GeoNetwork Incubation Status

Basics

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

Yes, it was approved in Twenty First Board Meeting.

Has an OSGeo committee member been assigned as Mentor?

Yes, Jody Garnett is assigned as mentor.

Infrastructure Transition

Has the projectname.osgeo.org domain been populated with the projects we presence?

Yes. The domain forwards to the GeoNetwork Community website http://geonetwork-opensource.org

An info sheet at http://www.osgeo.org/geonetwork has also been created.

The Community website has been transfered to a telascience server GeoNetwork Community Website.

Is the OSGeo bug tracker being used for the project?

Yes. the OSGeo tracker is in use by the project.

[http:/trac.osgeo.org/geonetwork/report GeoNetwork Tracker]

Is the OSGeo mailing list manager being used for the project?

No. SourceForge.net mailing list manager is in use by the project.

user mailing list

developer mailing list

commit mailing list

Archives

Is the OSGeo SVN or CVS system being used for the project?

No. SourceForge.net Subversion is used by the project.

svn co https://geonetwork.svn.sourceforge.net/svnroot/geonetwork geonetwork

subversion web interface

We have plans to move to the OSGeo SVN system in the coming months though.

Are binary and source downloads available from the OSGeo download area?

No. We don't know where that area is :)

Community Functioning

Is there a functioning user support mechanisms (ie. mailing list)?

A Community website for the project offering a documentation section with among others Manuals, Tutorials, FAQ's and Howto's and a software section for binaries is available at http://geonetwork-opensource.org

A user, a developer and a commit mailing list are available.

The mailing lists are also accessible online via Nabble

An IRC channel #geonetwork is registered at irc://irc.freenode.net/geonetwork

Commits are notified to the IRC channel via CIA-bot

The bug, feature and support trackers on trac.osgeo.org/geonetwork are used

Are source and binary downloads for the package available?

The latest source code is available form SVN on SourceForge.net . Source code for previous versions of GeoNetwork opensource are stored in the SourceForge.net CVS of the project.

Binaries including source code are available from SourceForge.net and can also be found on the Community website.

GeoNetwork opensource has also been published on a CD-Rom and on a DVD including other GeoFOSS software.

Has a Project Steering Committee been formed, and given control of the project?

A Project Steering Committee was formed in 2006. The committee has seven steering committee members. The steering committee meets once a year during the GeoNetwork opensource week. A workplan for the following year is approved during that meeting. See also PSC

Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.

The steering committee documentation is still under development.

How many active developers are there? Are they from multiple organizations?

The project has between 3 and 6 active committers from three different organizations.

The developer mailing list has about 145 subscriptions and the commit mailing list has 17 subscriptions. The user mailing list has about 200 subscriptions.

Foundation Membership

Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?

In articles about GeoNetwork, the relation of the project and OSGeo has been emphasized explicitly.

Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?

The project web site contains the OSGeo logo on the front page and indicates that GeoNetwork opensource is an incubator project of OSGeo. More emphasis on this relation will be added once the project has graduated.

Code Copyright and license Review

Has a Code Provenance Review document been prepared for the project?

Yes. A document is available at GeoNetwork Provenance Review describing the steps taken in the review process.

Have issues raised in the provenance review been adequately addressed?

Two issues were identified and have been resolved. No other issues have been found. The code is considered in full compliance with the used GPL license and there are no known issues related to conflicting copyrights or Intelectual Property rights.