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
We (MobilityData) are attempting to create a Public Backlog with the following goals:
Enable community members to view all GTFS addition ideas on a single page.
Allow community members to express interest and/or intent to contribute to these ideas.
Enable community members to see how many stakeholders are interested in each idea and who they are.
Enhance the transparency of MobilityData's decision-making process.
We hope that this public backlog will assist community members in deciding how to allocate resources. MobilityData will use the following factors, including information from this backlog, to prioritize ideas/features:
The geographical diversity of interested organizations. (E.g., interest from multiple continents/countries versus just one.)
The diversity of organization types. (E.g., whether the interest comes from trip planners, public transit operators (agencies or private companies), the public sector, etc.)
The potential riderships that would benefit from the feature.
The complexity of reaching consensus.
In the past, we attempted to use ProductBoard to capture community intent, but it lacked transparency and failed to provide tangible value to the community. We are now trying to build a public backlog using Airtable.
For more details on the purpose of this Public Backlog and how it aligns with the overall community goals, please refer to this detailed document.
Please feel free to share your thoughts or questions in this issue or in the document.
The text was updated successfully, but these errors were encountered:
tzujenchanmbd
added
Communication
General announcements to the community that do not involve specification changes.
Plan
Roadmap of a larger proposal that aggregates multiple specification changes into iterations.
and removed
Plan
Roadmap of a larger proposal that aggregates multiple specification changes into iterations.
labels
Sep 10, 2024
We (MobilityData) are attempting to create a Public Backlog with the following goals:
We hope that this public backlog will assist community members in deciding how to allocate resources. MobilityData will use the following factors, including information from this backlog, to prioritize ideas/features:
In the past, we attempted to use ProductBoard to capture community intent, but it lacked transparency and failed to provide tangible value to the community. We are now trying to build a public backlog using Airtable.
For more details on the purpose of this Public Backlog and how it aligns with the overall community goals, please refer to this detailed document.
Please feel free to share your thoughts or questions in this issue or in the document.
The text was updated successfully, but these errors were encountered: