Skip to content

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

Closed

Description

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions