-
Notifications
You must be signed in to change notification settings - Fork 232
Web conference notes, 2020.06.11 (City Services WG)
Michael Schnuerle edited this page Jun 11, 2020
·
30 revisions
- Every other week call at 9am PT / 12pm ET
Meeting ID: 671 331 832
One tap mobile:
- +16699006833,,671331832# US (San Jose)
- +19294362866,,671331832# 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
Add your own name, link, and organization during call
- Henri Bourdeau, Blue Systems
- Michael Schnuerle, OMF
- Neil Goldader, E&A
- William Henderson, Ride Report
- Bill Dirks, Ride Report
- Eric Mai, E&A
- John Ellis, E&A
- Michael Durling, E&A
- Jane Huang, E&A
- Sean Holman, E&A
- Thibault Castagne, Vianova
- Sharada Strasmore, DDOT
-
Reconciliation Naming Options - PR #506
- Consensus reached: on_trip (vs trip) and non_operational (vs unavailable)
- Final PR in progress
- Notes - agreed it's ready for final review
-
Policy: Adding Rates - PR #484
- Addressed issue #472
- Propose that it is ready to go for 1.0.0 with minor changes
- William at Ride Report can be spokesperson
- Mike McDonald from Portland said it was close to what the city could use
- Notes - See comments and reply
-
Audit API - PR #483
- Link to slides
- Is this duplicative of #326?
- Why add it to MDS? This moves away from the core MDS role about Provider-Agency communication.
- Should it live in a separate repo? (e.g. part of mds-compliance-mobile)
- Notes - See comments and reply
-
Docked - PR #430
- Inclusion of docked micromobility stops - w/o history for 1.0 and marked as beta.
- Issues #374 #427 #438
- Related PRs #427 #442 #441
- Open Questions:
- How much information to return about vehicles at the Stop? A few options proposed so far:
- Returning a list of Vehicles (with same type of information that would be contained in a
/vehicles
response payload) - Returning a list of
vehicle_ids
which contain UUID pointers to vehicle entries you can fetch from the/vehicles
endpoint. (recommend this to avoid duplication)
- Returning a list of Vehicles (with same type of information that would be contained in a
-
lat/lng
vs GeoJSON Feature (lean towards feature to accommodate large areas). Define buffer to account for GPS inaccuracy? - Keep the Provider and Agency PRs separate, or consolidate into one with shared data definitions as much as possible? (recommend consolidation)
- How much information to return about vehicles at the Stop? A few options proposed so far:
- Notes - See comments and reply
-
Policy: Address unknowns related to change management - Issue #517
- Discuss issue, identify next steps to develop a potential proposal
- Give feedback on issue, likely for 1.1.0
- Notes - See comments and reply
-
Release 1.0.0 timing and feature inclusion
- Draft notes via PR here
- Move from June 15 to June 29
- Proposed for 1.0.0
- Proposed for next release (1.1.0) after discussions
Notes and or transcript of the call with presentation, document, GitHub links and calls to action
- See inline Notes at the end of each topic for details
MDS Links
Working Groups
2.1.0 Release
0.4.1 Release Planning Meetings