Open chrisn opened 1 year ago
@gregwfreedman @joeyparrish @xhwang-chromium We can schedule meeting time as needed to progress or triage issues, just let me know.
Since last WG meeting in late March 2023 , we triaged existing EME issues and added labels to them.
Since then we have not made much progress on closing the V2 issues.
We discussed about this briefly in yesterday's (March 16, 2023) WG meeting. It'd be great if we close out the V2 issues and make the FPWD available.
I have PRs up for most open issues in the V2 milestone, except:
Thank you! I think we can go ahead to request FPWD independently of those, so I'll raise a call for consensus.
Sounds good
SGTM
On Wed, Jun 5, 2024 at 9:59 AM Joey Parrish @.***> wrote:
Sounds good
— Reply to this email directly, view it on GitHub https://github.com/w3c/encrypted-media/issues/501#issuecomment-2150537725, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEVHVMJ777JRKTSQB2ZYIHLZF47XZAVCNFSM6AAAAAARWHAFQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJQGUZTONZSGU . You are receiving this because you were mentioned.Message ID: @.***>
Following discussion at TPAC 2022, this issue tracks the work needed to get to First Public Working Draft for EME v2.
We also have issues labelled as V2 and V2-Bugfixes, but my understanding is that publishing FPWD isn't dependent on these (aside from https://github.com/w3c/encrypted-media/issues/467).