Difference between revisions of "MoU OGC/Review 2020"
Tomkralidis (talk | contribs) |
Tomkralidis (talk | contribs) |
||
| Line 20: | Line 20: | ||
* https://wiki.osgeo.org/wiki/Open_Source_and_Open_Standards | * https://wiki.osgeo.org/wiki/Open_Source_and_Open_Standards | ||
| − | ==Current State (2020) == | + | ==Current State (2020-) == |
* Reference implementations/demos | * Reference implementations/demos | ||
Revision as of 18:32, 22 February 2021
Review Team
- Tom Kralidis
- Rob Atkinson
- Franz-Josef Behr
- Rajat Shinde
- Angelos Tzotsos
Introduction
Overview
At the OSGeo Board 2019 face-to-face meeting in Bucharest, one of the topics covered was the OSGeo / OGC Memorandum of Understanding. OSGeo and OGC agreed that it would be a good time to review and update the MOU as required to reflect current requirements and opportunities.
Purpose
The purpose of this activity is to analyze the current OSGeo/OGC MOU to articulate opportunities in support of a renewed MOU.
Scope
This activity is bound to the OSGeo/OGC relationship.
Background
- MOU circa 2008
- https://wiki.osgeo.org/wiki/OSGeo_signs_Memorandum_of_Understanding_with_OGC
- https://wiki.osgeo.org/wiki/Open_Source_and_Open_Standards
Current State (2020-)
- Reference implementations/demos
- OSGeo certification service
- 6 membership slots
- OSGeo Standards mailing list
- OSGeo participation in OGC
- OGC participation in OSGeo
- OGC API efforts and OSGeo implementations
Analysis
- OGC: increase in developer focus and engagement of software development community - collaboration via OGC API sprints - FOSS4G is beneficial to all/for all software
Opportunities
- aligned missions: FAIR data principles - developer focus - more sprints/cross pollination - OSGeo participation innovation projects - OSGeo representation vs. individual membership - OSGeo contribution to developer.ogc.org
Next Steps
Draft Exhibit A for review by OSGeo and OGC