The vote ended on 2021-12-16 at 23:59:59 UTC.
There were 11 votes in favor, and 4 opposed. With no unanimous decision in favour, the vote does not pass.
MobilityData will choose to continue working on the proposal to address outstanding bugs and concerns.Hi everyone, with the proposal updated based on the feedback we received over the past weeks - we are opening up the vote on PR #286!
This vote is for the base implementation of GTFS-Fares v2 as outlined in this pull request.
There are at least three producers:
And at least one consumer:
Transit App: https://transitapp.com/ (@gcamp)
Voting ends on 2021-04-04 at 23:59:59 UTC.
As posted in PR #286:
__________
The vote ended on 2022-04-04 at 23:59:59 UTC.
There were 7 votes in favor, and 2 opposed. With no unanimous decision in favour, the vote does not pass.
Here are the complete results:
+1:
Transit @jsteelz
OpenGeo @skinkie
UrbanLabs @e-lo
LA Metro @matikin9
Maryland @SteveGladstone
Ito World @davidlewis-ito
Actionfigure @caywood
-1:
Interline @drewda
MTC @jewel1965
We want to thank everyone for their efforts towards the development of GTFS-Fares v2. Even though the vote did not pass, we made incredible progress towards getting the extension officially adopted.
The amount of collaboration we got from the community was incredible; whether it is through GitHub conversations or on the roundtable discussions that we hosted. A special thanks to everyone who joined the roundtable calls - we understand the meeting times were not ideal for some since there was a 10 hour time difference between people on those calls.
We have noted the outstanding items that need to be worked on to reopen the vote - and we see that the scope of the outstanding work is narrower than ever.
That being said, MobilityData will choose to continue working on the proposal in Q2.
We are going to spend some time to strategize and plan our next steps for the base implementation of GTFS-Fares v2. We will provide an update in a week's time. As always, we are excited to continue working with the community to move GTFS forward.
__________
Thanks,
Scott
Hi everyone, with the proposal updated, and the conversations slowing down - we are opening the vote!
This vote is for the base implementation of GTFS-Fares v2 as outlined in this pull request.
There are at least three producers:
And at least one consumer:
Voting ends on 2022-05-16 at 23:59:59 UTC.
PR #286 here.
Thanks,
Scott
The voting period ended on 2022-05-16 at 23:59:59 UTC.
With 9 votes in favour and no votes against, the vote to extend GTFS with the base implementation of GTFS-Fares v2 passes! The votes came from:
- Transit App (@jsteelz)
- Interline (@drewda)
- Metropolitan Transportation Commission (MTC) (@jewel1965)
- Trillium (@westontrillium)
- Ito World (@davidlewis-ito)
- Maryland Transit Administration (@SteveGladstone)
- IBI Group (@philip-cline)
- LA Metro (@matikin9)
- Cal-ITP (@evansiroky)
It is great to see this pull request come to a close, and we are excited to see what is next for GTFS-Fares v2. We encourage you to continue the conversations on the future of this extension by opening GitHub issues as well as Pull Requests.
On our end, to keep momentum on the fares project, we are dedicating a workshop session at our International Mobility Data Summit in Montreal to discuss GTFS-Fares, and we look forward to seeing you there!