-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Renaming of the repo to ffv1-specification #268
Comments
That would break all links and if we ever want to add something beyond the specification. Maybe some reference test files maybe some example code, whatever the name could be somewhat suboptimal |
GitHub handles the redirections :). I let this issue open in case there are comments from others then I close if not convinced. |
What is the oppinion of others ? (Feel free to just use the thumbs up/down thingies on the initial message to show your agreement disagreemnet if you have no further comments) |
IIUC github will manage a redirection, such as happened for https://github.com/matroska-org/matroska-specification. |
Just some administrative stuff: even if we don't move to IETF CELLAR working group, it may make more sense to mimic the names of the repositories, i.e.
ffv1-specification
for being clear in the name and not only in the description that it is the spec.The text was updated successfully, but these errors were encountered: