Skip to content
  • Astrid Emde @aemde ·

    Mapbender ist ein OSGeo Projekt seit 2006. Damals inkubierte die Version 2.2.x (http://mapbender2.org/Template:Entwicklungsgeschichte). Das Projekt durchlief eine Qualitätsprüfung.

    Zum Vergleich hier Links zu zwei "frisch" inkubierten OSGeo Projekten OSGeoLive und PyWPS: OSGeolive

    PyWPS

    Project Graduation Checklist

    Based on the OSGeo Project Graduation Checklist version 2.0.

    Creation Date: 15 April 2018

    Last Updated:

    Overview

    This checklist is based on the Mapbender stable branch (release/3.0.6).

    Incubation Checklist

    Open

    The project has demonstrated that it has an open, active and healthy user and developer community:

    Copyright and License

    We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:

    • All project source code is available under an Open Source license
    • Project documentation is available under an open license (e.g. Creative Commons)
    • The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice (As per a Provenance Review).
      TODO review status
    • The project maintains a list of all copyright holders identified in the Provenance Review Document.
      TODO Copyright holders
    • All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. TODO

    Processes

    • The project has code under configuration management (Eg, subversion, git.)
    • Git: https://github.com/mapbender/mapbender-starter
    • The project uses an issue tracker and keeps the status of the issue tracker up to date
    • GitHub issues: https://github.com/mapbender/mapbender/issues
    • The project has documented its management processes. This is typically done within a Developers Guide or Project Management Plan.
    • Developer's Guide CONTRIBUTING.md: https://github.com/mapbender/mapbender-starter/blob/release/3.0.6/CONTRIBUTING.md
    • The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. 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.
      TODO ** [PSC] ** [RFC]
    • The project uses public communication channels for decision making to maintain transparency. TOD

    Documentation

    • The project has user documentation:
    • Including sufficient detail to guide a new user through performing the core functionality provided by the application. https://doc.mapbender.org/
    • The project has developer documentation:
    • Including checkout and build instructions.
    • Including commented code, ideally published for developer use. Examples: javadocs for Java applications, or Sphinx documentation for Python. TODO
    • Providing sufficient detail for an experienced programmer to contribute patches or a new module in accordance with the project's programming conventions.
      TODO

    Release Procedure

    In order to maintain a consistent level of quality, the project should follow defined release and testing processes.

    • The project follows a defined release process:
    • Which includes execution of the testing process before releasing a stable release
      • TODO
      • TEST procedure
      • Release procideure
    • 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.
    • Release and testing processes provide sufficient detail for an experienced programmer to follow
      • Everything is described in the release how to and approved by the PSC TODO

    OSGeo Committees and Community

    The OSGeo Foundation is made up of a number of committees, projects and local chapters. This section gathers up information these groups have requested from OSGeo projects. These expectations are not mandatory requirements before graduation, but a project should be prepared to address them in order to be considered a good OSGeo citizen.

    Board

    The OSGeo Board holds ultimate responsibility for all OSGeo activities. The Board requests:

    • A project provide a Project Officer as primary contact TODO
    • select a project officer Axel Schaefer
    • The Project Officer should be listed at Officers and Board of Directors and Contacts
    • This person is established when the incubation committee recommends the project for graduation
    • Your community can change the project officer as needed
    • Add an agenda item to the next board meeting so they can recognise the change of officer.

    Marketing

    Access to OSGeo's Marketing_Committee and associated Marketing Pipeline is one of the key benefits of joining the OSGeo foundation. The Marketing Committee requests:

    • Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee's Marketing Artefacts. This lists the documentation requirements for OSGeo-Live. Marketing Artefacts include:
    • Application
    • Application Quick Start
    • Logo
    • Graphical Image

    TODO/TBD: update/fix OSGeoLive

    • Ideally, stable version(s) of executable applications are bundled with appropriate distributions. In most cases, this will at least include OSGeoLive, but may also include DebianGIS, UbuntuGIS, and/or osgeo4w, ms4w, etc.)
    • Mapbender is available is pre-installed in OSGeoLive 11.0. and will be bundled with OSGeoLive 12.0 (July 2018).
    • Mapbender is also available for ms4w as additional project (Thanks to Jeff McKenna)

    Projects

    • Projects do not exist in isolation; and are expected to communicate and collaborate on key issues.

      • ? TODO Collaborations ?

    SAC

    The System Administration Committee is available to help with infrastructure and facilities. Information for this committee is collected as part of the Project Graduation Checklist.

0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment