Skip to content
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

Vote on setting March 10, 2024 as the cut-off date to implement v3.0 changes #598

Closed
richfab opened this issue Feb 3, 2024 · 2 comments
Closed

Comments

@richfab
Copy link
Contributor

richfab commented Feb 3, 2024

What is the issue and why is it an issue?

Many of you have expressed a desire to use v3.0, a more secure and intuitive version of the specification.

Please describe some potential solutions you have considered (even if they aren’t related to GBFS).

This is why we propose to set a cut-off date for producers and consumers to implement the last v3.0 changes. After this date, v3.0 would become the official version, with the features implemented by a producer and a consumer (with the “Official” label in the tracker).

There are 5 v3.0 features that currently do not have both a producer and a consumer. This means that if they are not implemented by a producer and a consumer before March 10, 2024, these features would have to be delayed to v4 in Novembre:

  • 🅿️ Geofencing made simple (#481) - missing a consumer
  • 🕐 Opening hours format (#328) - missing a consumer
  • ⌛ Timestamps format (#522) - missing a consumer and a producer
  • 🦄 Unified station capacity (#547) - missing a producer
  • 💵 Pricing per mile (#546) - missing a producer

If you’re interested in being a consumer/producer and make a feature official, please add it in a comment.

@richfab
Copy link
Contributor Author

richfab commented Feb 3, 2024

📣 Are you in favor 👍 or against 👎 setting March 10, 2024 as the cut-off date for producers and consumers to implement the last v3.0 changes (a year after the initial Release Candidate)?

We appreciate your feedback! Thank you for your involvement in GBFS 💜

@richfab
Copy link
Contributor Author

richfab commented Feb 22, 2024

Following the vote (0 vote in favor, 1 vote against), there will be no cut-off date to implement the v3.0-RC features at this time.

This gives you, producers and consumers, more time to implement the features that you’d like to see included in v3.0:

  • 🅿️ Geofencing made simple (#481) - Missing a consumer. Produced by Flamingo, TIER, Check and ENTUR.
  • 🕐 Opening hours format (#328) - Missing a consumer. Produced by Flamingo, TIER, Check)
  • ⌛ Timestamps format (#522) - Missing a consumer. Produced by ENTUR.
  • 💵 Pricing per mile (#546) - Missing a producer. Consumed by Transit App.

@richfab richfab closed this as completed Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant