Introduce SV-NNNN numbering convention for vision documents#3359
Open
stmontgomery wants to merge 1 commit into
Open
Introduce SV-NNNN numbering convention for vision documents#3359stmontgomery wants to merge 1 commit into
stmontgomery wants to merge 1 commit into
Conversation
Introduces 4-digit ID prefixes for vision documents, matching the convention used by proposals/. Since existing GitHub links point to the unversioned filenames, the original files are left in place; each new file just carries the title and a note redirecting to the original.
FranzBusch
reviewed
Jul 16, 2026
FranzBusch
left a comment
Member
There was a problem hiding this comment.
Thanks for raising the PR. Will discuss it in the next ESG meeting.
This file contains hidden or 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This introduces 4-digit ID prefixes of the form
SV-NNNNfor vision documents, to retroactively number them matching the convention used by proposals (in theproposals/directory).Since there are likely many existing links pointing to the unversioned filenames, the original files are left in place; each new versioned file just carries the title, its new ID, and a note redirecting to the original.
I chose the ID numbers based on the date each vision document was first added to the repo:
I also added a description of the new document formatting details to the process documentation.