Changes between Version 15 and Version 16 of OSGeoIncubationChecklist


Ignore:
Timestamp:
Aug 5, 2013, 12:48:29 PM (11 years ago)
Author:
abeccati
Comment:

fixed links to old server name (now rasdaman.org)

Legend:

Unmodified
Added
Removed
Modified
  • OSGeoIncubationChecklist

    v15 v16  
    5252   i. rasdaman-dev list: https://groups.google.com/forum/?fromgroups#!forum/rasdaman-dev
    5353   i. rasdaman-user list: https://groups.google.com/forum/?fromgroups#!forum/rasdaman-usersras
    54    i. issue tracker (trac): http://rasdaman.eecs.jacobs-university.de/trac/rasdaman/report/1
     54   i. issue tracker (trac): http://rasdaman.org/report/1
    5555  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Open decision making process: Feature table is maintained on wiki, new features can be openly discussed on the mailing lists.
    5656 1. Active and healthy community:
     
    7373 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/1/11/Hourglass.png)]] Project documentation is available under an open license (Eg. Creative Commons)
    7474 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included.
    75   a. Code Provenance Review: http://rasdaman.eecs.jacobs-university.de/trac/rasdaman/wiki/OSGeoCodeProvenance
     75  a. Code Provenance Review: http://rasdaman.org/wiki/OSGeoCodeProvenance
    7676 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project maintains a list of all copyright holders identified in the Provenance Review Document
    7777  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/1/11/Hourglass.png)]] List holders here? (PB: Listing all would require somebody watching commits, it would be more or less up to date and more or less accurate - so seems like an extra burden without creating additional information content. All contributors are automatically listed here: http://www.rasdaman.org/patchmanager/all )
    7878 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived
    79   a. Code contribution agreement: http://rasdaman.eecs.jacobs-university.de/trac/rasdaman/wiki/ContributorAgreement .
     79  a. Code contribution agreement: http://rasdaman.org/wiki/ContributorAgreement .
    8080   *. In particular, from the contribution agreement: "Any contribution we make available under any license will also be made available under a suitable FSF (Free Software Foundation) or OSI (Open Source Initiative) approved license"
    8181
     
    8686  a. Rasdaman git repository is established at git://kahlua.eecs.jacobs-university.de/rasdaman.git
    8787 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
    88   a. Trac is used for that purpose and is constantly updated as issues are addressed. Ticket list is at http://rasdaman.eecs.jacobs-university.de/trac/rasdaman/report/1
     88  a. Trac is used for that purpose and is constantly updated as issues are addressed. Ticket list is at http://rasdaman.org/report/1
    8989 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.
    9090  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.