Changes between Version 39 and Version 40 of OSGeoIncubationChecklist


Ignore:
Timestamp:
Jun 11, 2014, 8:56:03 AM (10 years ago)
Author:
Peter Baumann
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • OSGeoIncubationChecklist

    v39 v40  
    1414== Icon legend and media attribution ==
    1515
    16 [[Image(http://upload.wikimedia.org/wikipedia/commons/1/11/Hourglass.png)]] Waiting for verification. From  http://commons.wikimedia.org/wiki/File:Hourglass.png
     16 * [[Image(http://upload.wikimedia.org/wikipedia/commons/1/11/Hourglass.png)]] Waiting for verification. From  http://commons.wikimedia.org/wiki/File:Hourglass.png
     17 * [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] OK. From http://commons.wikimedia.org/wiki/File:Icons-mini-icon_accept.gif#file
     18 * [[Image(http://upload.wikimedia.org/wikipedia/commons/9/90/Icons-mini-icon_alert.gif)]] Warning Note. From http://commons.wikimedia.org/wiki/File:Icons-mini-icon_alert.gif
     19 * [[Image(http://upload.wikimedia.org/wikipedia/commons/5/5a/Icons-mini-action_stop.gif)]] Not met, yet. From http://commons.wikimedia.org/wiki/File:Icons-mini-action_stop.gif#file
     20 * [[Image(http://upload.wikimedia.org/wikipedia/commons/1/1d/Icons-mini-icon_user.gif)]] Assigned and ongoing. From http://commons.wikimedia.org/wiki/File:Icons-mini-icon_user.gif#file
    1721
    18 [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] OK. From http://commons.wikimedia.org/wiki/File:Icons-mini-icon_accept.gif#file
    19 
    20 [[Image(http://upload.wikimedia.org/wikipedia/commons/9/90/Icons-mini-icon_alert.gif)]] Warning Note. From http://commons.wikimedia.org/wiki/File:Icons-mini-icon_alert.gif
    21 
    22 [[Image(http://upload.wikimedia.org/wikipedia/commons/5/5a/Icons-mini-action_stop.gif)]] Not met, yet. From
    23 http://commons.wikimedia.org/wiki/File:Icons-mini-action_stop.gif#file
    24 
    25 [[Image(http://upload.wikimedia.org/wikipedia/commons/1/1d/Icons-mini-icon_user.gif)]] Assigned and ongoing. From http://commons.wikimedia.org/wiki/File:Icons-mini-icon_user.gif#file
    26 
    27 == INCUBATION CHECKLIST (as per OSGeo) ==
     22== INCUBATION CHECKLIST (as per OSGeo v1.0) ==
    2823
    2924=== Copyright and License ===
    … …  
    4035
    4136 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project has code under configuration management, see the [git://kahlua.eecs.jacobs-university.de/rasdaman.git rasdaman git repository].
    42  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
    43   a. Trac is used for that purpose and is constantly updated as issues are addressed. Ticket list is at http://rasdaman.org/report/1
    44  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. The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner: http://www.rasdaman.org/wiki/Governance; developers are actively solicited to have technical discussion directly through the dev list.
     37 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: http://www.rasdaman.org/report
     38 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project has documented its management processes: http://www.rasdaman.org/wiki/Governance
     39  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner: http://www.rasdaman.org/wiki/Governance; developers are actively solicited to have technical discussion directly through the dev list.
    4640  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project uses public communication channels for decision making to maintain transparency: http://www.rasdaman.org/wiki/MailingLists, http://www.rasdaman.org/report
    4741
    … …  
    5145 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project has user documentation, including sufficient detail to guide a new user through performing the core functionality provided by the application: http://www.rasdaman.org/wiki/Documentation, http://www.rasdaman.org/browser/manuals_and_examples
    5246 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project has developer documentation:
    53   a. Including checkout and build instructions: http://www.rasdaman.org/wiki/Documentation, http://www.rasdaman.org/wiki/Download
    54   a. Including commented code, ideally published for developer use: there is ample inline documentation, including javadoc and doxygen instrumentation: http://www.rasdaman.org/browser
    55   a. Providing sufficient detail for an experienced programmer to contribute patches or a new module in accordance with the project's programming conventions: see http://www.rasdaman.org/wiki/HowToContribute as an entry point for tons of descriptions, hints, and how-tos.
     47  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Including checkout and build instructions: http://www.rasdaman.org/wiki/Documentation, http://www.rasdaman.org/wiki/Download
     48  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Including commented code, ideally published for developer use: there is ample inline documentation, including javadoc and doxygen instrumentation: http://www.rasdaman.org/browser
     49  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Providing sufficient detail for an experienced programmer to contribute patches or a new module in accordance with the project's programming conventions: see http://www.rasdaman.org/wiki/HowToContribute as an entry point for tons of descriptions, hints, and how-tos.
    5650
    5751=== Release Procedure ===
    5852
    59 See http://rasdaman.org/wiki/RasdamanReleaseProcess, rasdaman has set up Release Line and semantic versioning adoption.
    60 Selected portions of the systemtest (mainly OGC services) are being improved with oracle based output validation (e.g. #363, #404)
     53
    6154
    6255In order to maintain a consistent level of quality, the project should follow defined release and testing processes.
    6356
    6457 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project follows a defined release process: (patch revision in place, release policy review ongoing)
    65   a. Which includes execution of the testing process before releasing a stable release.
    66   * All patches submitted to the repository undergo review before being applied to the code base
    67   * Milestones and tickets are used to prepare releases
    68   * Releases adopt semantic versioning (starting from 8.4.0)
    69   * Systemtests are to be run by developers before submitting patches (automated test after patch application under work).
     58  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Which includes execution of the testing process before releasing a stable release: http://212.201.49.21:35000/
     59  * All patches submitted to the repository undergo review before being applied to the code base: http://www.rasdaman.org/patchmanager
     60  * Milestones and tickets are used to prepare releases: http://www.rasdaman.org/report, http://www.rasdaman.org/timeline
     61  * Releases adopt semantic versioning (starting from 8.4.0): http://rasdaman.org/wiki/RasdamanReleaseProcess
     62  * Systemtests are to be run by developers before submitting patches: http://www.rasdaman.org/wiki/CodeGuide
    7063  * Formal process under review at http://rasdaman.org/wiki/RasdamanReleaseProcess
    7164
    72  1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project follows a documented testing process. NOTE: Ideally, this includes both automated and manual testing. Ideally this includes documented conformance to set quality goals, such as reporting Percentage Code Coverage of Unit Tests
    73   *  Release and regression testing has been improved, also with respect to its documentation on the wiki which is still work in progress but already gives the overall picture of the project's test method with systemtests. We encourage users to download forthcoming betas and run these tests on their environment to see it rasdaman can be successfully run there.
     65 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project follows a documented testing process.
     66  *  Release testing has been automated (platforms continuously getting extended); regression testing is available, since inception of open-source rasdaman, through ''cd systemtest && make check''.
    7467  * README documents and wiki pages provide test system description and information
    7568 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Release and testing processes provide sufficient detail for an experienced programmer to follow.
    76   * Release process makes use of the project trac roadmap feature, paired with the ticket manager. The latter has been extended to support "feature" tickets to ease tracking high-level features and assign them to release milestones. Testing system has been documented on wiki.
     69  * Release process makes use of the project trac roadmap feature, paired with the ticket manager. The latter has been extended to support "feature" tickets to ease tracking high-level features and assign them to release milestones. Testing system has been documented on wiki: LINK
    7770
    7871=== OSGeo Committees and Community ===
    … …  
    8376
    8477The OSGeo Board holds ultimate responsibility for all OSGeo activities. The Board requests:
    85  1. [[Image(http://upload.wikimedia.org/wikipedia/commons/5/5a/Icons-mini-icon-accept.gif)]] A project provide a Project Officer as a contact point: (Note: the template at OSGeo states "contract point", mistake?)
     78 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/5/5a/Icons-mini-icon-accept.gif)]] A project provide a Project Officer as a contact point: (Note: the OSGeo template states "contract point", we interpreted this as "contact"): see top of this page, http://www.rasdaman.org/wiki/Governance, http://www.rasdaman.org/wiki/Legal
    8679  a. The Project Officer should be listed at Officers and Board of Directors and Contacts
    8780  a. This person is established when the incubation committee recommends the project for graduation
    88   a. Your community can change the project officer as needed. Note: Add an agenda item to the next board meeting so they can recognize the change of officer.
    89 
     81  a. Your community can change the project officer as needed.
    9082
    9183==== Marketing ====
    … …  
    9385Access to OSGeo's [http://wiki.osgeo.org/wiki/Marketing_Committee Marketing_Committee] and associated [http://wiki.osgeo.org/wiki/Marketing_Pipeline Marketing_Pipeline] is one of the key benefits of joining the OSGeo foundation. The Marketing Committee requests:
    9486
    95  1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] (All material is available since rasdaman is already included in OSGeo Live) Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee's [http://wiki.osgeo.org/wiki/Marketing_Artefacts Marketing Artefacts]. This lists the documentation requirements for OSGeo-Live. Marketing Artefacts include:
    96   a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Application Overview
    97   a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Application Quick Start
    98   a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Logo
    99   a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Graphical Image
    100  1. Ideally, stable version(s) of executable applications are bundled with appropriate distributions. Note: In most cases, this will at least include OSGeo-Live, but may also include DebianGIS, UbuntuGIS, and/or osgeo4w, ms4w, etc.)
     87 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee's [http://wiki.osgeo.org/wiki/Marketing_Artefacts Marketing Artefacts]: rasdaman is included in OSGeo-Live
     88 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Ideally, stable version(s) of executable applications are bundled with appropriate distributions: Available with OSGeo-Live, see also http://standards.rasdaman.org .
    10189
    10290
    … …  
    10593Projects do not exist in isolation; and are expected to communicate and collaborate on key issues.
    10694
    107 [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Related:
    108  * [http://www.postgresql.org/ PostgreSQL] (contact with community established, tickets submitted)
     95Related:
     96 * [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] contact with [http://www.postgresql.org/ PostgreSQL] community established, tickets submitted.
    10997
    11098==== PSC ====
    11199
    112 Project Steering Committee; Consider definition of a PSC to define project direction and overall desired (and undesired) features to better direct development efforts by volunteer contributors.
    113  * STATUS
    114   * we have actively been soliciting technical discussion directly through the dev list, puling dev'ers from bilateral communication to the list. Based on these improvements we can keep with the overall regime for now.
    115   * we double checked the registration policy to the project trac and mailing lists and verified that these are open for registration (lists hosted on google groups)
    116   * PSC and governance is established
     100 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Project Steering Committee: has been stablished, see http://www.rasdaman.org/wiki/Governance
     101  * registration to project trac and mailing lists are open: http://www.rasdaman.org/wiki/MailingLists, http://www.rasdaman.org/admin
     102  * PSC and governance is established: http://www.rasdaman.org/wiki/Governance
    117103
    118  1. Open: projects are expected to function in an open and public manner and include:
    119   a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Open source license(s): GPL for server, LGPL for client components (various other for dependency packages)
     104 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Projects are expected to function in an open and public manner and include:
     105  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Open source license(s): GPL for server, LGPL for client components: http://www.rasdaman.org/wiki/CodeProvenance
    120106  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Open communication channels:
    121107   i. rasdaman-dev list: https://groups.google.com/forum/?fromgroups#!forum/rasdaman-dev
    122108   i. rasdaman-user list: https://groups.google.com/forum/?fromgroups#!forum/rasdaman-usersras
    123109   i. issue tracker (trac): http://rasdaman.org/report/1
    124   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.
    125  1. Active and healthy community:
    126   a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project should have a community of developers and users who actively collaborate and support each other in a healthy way.
    127    i. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Committers listed on governance page.
    128   a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations.
    129    i. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] As of early December 2012 five organizations are actively participating in code development:
    130      * Jacobs University Bremen - http://www.jacobs-university.de/
    131      * Rasdaman - http://rasdaman.com/
    132      * EOX IT Services - http://eox.at
    133      * Landcare Research New Zeland - http://www.landcareresearch.co.nz/home
    134      * Università degli Studi di Ferrara - http://www.unife.it/unife-en
     110  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Open decision making process: [http://www.rasdaman.org/wiki/Features Feature table] is maintained on wiki, new features can be openly discussed on the mailing lists
     111 1. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Active and healthy community:
     112  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] The project should have a community of developers and users who actively collaborate and support each other in a healthy way: see [http://www.rasdaman.org/wiki/MailingLists list] archives
     113   i. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Committers listed on governance page: there are too many, and new ones coming in frequently, so we have automated this: http://www.rasdaman.org/patchmanager
     114  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations: http://www.rasdaman.org/patchmanager
    135115
    136116
    … …  
    141121  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/5/5a/Icons-mini-icon_accept.gif)]] A http://projectname.osgeo.org domain name (note: optional, not required by OSGeo)
    142122 1. A project may optionally request SAC help to make use of:
    143   a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] OSGeo issue tracker : not needed
    144   a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] OSGeo mailing list : not needed
    145   a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] OSGeo svn : not needed
    146   a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] http://downloads.osgeo.org : not needed
     123  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] OSGeo issue tracker : rasdaman tracker used instead: http://www.rasdaman.org/report
     124  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] OSGeo mailing list : rasdaman lists used instead: http://www.rasdaman.org/wiki/MailingLists
     125  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] OSGeo svn : rasdaman git used instead: http://www.rasdaman.org/browser
     126  a. [[Image(http://upload.wikimedia.org/wikipedia/commons/c/cc/Icons-mini-icon_accept.gif)]] http://downloads.osgeo.org : rasdaman download facilities used instead: http://www.rasdaman.org/wiki/Download
    147127