pygeoapi
pygeoapi copied to clipboard
apply for OSGeo project status
As per https://lists.osgeo.org/pipermail/pygeoapi/2021-October/000203.html, it's a good time to move pygeoapi through the OSGeo incubation process. Becoming an OSGeo project will give the project a stamp of approval, help with long term health and sustainability, as well as provide the project some access to OSGeo budget.
pygeoapi is already an OSGeo Community project so our next step is entering incubation.
Steps (per https://wiki.osgeo.org/wiki/Incubation_Committee):
- Initial Application
- [x] Application request
- [x] Mentor volunteer (@msmitherdc)
- Incubator
- [x] Project Status: project details, and a few resourcing questions for the system admin committee (see Project Status Template)
- [x] Provenance Review: project team check to ensure the project is open source and has permission to distribute its source code.
- [x] Project team and mentor work on graduation checklist priorities
- Graduation
- [x] Mentor recommends project for graduation with motion to the incubation committee
- [ ] Committee chair informs the OSGeo board, who appoints the project team as a newly formed OSGeo committee
The pycsw and PyWPS projects provide examples from similar projects in our Geopython family.
Documentation is on Wiki at https://github.com/geopython/pygeoapi/wiki/OSGeoIncubation
- application submitted: https://trac.osgeo.org/osgeo/ticket/2651
- request sent to Incubation Committee: https://lists.osgeo.org/pipermail/incubator/2021-October/004422.html
@msmitherdc has graciously agreed to be our project mentor -- thanks and welcome @msmitherdc! I'm adding Mike as a collaborator to the project.
welcome @msmitherdc !
Hi all: update: our next step in the process is the provenance review. I've done a first pass in https://github.com/geopython/pygeoapi/wiki/ProjectProvenanceReview for review and comment.
@msmitherdc please let us know if this is suitable and what we should update.
@tomkralidis this looks like a very good start for the Provenance Review. Have you started contacting Copyright holders? That and fixing the few code headers and attribution and you look quite far along. Do you have a target release for getting these changes in?
Thanks @msmitherdc. Updates/questions:
- contribution agreements issue now filed in #928
- I've also added a Pull Request Template for contributions moving forward
- as far as other issues:
- [x] https://github.com/geopython/pygeoapi/issues/929
- [x] https://github.com/geopython/pygeoapi/issues/930
- [x] we have one file with magazine code: https://github.com/geopython/pygeoapi/blob/master/pygeoapi/util.py#L118. Not sure if/how this one needs to be resolved per se?
We are targetting 0.13 as our next release in the coming weeks.
Updates:
- OSGeo project officer selected (https://lists.osgeo.org/pipermail/pygeoapi/2022-August/000259.html)
- PSC approved to motion to graduate (https://lists.osgeo.org/pipermail/pygeoapi/2022-August/000267.html)
- @msmitherdc has made the motion to the OSGeo Incubation committee (https://lists.osgeo.org/pipermail/incubator/2022-August/004507.html)
Additional references:
- https://wiki.osgeo.org/wiki/Incubation_Committee#pygeoapi
- https://www.osgeo.org/projects/pygeoapi
Motion passed: https://lists.osgeo.org/pipermail/incubator/2022-August/004535.html
Next step:
- seek OSGeo Board of Directors approval
- forwarded to Board by @jodygarnett https://lists.osgeo.org/pipermail/board/2022-August/013088.html
- Loomio vote cast by @msmitherdc at https://www.loomio.org/p/XjpcFNvf?stance_token=942siJBuhnMpw5NgrGDsNWnY
- also added to agenda for next Board meeting: https://wiki.osgeo.org/wiki/Board_Meeting_2022-08-27#Current_items
Board vote complete; motion passed.
- https://www.osgeo.org/foundation-news/pygeoapi-graduates-osgeo-incubation
- https://twitter.com/OSGeo/status/1561434042007945216
- sent as news item to OSGeo announce as per https://wiki.osgeo.org/wiki/News_Queue#Submitting_News
So we can close, right?
Yes, we are now an official OSGeo project. Thanks everyone!