[Governance] A New Framework has been adopted - What's Next? - Discussion Thread
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 225
- Avg merge
- 7d 17h
- Merged PRs (30d)
- 3
Description
## Context
In July 2025, [we adopted the new GTFS Schedule Governance Framework](https://github.com/google/transit/pull/544) to bring more clarity, transparency, and structure to how GTFS evolves.
This framework reflects a pragmatic approach grounded in four key goals: stability, accessibility, predictability, and diversity.
### What’s new?
Key process changes:
- Formal Issue stage
- New Pull Request template
- Added Review and Voting Periods
- Updated voting requirements
- Clearer change types and processes
- Defined roles and responsibilities
This is a starting point—we’re opening a 6-month revision period and inviting your feedback to help refine it. Our long-term goal is to build a strong foundation for future updates, including the possible unification of GTFS Schedule and Realtime governances.
## Transition Period
- As of July 7, 2025, all new Pull Requests are subject to the new [GTFS Schedule Governance Framework](https://github.com/google/transit/blob/master/gtfs/Governance/introduction.md).
- Pull Requests opened before July 7, 2025 will continue to follow the [Former Governance](https://github.com/google/transit/blob/master/gtfs/Governance/CHANGES.md).
- This includes the following PRs: https://github.com/google/transit/pull/567, https://github.com/google/transit/pull/561, https://github.com/google/transit/pull/556, https://github.com/google/transit/pull/546, https://github.com/google/transit/pull/545, https://github.com/google/transit/pull/533, https://github.com/google/transit/pull/515, https://github.com/google/transit/pull/502, https://github.com/google/transit/pull/498, https://github.com/google/transit/pull/483, https://github.com/google/transit/pull/423.
- These PRs have also been attributed the label of: `Former Governance Applies`
- Once all PRs opened prior to July 7, 2025 are resolved, the [Former Governance](https://github.com/google/transit/blob/master/gtfs/Governance/CHANGES.md) will be fully deprecated.
## Revision Period
- The new GTFS Schedule Governance Framework is undergoing a 6-month revision period, so that the community can help fine tune it.
- We ask the community to use the comment section below to submit noticed frictions or issues they noticed when using the governance. This will allow us to collect valuable feedback and work collectively on an improvement.
- At the end of this period, we will communicate next steps here and / or host a meeting to assess the current state by identifying areas of improvement and their potential solutions.
## Ideas with considerable discussion and / or support
- #442
- #495
- #415
- #530
- Merging GTFS Schedule and GTFS Realtime Governances
## Ideas to be discussed
- Revising the Guiding Principals
- Experimental phase for proposals based on adoption
- Flexibility in 1 Consumer and 1 Producers testing requirements and depreciation of “small” unused fields
- Formalizing Working Groups
- Versioning and backward compatibility
- MDIP Certification / badging for contributors
- Deprecating Google Groups Requirement
Please feel free to submit any ideas you feel could improve the governance of GTFS. We will be sure to add them to this list.
Contributor guide
Assessment
This issue has not been assessed yet.