You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 2020 MobilityData revised the GBFS Governance Process, since then we have noticed some elements of confusion and ambiguity. At the 2023 North American Workshop in New York City, we worked on a revision document to begin keeping track of all of things that need more attention.
MobilityData would like to open this discussion to the broader community for feedback. You can find the working document here that is open for comment. This document will remain the source of truth for changes until a PR is opened, and this issue is closed.
While the entire governance process is up for review, there are some key questions we would like some feedback on:
What should the conditions be for blocking a proposal? Currently, one person is able to block a proposal, should the threshold be higher?
The frequency of releases - We are seeing the official release v3.0 being blocked until a release and adoption v3.0-RC2 (and other changes in v3.0-RC), the release of v3.0-RC2 is blocked because more and more breaking proposals are being opened - which is great! That said, we would like to create a release timeline and release cycle that is predictable. We would like to propose distinct periods in which we accept proposals for a version, with a cut off date. The intention is for producers and consumers to be well aware ahead of time when a new version will be released, to help them better plan their work. Currently, MAJOR versions are released no more than once every 12 months. We propose to choose a specific date, for example the 1st of a chosen month, where at that point no more changes will be accepted, and the voting period begins for all remaining open PRs (and any required discussion periods). At that point, everyone can expect a MAJOR version to be released by the end of that month, every year. We would do the same with MINOR versions, say every 6 months, which would mean 2 releases a year, one MINOR and one MAJOR.
Please let us know what you think about these changes in this thread or in the document linked above! (Here again for your convenience).
Thank you in advance!
The text was updated successfully, but these errors were encountered:
In 2020 MobilityData revised the GBFS Governance Process, since then we have noticed some elements of confusion and ambiguity. At the 2023 North American Workshop in New York City, we worked on a revision document to begin keeping track of all of things that need more attention.
MobilityData would like to open this discussion to the broader community for feedback. You can find the working document here that is open for comment. This document will remain the source of truth for changes until a PR is opened, and this issue is closed.
While the entire governance process is up for review, there are some key questions we would like some feedback on:
Please let us know what you think about these changes in this thread or in the document linked above! (Here again for your convenience).
Thank you in advance!
The text was updated successfully, but these errors were encountered: