-
Notifications
You must be signed in to change notification settings - Fork 303
Minimum age requirement #799
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
remove extra spaces
fredericsimard
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
|
I hereby call a vote on this proposal. Voting will be open for 10 full calendar days until 11:59PM UTC on November 12. Please vote for or against the proposal, and include the organization for which you are voting in your comment. Please note if you can commit to implementing the proposal. |
|
Entur votes in favor and will implement it. |
|
FutureTap / Where To? votes in favor, too. We won’t implement it anytime soon, though. |
|
Voting on this PR closes in 2 calendar days. Please vote for or against the proposal, and include the organization for which you are voting in your comment. Please note if you can commit to implementing the proposal. |
|
AtB votes in favor as well, and will implement it 👍 |
|
NVBW votes in favor and will implement it. |
|
+1 from Transit. No plans to implement at the moment. |
|
This vote has now closed, and it passes! Votes in favor: Entur (producer) There were no votes against. This change will be part of the next MINOR Release, which is currently planned spring of 2026, as per the version release cycle in the governance. Thank you all for your involvement in the GBFS spec 🙏 |
**What problem does your proposal solve?
I'm doing this PR on behalf of @marius-at-atb in in Trondheim, Norway. Additional discussion can be found in #771 . They have a need for a field to contain a minimum age requirement in order to use a vehicle. There are potentially a number of user requirements that could be included in the
vehicle_typesfile, such as a drivers license, helmets etc but until we have real-world use cases my preference is to limit this to a single field that contains minimum age. In the future if there are additional needs beyond age we could develop a list of enums.If anyone has additional needs in this area I'd like to hear from you so we can include them before this goes to a vote.
What is the proposal?
This PR adds a single field
min_agetovehicle_types.json. The field is OPTIONAL and defined as a non-negative integer that describes the minimum age required to use the vehicle.This is a non-breaking change that would be included in the next minor version release scheduled for November.
Is this a breaking change?
Which files are affected by this change?
vehicle_types.json