Changes between Version 15 and Version 16 of Graduation List


Ignore:
Timestamp:
24 Mar 2018 07:28:24 (13 months ago)
Author:
kalxas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Graduation List

    v15 v16  
    7474
    7575* The project has developer documentation:
    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
     76  * YES: How to add a new project to OSGeoLive is covered in detail. Linked from: https://wiki.osgeo.org/wiki/OSGeoLive#How_to_add_a_project_to_OSGeoLive
    7777  * Including checkout and build instructions.
    78     * YES: Linked from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive</span>
     78    * YES: Linked from: https://wiki.osgeo.org/wiki/OSGeoLive#How_to_add_a_project_to_OSGeoLive
    7979  * Including commented code, ideally published for developer use. (Examples: javadocs for Java applications, or Sphinx documentation for Python applications.)
    80     * YES: Code is primarily relatively small shell script files, which include comment.
     80    * YES: Code is primarily relatively small shell script files, which include comments.
    8181  * Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.
    82     * YES
     82    * YES: We accept Pull Requests on GitHub and Gitea https://trac.osgeo.org/osgeolive/wiki/Source_code
    8383
    8484
     
    8989* The project follows a defined release process:
    9090  * Which includes execution of the testing process before releasing a stable release.
    91   * The project has an established build and release process, but it needs to be more clearly documented. Some information here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Build_Process . The release management role is well established, but not documented. This includes setting up a schedule, sending out press releases, chasing up projects, etc, etc.
     91  * The project has an established build and release process, but it needs to be more clearly documented. Some information here: https://wiki.osgeo.org/wiki/OSGeoLive_Build . The release management role is well established, but not documented. This includes setting up a schedule, sending out press releases, chasing up projects, etc, etc.
    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   * 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
     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, and documented on [[OSGeoLive Testing Process]]
    9595
    9696* Release and testing processes provide sufficient detail for an experienced programmer to follow.