Incubation FAQ - Revision history

Neteler: mention OSGeo Community Projects as well

2020-04-18T09:01:15Z

mention OSGeo Community Projects as well

Arnulf: /* Q: Sample data licensing? */ more minor fixes

2014-05-15T10:08:55Z

Q: Sample data licensing?: more minor fixes

Arnulf: /* Q: What is needed for Open Development */ minor typos fixed and changes in wording

2014-05-15T10:07:00Z

Q: What is needed for Open Development: minor typos fixed and changes in wording

Arnulf at 09:46, 12 September 2013

2013-09-12T09:46:20Z

Arnulf: /* Projects Joining the Foundation */

2013-03-23T12:09:13Z

Projects Joining the Foundation

Jive: /* Q: What is checked for Open Development = */

2012-10-09T02:17:26Z

Q: What is checked for Open Development =

Jive: /* Open Development */

2012-10-09T02:17:05Z

Open Development

Jive: /* Q: Attribution and Agreement */

2012-10-09T02:15:19Z

Q: Attribution and Agreement

Jive: /* Open Development */

2012-10-09T02:13:59Z

Open Development

Jive: /* Q: Attribution and Agreement */

2012-10-09T02:02:04Z

Q: Attribution and Agreement

@@ Line 195: / Line 195: @@
 *  (FAIL)  Early uDig included some sample data from an ESRI product (simply because that was the data used for testing). The project pulled those releases when the problem was noticed.
 *  (SUCCESS) [[OSGeo Live]] contains and distributes the natural earth dataset and [http://live.osgeo.org/en/overview/naturalearth_overview.html mentions that the license is public domain].
 [[Category:Incubation]]

@@ Line 194: / Line 194: @@
 *  (FAIL)  Early uDig included some sample data from an ESRI product (simply because that was the data used for testing). The project pulled those releases when the problem was noticed.
-*  (SUCCESS) The live DVD is distribution the natural earth dataset and [http://live.osgeo.org/en/overview/naturalearth_overview.html mention that the license is public domain].
+*  (SUCCESS) [[OSGeo Live]] contains and distributes the natural earth dataset and [http://live.osgeo.org/en/overview/naturalearth_overview.html mentions that the license is public domain].
 [[Category:Incubation]]

@@ Line 131: / Line 131: @@
 A: A procedure for several organisations to collaborate, open to new organisations becoming involved
-This is perhaps the most important indicattor of long term viability is how well a project practices open development.
+How well a project practices open development is perhaps the most important indicator of long term viability.
 We are really looking for two things:
@@ Line 145: / Line 145: @@
 * MapServer [http://mapserver.org/development/rfc/index.html Request for Change] procedure has been adopted by several projects for public participation.
 * GeoTools [http://docs.geotools.org/latest/developer/procedures/proposal.html Request for Change] procedure
-* GeoServer has a [http://docs.geoserver.org/stable/en/developer/policies/gsip.html GeoServer Improvement Proposal] procedure
+* GeoServer has a [http://docs.geoserver.org/stable/en/developer/policies/gsip.html Improvement Proposal] procedure
-* The original [http://www.apache.org/foundation/voting.html Apache Voting Process] is here
+* The original [http://www.apache.org/foundation/voting.html Apache Voting Process] also gives good guidance
-Several of these procedures make use of a project steering committee, in each case there is a procedure for new members to be added to the project steering committee.
+Several of these procedures make use of a project steering committee. In each case there is a procedure for new members to be added to the project steering committee.
 = Checks =

← Older revision		Revision as of 09:46, 12 September 2013
Line 195:		Line 195:
	* (FAIL) Early uDig included some sample data from an ESRI product (simply because that was the data used for testing). The project pulled those releases when the problem was noticed.		* (FAIL) Early uDig included some sample data from an ESRI product (simply because that was the data used for testing). The project pulled those releases when the problem was noticed.
	* (SUCCESS) The live DVD is distribution the natural earth dataset and [http://live.osgeo.org/en/overview/naturalearth_overview.html mention that the license is public domain].		* (SUCCESS) The live DVD is distribution the natural earth dataset and [http://live.osgeo.org/en/overview/naturalearth_overview.html mention that the license is public domain].
		+
		+	[[Category:Incubation]]

@@ Line 8: / Line 8: @@
 ; What software projects are currently part of the foundation?
-: On its formation, the GDAL/OGR, GeoTools, GRASS GIS, Mapbender, MapBuilder, MapGuide Open Source, MapServer and OSSIM projects declared their support, and joined as projects in incubation. Since then GDAL/OGR, GRASS GIS, Mapbender, MapBuilder, and MapGuide Open Source have graduated as full projects from this list. Further projects have entered incubation and some have also graduated. See the [http://www.osgeo.org/ OSGeo Projects] on the foundation website for an official list.
+: On its formation, the GDAL/OGR, GeoTools, GRASS GIS, Mapbender, MapBuilder, MapGuide Open Source, MapServer and OSSIM projects declared their support, and joined as projects in incubation. Since then all of these projets have successfully graduated as full projects from this list. Further projects have entered incubation and some have also graduated. See the [http://www.osgeo.org/ OSGeo Projects] on the foundation website for an official list.
 ; What does a project need to do to join?
@@ Line 36: / Line 36: @@
 ; Does the foundation mandate a particular license for content other than software, such as geodata, educational materials, documentation, etc.?
 : The foundation accepts non-software projects that use [http://creativecommons.org/ Creative Commons] or similar licenses for their public geodata, educational material, or promotional material. The foundation also discourages a proliferation of new and incompatible licenses.
 == Q: What is incubation ==

@@ Line 112: / Line 112: @@
 * The GeoTools project [http://docs.geotools.org/latest/developer/roles/commit.html Comitters] roles and responsibilities documents expectations on committter behaviour and links to a formal [http://docs.geotools.org/latest/developer/_downloads/GeotoolsAssignmentToOSGeo.pdf GeoToolsAssignmentToOSGeo.pdf] which must be printed out, and mailed to the OSGeo Foundation.
-== Q: What is checked for Open Development ===
+== Q: What is needed for Open Development ==
 A: A procedure for several organisations to collaborate, open to new organisations becoming involved

@@ Line 85: / Line 85: @@
 == Q: Attribution and Agreement ==
-A: Who wrote it and did they agree to let you distribute it
+A: Record who wrote it and check they agree to let you distribute it
 On the face of it this is a real easy check to understand - but a very hard one to get correct. Projects receive input in large part through contributors and committers; supplemented by patches submitted via issue trackers.

@@ Line 115: / Line 115: @@
 Perhaps the most important indicattor of long term viability is how well a project practices open development.
 We are really looking for two things:
-- evidence that the procedures are in place allowing the project to be run by several organisations as a collaboration
+* Evidence that the procedures are in place allowing the project to be run by several organisations as a collaboration
-- ensuring new groups can take part
+* Ensuring new groups can take part
-While this is sometimes considered a tall order we do ask that projects write down how they are functioning - even if it is inconvenient for others. OSSIM often had key decisions made over breakfast in a monthly face to face meeting. The direction for GeoNetwork was often set by key stakeholders meeting face to face each year. In both these cases taking part is open to new members.
+While this is sometimes considered a tall order, what we are really asking is that projects write down how they are functioning today. As long as new volunteers can take part the project is considered open.
 = Checks =

@@ Line 94: / Line 94: @@
 *  It is common for projects to get in trouble with individuals contributing fixes; while working as an employee. In these cases the employees often owns the contribution and a separate code contribution agreement must be filled in by the employer.
 * It is common from working code to be picked up from one project and used to fix an issue in another. Care must be taken to ensure the licenses compatible or suitable arrangements have been made.
 Examples:
 * PostGIS contributions are made under a common license with no copyright assignment
 * GeoTools contributions are made after a developer has signed a code contribution to the OSGeo Foundation
 * GeoServer contributions are assigned to the Open Planning Project
 * GeoTools has a standing arrangement with GeoServer allowing code to be contributed; in each case an email request is made and formally responded to prior to a fix being back ported to GeoTools. This is a case of a procedure being established allowing the license of the code to be changed from GPL to LGPL.
-This is often checked against file headers and verified using version control history, issue tracker history and any written records such as code contribution agreements.
+== Q: Is a code contribution agreement required ==
-A: Example of a Code Contribution Agreement
+Examples:
 == Open Development ==