Difference between revisions of "General Principles of Incubation"

From OSGeo
Jump to: navigation, search
Line 1: Line 1:
This document is meant to be a guide to the incubation principles of OSGeo.
+
== Purpose of Incubation ==
  
* Projects should manage themselves striving for consensus and encouraging participation from all contributors - from beginning users to advanced developers.
+
The purpose of the OSGeo incubation process is to ensure that projects that are officially part of OSGeo:
* Projects should document how they manage themselves.
+
 
 +
* have a successfully operating open and collaborative development community
 +
* have clear IP oversight of the code base of the project
 +
* adhere to the OSGeo principles and operating procedures
 +
 
 +
== Principles of OSGeo Projects (The OSGeo Way) ==
 +
 
 +
* Projects should manage themselves, striving for consensus and encouraging participation from all contributors - from beginning users to advanced developers.
 
* Contributors are the scarce resource and successful projects court and encourage them.
 
* Contributors are the scarce resource and successful projects court and encourage them.
 
* Projects are encouraged to adopt open standards and collaborate with other OSGeo projects.
 
* Projects are encouraged to adopt open standards and collaborate with other OSGeo projects.
 +
* Projects are responsible for reviewing and controlling their code bases to insure the integrity of the open source baselines.
 +
 +
== Operating Procedures ==
 +
 +
* Projects should document how they manage themselves.
 
* Projects should maintain developer and user documentation.
 
* Projects should maintain developer and user documentation.
* Projects should maintain a source code management system - svn is preferred.
+
* Projects should maintain a source code management system.
 
* Projects should maintain a discrepancy tracking system.
 
* Projects should maintain a discrepancy tracking system.
 
* Projects should maintain project mailing lists.
 
* Projects should maintain project mailing lists.
 
* Projects should actively promote their participation in OSGeo.
 
* Projects should actively promote their participation in OSGeo.
* Projects are responsible for reviewing and controlling their code bases to insure the integrity of the open source baselines.
 
 
* Projects are encouraged to adopt OSGeo look and feel, branding, logos on their project sites.
 
* Projects are encouraged to adopt OSGeo look and feel, branding, logos on their project sites.
 
* Projects are encouraged to participate in OSGeo standardization efforts to present a common interface for OSGeo visitors and members.
 
* Projects are encouraged to participate in OSGeo standardization efforts to present a common interface for OSGeo visitors and members.
* Projects should have automated build and smoke test systems
+
* Projects should have automated build and smoke test systems.
*
+
 
+
The OSGeo will in turn attempt to make available the best of breed 
+
open source collaborative tools and resources to support those 
+
efforts, if we offer better tools and resources projects will 
+
naturally migrate to the better implementations.
+
 
+
I'm sure I've missed several important points, the main point being 
+
that we lead vs control.
+
  
New projects compete for our approval with the same guidelines - 
 
hopefully they will be included based on their perceived value to the 
 
OSGeo overall goals and objectives.
 
  
  
 
[https://incubator.osgeo.org/servlets/ReadMsg?listName=incubator&msgNo=224 Mark Lucas' thoughts on incubation]
 
[https://incubator.osgeo.org/servlets/ReadMsg?listName=incubator&msgNo=224 Mark Lucas' thoughts on incubation]

Revision as of 10:26, 12 June 2006

Purpose of Incubation

The purpose of the OSGeo incubation process is to ensure that projects that are officially part of OSGeo:

  • have a successfully operating open and collaborative development community
  • have clear IP oversight of the code base of the project
  • adhere to the OSGeo principles and operating procedures

Principles of OSGeo Projects (The OSGeo Way)

  • Projects should manage themselves, striving for consensus and encouraging participation from all contributors - from beginning users to advanced developers.
  • Contributors are the scarce resource and successful projects court and encourage them.
  • Projects are encouraged to adopt open standards and collaborate with other OSGeo projects.
  • Projects are responsible for reviewing and controlling their code bases to insure the integrity of the open source baselines.

Operating Procedures

  • Projects should document how they manage themselves.
  • Projects should maintain developer and user documentation.
  • Projects should maintain a source code management system.
  • Projects should maintain a discrepancy tracking system.
  • Projects should maintain project mailing lists.
  • Projects should actively promote their participation in OSGeo.
  • Projects are encouraged to adopt OSGeo look and feel, branding, logos on their project sites.
  • Projects are encouraged to participate in OSGeo standardization efforts to present a common interface for OSGeo visitors and members.
  • Projects should have automated build and smoke test systems.


Mark Lucas' thoughts on incubation