Changes between Version 24 and Version 25 of OSGeoIncubationChecklist

Timestamp:

Mar 29, 2014, 8:16:54 PM (11 years ago)

Author:

Peter Baumann

Comment:

—

OSGeoIncubationChecklist

@@ -59 +59 @@
  1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project uses an issue tracker and keeps the status of the issue tracker up to date
   a. Trac is used for that purpose and is constantly updated as issues are addressed. Ticket list is at http://rasdaman.org/report/1
- 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/1/11/Hourglass.png)]] The project has documented its management processes. NOTE: This is typically done within a Developers Guide or Project Management Plan.
-  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/9/90/Icons-mini-icon_alert.gif)]] (looks like duplicate of "Open" item 1.c) The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. Note: This typically means a Project Management Committee has been established with a process for adding new members. A robust Project Management Committee will typically draw upon developers, users and key stakeholders from multiple organisations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.
+ 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project has documented its management processes. NOTE: This is typically done within a Developers Guide or Project Management Plan.
+  a. (looks like duplicate of item 1.c) The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. Note: This typically means a Project Management Committee has been established with a process for adding new members. A robust Project Management Committee will typically draw upon developers, users and key stakeholders from multiple organisations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.
   * developers are actively solicited to have technical discussion directly through the dev list. Based on these improvements it seems we can keep with the overall regime for now.