Changes between Version 10 and Version 11 of Graduation List


Ignore:
Timestamp:
03/24/18 04:07:58 (7 years ago)
Author:
kalxas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Graduation List

    v10 v11  
    44This page addresses the status of OSGeoLive as per version 2.0 of the [https://github.com/OSGeo/osgeo/blob/master/incubation/documents/graduation_checklist.pdf OSGeo Incubation Checklist]. It is derived from the [http://old.www.osgeo.org/incubator/process/project_graduation_checklist.html Project Graduation Checklist]
    55
    6 For the purposes of incubation auditing, the scope of the OSGeo-Live project comprises of the scripts and processes used to build OSGeoLive, but doesn't include the specific projects being packages (many of which are addressing OSGeo Incubation separately in their own right).
     6For the purposes of incubation auditing, the scope of the OSGeoLive project comprises of the scripts and processes used to build OSGeoLive, but doesn't include the specific projects being packages (many of which are addressing OSGeo Incubation separately in their own right).
    77
    88
    … …  
    2727* Active and healthy community:
    2828  * The project should have a community of developers and users who actively collaborate and support each other in a healthy way. ''Eg. collaboration on project activities such as testing, release and feature development.''
    29     * YES: A few hundred people have contributed to OSGeo-Live. Most contributions have been in writing application installer scripts, associated documentation, as well as translations. A list of contributors are at: http://live.osgeo.org/en/sponsors.html
     29    * YES: A few hundred people have contributed to OSGeoLive. Most contributions have been in writing application installer scripts, associated documentation, as well as translations. A list of contributors are at: http://live.osgeo.org/en/sponsors.html
    3030  * Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. ''Eg. The project is resilient enough to sustain loss of a developer or supporting organisation, often referred to as having a high [http://en.wikipedia.org/wiki/Bus_factor bus factor]. Decisions are made openly instead of behind closed doors, which empowers all developers to take ownership of the project and facilitates spreading of knowledge between current and future team members.''
    3131   * YES: Contributors come from a wide range of organizations (as seen by email addresses of contributors). Sponsoring organizations are also listed at:  http://live.osgeo.org/en/sponsors.html
    … …  
    4747
    4848* All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.
    49   * YES: All contributors have publicly accepted the terms of the OSGeo-Live license. This is archived in the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeo-Live email list]. The process is described here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion
     49  * YES: All contributors have publicly accepted the terms of the OSGeoLive license. This is archived in the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeoLive email list]. The process is described here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion
    5050
    5151
    … …  
    7474
    7575* The project has developer documentation:
    76   * YES: How to add a new project to OSGeo-Live is covered in detail. Linked from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive
     76  * YES: How to add a new project to OSGeoLive is covered in detail. Linked from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive
    7777  * Including checkout and build instructions.
    7878    * YES: Linked from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive</span>
    … …  
    9292
    9393* The project follows a documented testing process. (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.)
    94   * OSGeo-Live is an integration project, which is difficult to create automated testing for. Instead we rely on manual testing. The testing process is well practiced, but needs to be documented better
     94  * OSGeoLive is an integration project, which is difficult to create automated testing for. Instead we rely on manual testing. The testing process is well practiced, but needs to be documented better
    9595
    9696* Release and testing processes provide sufficient detail for an experienced programmer to follow.