-
Notifications
You must be signed in to change notification settings - Fork 61
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
repo name nit: it'd be nice if this were simply w3c/mediacapture #1003
Comments
That sounds appealing. I assume we have a way of doing so without breaking old links? I do notice that for https://w3c.github.io/webrtc-pc the TR version is named https://www.w3.org/TR/webrtc So that might be another option. I wonder why we didn't do that there. @dontcallmedom do you know? |
To clarify, today we have:
Is the proposal to change all (or just some) to:
? |
This issue had an associated resolution in WebRTC Interim, May 21st – 21 May 2024 (Issue 1003: repo name nit: it'd be nice if this were simply w3c/mediacapture):
|
the reason the shortnames aren't aligned is historical; that being said, the cost of renaming the repo isn't trivial since it requires creating redirects, updating a number of other projects (browser-specs, wpt, mdn bcd, …) - I'm not convinced this is worth doing at this point. |
I'd also not have suggested this because I think it's more work than it's worth. But if the people who suggested this renaming are motivated enough... Maybe the inverse is easier? Maybe you could create https://w3c.github.io/mediacapture and have it redirect to https://w3c.github.io/mediacapture-main? (Just a thought.) |
FWIW, Google search for link:https://w3c.github.io/mediacapture-main claims that there are around 5.740 links around the Web to the github.io version of the spec. So the redirects will have to stay around forever. |
given the expected cost/benefits ratio, we're no longer proposing to proceed with this |
No description provided.
The text was updated successfully, but these errors were encountered: