Web Conference 2022.04.19 Curb
- Every other week Tuesday call at 9am PT, 12pm ET, 5/6pm CET
Meeting ID: 898 5980 7668 - Passcode 320307
https://us02web.zoom.us/meeting/register/tZ0lcuCgrjwsHNyZRagmc86b12iCmWGBHfjq
One tap mobile: +13126266799,,89859807668#,,,,*320307# US (New York)
Dial by phone: +1 929 436 2866 (US) (Find your local number)
Main Topics
- Welcome (5 mins) - Jacob Larson, Omaha
- Resources and Help with CDS Implementation (10 mins) - Jacob Larson, Omaha
- Getting Started with Fleet Conversations (10 mins) - Jacob Larson, Omaha
- OMF Specification Release Process (10 mins) - Michael Schnuerle, OMF
- The Next CDS Release Planning (10 mins) - Michael Schnuerle, OMF
- Q&A (10 mins)
- Hosts: Jacob Larson, Omaha
- Note Taker: Elias Khoury, City of San Jose
- Facilitator: Michael Schnuerle, OMF
- Outreach: Angela Giacchetti, OMF
- 32 Attendees
-
Meeting Recording - Passcode:
eq25u15* - OMF Slide Presentation
- Leave your comments and new ideas for the next CDS release in Issues and Discussions
- Watch "What is GitHub?" video to understand how we work
9:02 AM Jacob Larson (City of Omaha), co-chair CDS Steering Committee: kicked off the meeting with brief discussion related to:
- Zoom meeting house keeping
- CDS overview
- Curb API
- Event API
- Metrics API
- CDS is open-source and seeks participation from private and public entities with members from both
- CDS release candidate 1.0 is complete and awaiting approval
- Presented a slide on who is currently using or planning on using CDS. Encouraged other entities to use and to indicate whether they are using CDS if their name is missing from the list
- Went over the available resources such as OMF website, blog posts, and Github including content related to policy language, Privacy Guidance, and Pilot Program Guide.
Michael Schnuerle (OMF) Director of Open Source Operations: Asked attendees about the available resources and if anyone thinks that something else is needed.
Ken Husting, City of LA: raised a question about APDS and how there is some unfamiliarity with CDS and whether the two standards or the two groups talking to each other.
Michael Schnuerle: stated that there are on-going talks between APDS and CDS for collaboration especially that APDS scope is more broad and related to general parking and does not address curb related standards in detail like CDS. He indicated that APDS is leaning towards referring to CDS when it comes to curb standards and its use cases. Will have a shared help document on this soon.
9:13 AM Jacob Larson (City of Omaha), co-chair CDS Steering Committee: discussed some of the work that was done at the City of Omaha related to the curb and how they outreached to companies and drivers to notify them about their pilot program. They compiled a list of delivery companies and worked with Automotus on a pilot related to delivery routes, problem areas, safety considerations, establishing zone locations, and providing locations to delivery companies and drivers.
Michael Schnuerle (OMF) Director of Open Source Operations: Asked Jacob whether they talked to delivery companies about CDS.
Jacob Larson (City of Omaha), co-chair CDS Steering Committee: responded that they are planning to engage them in the current phase of the implementation
Michael Schnuerle (OMF) Director of Open Source Operations: asked whether Jacob thinks that they will utilize CDS API’s.
Jacob Larson (City of Omaha), co-chair CDS Steering Committee: expressed his desire to accomplish that through agreements
Michael Schnuerle (OMF) Director of Open Source Operations: asked about the companies that they have been talking to.
Jacob Larson (City of Omaha), co-chair CDS Steering Committee: responded that they have been talking to Amazon, Sysco, and other local companies.
Michael Schnuerle (OMF) Director of Open Source Operations: asked if anyone has a follow-up related to this discussion
Akshay Malik (City of Philadelphia): shared that the biggest concern for delivery companies is when a reserved parking space is used by someone else. Can or does CDS plan to have a communication API or something in place to address or to communicate to the cities about it?
Michael Schnuerle (OMF) Director of Open Source Operations: explained that no code is in place around this. CDS can help address through data and setting defined policies and broadcasting occupancy. No communication layer is anticipated but will be open to discussion.
Elias Khoury, CDS Steering Committee board member, San Jose DOT: asked whether CDS will incorporate non-compliance/violation tracking at a minimum.
Michael Schnuerle (OMF) Director of Open Source Operations: pointed out that there is already an open and active discussion about this issue
Then there was brief exchange between Michael and Ashkay on how the challenge can be addressed such as companies providing the data about the violation.
9:28 AM Michael Schnuerle (OMF) Director of Open Source Operations: explained the OMF release process for future releases in detail and addressed the following:
- Release process is defined by the by-laws
- Presented the Release Cycle on a week by week, a process of 14 weeks
- Complete previous release
- Set goals
- Feature proposals
- Implementation and coding
- Decision and consensus
- Finalize release candidate
Then he presented a visual representation that included 4 checkpoints
- Plan
- Midpoint
- Consensus
- Review
He then presented Feature Evaluation Rubric for checkpoints with a scale 1 – 5 to be used for evaluation based on the following elements:
- Utility
- Adoption
- Simplicity
- Consensus
- Amount of work
Michael continued to present OMF structure for Release approvals and OMF Deliverable Approval Process including Working Groups, Technology Council, and Board of Directors.
The current release 1.0 is at the Board of Directors for approval, likely next week. He then proceeded to talk about the Release Process and the approval phases and timeline in number of weeks.
9:38 Michael asked if anyone has any question but none was received. Michael then proceeded to explain that decisions on future releases will be made. A decision would need to be made whether the future release is a major release such as 2.0 version or a minor release such as a 1.1 version. This will be discussed within the Working Group and the Steering Committee.
Michael the shifted everyone’s attention to Github. He presented the 3 open issues and encouraged participation on them:
- Alignment and connection to MDS
- Connection to USDOT and WZDX
- Open API/Swagger definition
He also pointed out the 5 open discussions on Github and encouraged participation and feedback. He also asked that ideas to be posted on Github such as goal setting and feature proposal ideas and needs. He then indicated that OMF is willing to provide tutorials on the use of Github if needed. Either on a one-on-one basis or in groups.
Brian Hamlin SDOT and Steering Committee board member: Thanked Michael for the presentation and indicated that SDOT is in the process of preparing RFPs to start work on the curb with CDS.
Michael Schnuerle (OMF) Director of Open Source Operations: shared Github screen that has the discussion page and provided some explanation on how it is used as well as discussion points and issues.
Asked if there are any questions. None were received.
9:49 AM the session was concluded.
