Fill out the template for OSGEO graduation

[bermud]

https://github.com/opengeospatial/teamengine/wiki/OSGEO-Graduation

[dstenger]

https://portal.opengeospatial.org/wiki/CITEsc/CITEscTE2OSGeo

[dstenger]

Inform Luis as soon as finished.

[dstenger]

We have to differentiate between

• developers of TEAM Engine itself and
• developers of test suites.

I guess, both cases must be considered.

@bermud We should discuss this during the next meeting.

[dstenger]

TODO: Create an issue for all missing requirements.

[dstenger]

Open topics (we should discuss them and decide if issue is required):

• Open decision making process - OSGeo Graduation: Document and improve open decision making process #402
• License of user Manual - Apache Licence - Done
• The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included. - OSGeo Graduation: The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included #403
• The project maintains a list of all copyright holders identified in the Provenance Review Document. - OSGeo Graduation: The project maintains a list of all copyright holders identified in the Provenance Review Document #404
• All code contributors have agreed to abide by the project’s license policy, and this agreement has been documented and archived. - OSGeo Graduation: All code contributors have agreed to abide by the project’s license policy, and this agreement has been documented and archived #405
• Including commented code, ideally published for developer use. - We don't have commented code requirements because we prefer understandable class and method names. - Done
• Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project’s programming conventions. - OSGeo Graduation: Create documentation providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project’s programming conventions #407
• Which includes execution of the testing process before releasing a stable release. - OSGeo Graduation: Document testing process #406
• The project follows a documented testing process. - OSGeo Graduation: Document testing process #406
• Release and testing processes provide sufficient detail for an experienced programmer to follow. - OSGeo Graduation: Document testing process #406

[dstenger]

Issues are created in TEAM Engine issue tracker.

TEAM Engine itself shall become OSGEO project.

[dstenger]

Issues have been created.

[dstenger]

TODO: Add issues to graduation.
TODO: Work on issues.

[dstenger]

TODO: Create wiki page(s) to solve those issues.

[dstenger]

Report summarizing all open issues: https://github.com/opengeospatial/teamengine/labels/OSGEO-Graduation

[dstenger]

Focus on #402 first.

[bermud]

Have draft for 2019-07-15 for the decision process: #402.

[ghobona]

@tomkralidis @kalxas

The CITE SC session during the Virtual OGC Member meeting on June 19th, 2020 at 1:00 AM - 2:30 AM EDT will discuss the process and timeline for OSGeo graduation.

http://ogcmeet.org/events/2006tc/

[dstenger]

Open tasks:

• @dstenger is creating a pull request or wiki page for each open issue.
• @jodygarnett is reviewing those to confirm if all requirements by OSGeo are met.
• If required, further adjustments are made.
• Representative of OGC is reviewing the results as well.
• If required, further adjustments are made.
• Pull requests are merged.
• Final review of https://github.com/opengeospatial/teamengine/wiki/OSGEO-Graduation and submission of OSGeo graduation.