Web conference notes, 2022.01.20 (MDS Working Group)

MDS Working Group

Zoom Registration Link: https://us02web.zoom.us/meeting/register/tZAscOmhpjIuHNakPx6CNbACpjUjw1Gsucr4

One tap mobile: +19294362866,,84170989462#,,,,*612987# US (New York) - though we encourage Zoom

Attendees

Note: Attendees register upon entry into the Zoom meeting. An attendee count will be posted here after the meeting:

26 Attendees

Main Topics

Kickoff - Sébastien Berthaud, Blue Systems
MDS Working Group Task Forces - Michael Schnuerle (OMF) and Task Force Members
- Modes Architecture Task Force
- Policy Reimagining Task Force
- Unification Task Force
OMF announcement: Curb Data Spec launch next week - Angela Giacchetti (OMF)

WGSC Meeting Organizers

Go to Wiki pages for each Task Force you're interested in, and join the mailing list!

Important items to consider for MDS 2.0:

Increase adoption of latest MDS by cities to make it easier for providers
Encourage more provider participation in working group since MDS features impacts them a lot
OMF possibly shepherd more open source tooling to help with MDS adoption and use by cities and providers
Refine MDS, not expand with new features
- 2.0 is doing this with focus on: 3 modes already in use in multiple cities, policy changes to make it clearer, and unifying disparate APIs
Get commitment to real use of new MDS releases by operators, cities, companies
- Maybe an OMF Upgrade Cohort to get buy in up front and help each other with upgrading

MDS 2.0 Goals

Task Forces

Task Force Slides
The scope is expansive, and while the WG has made progress on all items at previous meetings, the WGSC has created three Task Forces to work on each of the three items simultaneously. This allows members of the WG to also dedicate time to the topics they are interested in. We have precedent for this: API Reconciliation and Working Group Operations
WGSC members have volunteered to lead and organize the Task Forces. Each Task Force has its own mailing list, Zoom meeting room, and wiki page. WGSC to decide how full WG meetings will be utilized. Could be report outs from each Task Force or deep dives into individual topics.
Modes Architecture: Sanjiv Nanda & Alex Demisch co-leading
Policy Reimagining: Jean Kao & Sebastien Berthaud co-leading
API Unification: Marie Maxham leading

Discussion

William: In order for 2.0 to be successful, we need to maintain an eye on ease of implementation. How can we ensure this at the design phase? Need operator representation. Task Forces should be allowed to focus on technical work, and Working Group can serve as a counterbalance. We need greater operator participation, particularly for new modes.
Angela/Michael: We've implemented additional processes/tools to consider implementation, e.g., Member Networks, feature evaluation rubric, establish outreach role in WGSC for each meeting's topics
William: In contrast to GBFS, MDS has many features in recent versions that haven't been implemented. We need to shift burden of proof back on ourselves. Perhaps ease of implementation should be a design goal for 2.0.
Michael: Many features have been brought into MDS because forks already exist. We're focusing on taxi/ridehail, delivery robots, and car share as new modes because MDS is already being used for them in the wild.
Marie: Providing new tools can help adoption.
Brandon: We should also keep a focus on refining existing features rather than expanding features.
Josh: Cities determine MDS requirements for operators through permits, so they drive development priorities for operators.
Group agreed that implementation is a challenge, and that greater operator participation is needed, as well as commitment to real use (both on the city and operator side).

omf-mds-github-footer