Changes between Version 37 and Version 38 of OSGeoIncubationChecklist


Ignore:
Timestamp:
Jun 11, 2014 7:09:20 AM (3 years ago)
Author:
pbaumann
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OSGeoIncubationChecklist

    v37 v38  
    4343  a. Trac is used for that purpose and is constantly updated as issues are addressed. Ticket list is at http://rasdaman.org/report/1
    4444 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.
    45   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.
    46   * 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.
    47 
    48   a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] (duplicate of Open item 1.b) The project uses public communication channels for decision making to maintain transparency. E.g. archived email list(s), archived IRC channel(s), public issue tracker.
     45  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: http://www.rasdaman.org/wiki/Governance; developers are actively solicited to have technical discussion directly through the dev list.
     46  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] (duplicate of Open item 1.b) The project uses public communication channels for decision making to maintain transparency. E.g. archived email list(s), archived IRC channel(s), public issue tracker: http://www.rasdaman.org/wiki/MailingLists
    4947
    5048