• Combined working group call
• This meeting recording is here Password: xx?5bG%t
• Slides are available here
• Usually every other week call at 9am PT / 12pm ET

https://zoom.us/j/671331832

Meeting ID: 671 331 832

One tap mobile:

• +19294362866,,671331832# US

Dial by phone:

• +1 929 436 2866 (US)

Find your local number

Add your own name, link, and organization during call

• Michael Schnuerle, OMF
• Mark Maxham, Ellis & Associates
• Kegan Maher
• Neil Goldader, Ellis & Associates
• Henri Bourdeau, BlueSystems
• Anthony Anderson, City of Seattle
• Jonathan Internicola, NYC TLC
• Joanathan McIntosh, Ellis and Associates
• Sharada Strasmore, DDOT
• Joseph Yawn, Atlanta Regional Commission
• Sanjiv Nanda, SANDAG
• Brian Ng
• John Ellis
• Josh Johnson
• Sean Holman
• JR Heard
• Jean Koa
• Jane Huang
• Matt Davis
• Jascha Franklin-Hodge, OMF

1. Revised OMF Release Process
   • Goals
   • Timeline
   • Checkpoints
   • Governance PR #9 for feedback
2. Working Group Steering Committee member introduction
   • 5 members for each WG
   • Board approved
3. Release 1.0.0
   • Tech Council approved
   • to Board for review
   • anticipated release Sept 15
   • Release Plan
4. Looking to 1.1.0
   • Metrics/Reports, Compliance/Audit, Jurisdiction, Geography, Policy driven events
   • Will have a formal proposal time according to release process
   • Release Plan
5. Call for release ideas/proposals for your city/company in Github now.

Notes and or transcript of the call with presentation, document, GitHub links and calls to action

Release plan Q&A

• Sharada Strasmore (in chat): can the timelines/checkpoints be on the google calendar to help track
  • Michael: Good idea. Mostly the calendar has been for regular public events, but will look into it for Checkpoints.
  • JR Heard: Really like release plan page, which will be helpful in providing visibility into the process
• Sean Holman: This is great. Given the planning cycle and the length of this, what’s the flexibility for adopting and reprioritizing features that are in the plan?
  • It will change slightly. New process is having more planning, goal-setting, and feature proposals up front.
  • We’ve sometimes tried to squeeze things in at the end of the cycle.
  • Don’t know that it will happen us much, unless it’s something urgent, obvious, or not requiring a whole lot of discussion
• Sean Holman: Inevitably last minute things do happen.
  • If something came along weeks 8, 9, 10 that really needed to go in, we could use the flexibility in the timeline and push things out.
  • We could also shrink the timeline if we want to get to breaking changes in the next release.
• Kegan Mahar: None of this replaces the milestones on GH. Will still be tracking there.

WGSC

• Mark Maxham: Can we do a social meet-and-greet?
  • Yes let’s discuss planning an event at the WGSC intro meeting with Angela G

Support

• JR Heard: History of supported versions?
  • Michael: Support is currently patching typos and fixing things, providing documentation and guidance, and signalling from OMF on what versions should be supported.
  • Jascha: Desire to not have fragmentation, and to have a standard some cutoff is required. Discussion needed about the ‘supported’ language since we don’t technically support a release (eg, no 800 number).