ZOO-Project Incubation Checklist - Revision history

Jmckenna at 15:10, 19 August 2017

2017-08-19T15:10:06Z

2017-08-19T15:02:42Z

Open

2015-03-12T13:42:48Z

Documentation

2015-03-12T11:45:20Z

Documentation

2015-03-12T11:26:20Z

Open

2015-02-25T13:42:12Z

2015-02-25T13:41:24Z

2015-02-23T13:28:44Z

2015-02-23T13:19:07Z

Open

2015-02-23T13:18:17Z

Open

@@ Line 6: / Line 6: @@
 # Open: projects are expected to function in an open and public manner and include:
 #* Open source license(s),
-#** The ZOO-Project is primarily under the BSD [http://www.zoo-project.org/trac/browser/trunk/zoo-project/LICENSE LICENSE] and the [http://zoo-project.org/trac/wiki/Provenance%20Review Provenance Review] has confirmed there are no known problems.
+#** The ZOO-Project is primarily under the BSD [http://www.zoo-project.org/trac/browser/trunk/zoo-project/LICENSE LICENSE] and the [http://zoo-project.org/trac/wiki/ProvenanceReview Provenance Review] has confirmed there are no known problems.
 #* Open communication channels,
 #** The [http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss zoo-discuss] list is public and active.  IRC and other [http://zoo-project.org/site/ZooWebSite/ZooProject/Contact Contact] points also available.

@@ Line 18: / Line 18: @@
 #** http://www.zoo-project.org/site/ZooWebSite/ZooProject/Tribe provides informations about the community
 #* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. <br/>
-#** contributions come from GeoLabs SARL, Fundazione Edmund Mach, Osaka City University, 3LIZ SARL, Cartogenic SARL and further more.
+#** contributions come from GeoLabs SARL, Fundazione Edmund Mach, Osaka City University and some more.
 == Copyright and License ==

@@ Line 57: / Line 57: @@
 #** Build instructions are here: [http://www.zoo-project.org/docs/kernel/installation.html#kernel-installation]
 #* Including commented code, ideally published for developer use. <br/><i>Examples: javadocs for Java applications, or Sphinx documentation for Python applications.</i>
-#** The code comments are using Doxygen, final tweeks before publication on the ZOO-Project web site.
+#** The code comments are using Doxygen and available from [http://zoo-project.org/trac/doxygen/index.html].
 #* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.

@@ Line 51: / Line 51: @@
 # The project has user documentation:
 #* Including sufficient detail to guide a new user through performing the core functionality provided by the application.
 # The project has developer documentation:
 #* Including checkout and build instructions.
 #* Including commented code, ideally published for developer use. <br/><i>Examples: javadocs for Java applications, or Sphinx documentation for Python applications.</i>
 #* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.

@@ Line 13: / Line 13: @@
 # Active and healthy community:
 #* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. <br/>
-#** Suggested Text?
+#** Release processes are open and documented at http://zoo-project.org/trac/wiki/ReleaseProcedure
 #* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. <br/>
 #** contributions come from GeoLabs SARL, Fundazione Edmund Mach, Osaka City University, 3LIZ SARL, Cartogenic SARL and further more.

@@ Line 23: / Line 23: @@
 #* Yes, as seen in [http://www.zoo-project.org/trac/browser/trunk/zoo-project/LICENSE LICENSE].
 # Project documentation is available under an open license, such as Creative Commons.
-#* The documentation license is now well stated on its [file:///Users/djay/MapMint/zoo-project-svn-1.4.0/trunk/docs/_build/html/index.html#license front page].
+#* The documentation license is now well stated on its [http://zoo-project.org/docs/index.html#license front page].
 # The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included, as per a [http://www.osgeo.org/incubator/process/codereview.html Provenance Review].
 #* [http://zoo-project.org/trac/wiki/Provenance%20Review Provenance review] completed, no issues.

@@ Line 27: / Line 27: @@
 #* [http://zoo-project.org/trac/wiki/Provenance%20Review Provenance review] completed, no issues.
 # The project maintains a list of all copyright holders identified in the Provenance Review Document.
-#* (how to respond?)
+#* In some sense, the prevenance review for the ZOO-Kernel point to the LICENCE file which should bne updated at any new commit as specified in the contribution [http://zoo-project.org/docs/community/developer.html#legal rules].
 # All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.
 #* The [http://zoo-project.org/docs/community/developer.html code contribution guidelines] have been documented and agreed to by all developers.

@@ Line 10: / Line 10: @@
 #** The [http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss zoo-discuss] list is public and active.  IRC and other [http://zoo-project.org/site/ZooWebSite/ZooProject/Contact Contact] points also available.
 #* Open decision making process,
-#** (Gerald is looking into making zoo-psc list public).  PSC meeting agenda and results available (for instance [http://zoo-project.org/trac/wiki/PSC/meetings/PSCMeet19?version=8 PSC Meeting 19]).
+#** zoo-psc list is public (see [http://lists.osgeo.org/pipermail/zoo-psc/2014-September/000542.html reference email]).  PSC meeting agenda and results available (for instance [http://zoo-project.org/trac/wiki/PSC/meetings/PSCMeet19?version=8 PSC Meeting 19]).
 # Active and healthy community:
 #* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. <br/>