Web conference notes, 2020.03.26 (Provider Services wg)
Web conference notes, 2020.03.26 (Provider Services wg)
- biweekly call at 11am PST / 2pm EST
- Join Zoom Meeting https://zoom.us/j/627957166
Meeting ID: 627 957 166
One tap mobile:
- +16699006833,,627957166# US (San Jose)
- +19294362866,,627957166# US (New York)
Dial by your location:
- +1 669 900 6833 US (San Jose)
- +1 929 436 2866 US (New York)
Find your local number: https://zoom.us/u/aeJWJsuC2b
- Kegan Maher, City of Santa Monica
- Mark Maxham, Ellis & Associates
- Jascha Franklin-Hodge, Open Mobility Foundation
- Matt Davis, Populus
add your name at beginning or end of call
-
0.4.1 Release Candidate check
-
Current release cycle check
-
OMF Architectural Landscape document update
-
WG Operations versioning update
-
Provider/Agency reconciliation update
Tech Council working on finalizing review and recommendations to send to OMF Board probably the week of April 6.
Current Bylaws state that review can take up to 60 days once Tech Council has made recommendation.
Vote will be scheduled once recommendations have been made, and Jascha will share out information to wider OMF community.
Please submit issues/ideas/questions (even if not fully baked) as we will derive the agenda for the Working Group calls from suggestions on GitHub.
OMF Bylaws define the concept of this document - substantial piece of work intended to set the direction of OMF in terms of:
- what are we building?
- how are we building?
- how are we architecting to interoperate and reflect contribution of broad community?
Hybrid of product/tech strategy document.
IBI group has been leading work on development, interviewing stakeholders, etc.
Tech Council has reviewed, OMF Board has received a draft and most of their feedback has been submitted.
Not yet definitive approval date, but potential to be approved at the next OMF Board meeting next week (April 1). Should be finalized in April or May.
Once finalized, the document will be shared with broader community.
Long running discussion, general consensus that we should be using SemVer as intended.
Upcoming changes will be "MAJOR" enough that we should move to 1.0.0 for the upcoming release.
Milestones, Wiki, etc. will be updated accordingly.
Adam from Uber proposed the "Big Bang" change to rename/align events/statuses across the various APIs.
Goal was to have constituencies from City, Provider, and Tooling companies involved in the process, reps from each have participated in all planning calls and submitted comments.
Look for PRs for Provider, Agency, and potentially Policy in the coming weeks.
