-
Notifications
You must be signed in to change notification settings - Fork 58
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
Documentation regarding the transition to WebM format (for videos) #338
Comments
Hi @vahidmas , I'm new to open source contribution. I would like to tackle this issue. You mentioned transitioning away from MP4—could you confirm if WebM is the new preferred format, or if there’s another format being adopted? Additionally, are there specific details about compatibility issues or tools to consider during this transition? Once I have these details, I’ll proceed with updating the documentation to provide clear guidance and address any potential challenges for users. Looking forward to your response! |
Hi @Mamatha1718! Yes, sure! I'll assign it to you! For purposes of clarity, please see additional guidance below;
We'll provide you with any additional clarification once you start on the issue. Thank you again. |
Hi @akolson, Thanks again for your guidance, and I look forward to getting started! |
Hi @Mamatha1718! I think the changes to the documentation need to be made here. cc'ing @rtibbles just in case. Be sure to let us know in case you have any additional queries. Thank you! |
Thank you for your response @akolson. |
Hi @Mamatha1718 I looks like you don't have any opened pr, could you please confirm this is not the case? Thanks |
Hi @akolson, |
Description
As the transition to using WebM (and sunsetting MP4) occurs, documentation needs to be updated. In particular, the Video Compression Tools guide needs an update to reflect the new preference/standard. The updates should include the caveats regarding browsers that will no longer be able to play videos, and mitigating actions users could possibly take.
What I Did
The text was updated successfully, but these errors were encountered: