-
Notifications
You must be signed in to change notification settings - Fork 139
what is the state of this repository? #246
Comments
Selected content from the now old webrtc site will be ported to the new site in the next days. This includes a working security page, the unified plan transition guide, and a link to the release notes. Stay tuned. |
So we go from open source with the possibility to collaborate to closed source Google internal? |
@blum-webrtc it would have been great if @MirkoBonadei had been kept in the loop and had stopped me from wasting time on fixing the build. |
The SDP generated by WebRTC includes extensions with URLs to experimental features, for example:
Those links are now dead. I'd report it to Google, but I don't even know where such a thing could be reported? I assume the new website is now internal only? |
the /start/ linked from https://cocoapods.org/pods/GoogleWebRTC (which, along with its android counterpart would be great to update to reflect recent decisions) also 404s |
I've been staying tuned for a month now, can I stand down? Also note that @anatolid's release note template links to /bugs, not the fancy new url that still lacks bisect information. May I suggest rolling back? |
Fippo, thanks for letting us know about the broken link in the release notes! I edited the original post on discuss-webrtc and fixed the link. |
https://webrtc.github.io/webrtc-org/license/ilbc-freeware/ -- iLBC information is missing too. |
it looks like webrtc.org was updated. However, the new content looks like its missing a lot of things, including content updates in the last 12 months (in particular #229). Changelogs are missing, so are the protocol descriptions for various header extensions. The unified plan description/timeline page is AWOL too.
What is the plan?
Thankfully this page still gets deployed to gh-pages ;-)
The text was updated successfully, but these errors were encountered: