[Revision history] Move Schedule Revision history out of the spec amendment process and add the realtime revision history to this repo #467
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.
Problems with the revision history
We're reorganizing content on gtfs.org to enhance the user experience. The revision history will be placed in a new Technical Documentation section, and the Spec Amendment Process will be moved to a Community section, which will include information on how to participate. To achieve this, we need these to be two separate documents. Also, the revision history is actively maintained, while the Spec Amendment Process rarely changes, so having them in separate documents will make things clearer.
Solution included in this PR
This doesn't change the spec or its amendment process, so I believe a vote is not needed.