-
Notifications
You must be signed in to change notification settings - Fork 26
2020 01 15
Chris covered the IP rules and asked people to sign the observer agreement.
Co-chair vote.
Chris, Dave and Peng volunteered to chair.
NOTUC.
Proposed time scale — draft for Hong Kong and a set of additional capabilities beyond that.
Q: How much do we want to align with API Common?
A: We must align with OWS Common. API Common will be released for public comment soon. Since we are a little orthogonal, we don’t have THAT many dependencies and can continue rapidly. We will have a lot in common with API Features core but that’s a given we can build on.
Discussion — note the collections is a separate conformance class from the rest. We may have a different concept of “collections” and that is probably fine.
Dave B. Advocated to move quickly on a “part 1” that is point and time series.
Agreement to use GitHub: https://github.com/opengeospatial/Environmental-Data-Retrieval-API
Plan to have a face to face meeting at each TC.
Pete Trevelyan proposes a hackathon (some may refer to it as a sprint) between OGC TCs.
Proposed hackathon in Silver Spring (DC area) week of March 17
Call schedule:
Proposed every other week decisional meetings and opposite weeks for working meetings.
Chris will set up a doodle to determine timing: https://doodle.com/poll/hgzrediy2ugwdcd2
Process for document management.
All changes via Pull Request.
Those with “push” privileges may push some trivial changes.
Use “issues” to track discussion.
Notes / minutes.
Should we use GitHub Wiki?
Decision to use GitHub wiki like pyGeoAPI does. https://github.com/geopython/pygeoapi/wiki/Meetings
@dblodgett will set that up.
Do we want to use GitHub projects?
Only if we find a need for it down the road.
What about chat? Should we use gittr?
Yes. Will link in the readme.
How should we use the SWG email list?
For official SWG communications.
What about example implementations?
Should we follow: https://github.com/opengeospatial/ogcapi-features/blob/master/implementations.md ?
Things that intend to be conformant should go in the implementations page. More ad-hoc stuff would go in a wiki page.
@tomkralidis will do it.
Volunteers to edit document sections?
May be premature — we need some idea of what the sections are going to be.