This repository has been archived by the owner on May 21, 2024. It is now read-only.
Make it clear to contributors where to suggest new best practices #58
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Best Practice Proposal:
As outlined in google/transit#396, MobilityData and the community is working on merging best practices into the spec. While we work through each adoption phase, it needs to be clear to contributors where to go to suggest new best practices. Consolidating spec conversation on https://github.com/google/transit will help retain momentum and reduce confusion.
Solution
This PR adds a notice to contributors to go to https://github.com/google/transit/ to suggest new best practices. Please share feedback on the phasing plan at google/transit#396.