-
Notifications
You must be signed in to change notification settings - Fork 3
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
Report a score to the overall Interop 2022 effort #10
Comments
Based on the previous meeting we can now update the total score to 36% (but we also have clear next steps to improve the score: each issue documents what's needed to make that happen). |
Is 36% complete still the correct score? |
We haven't had a meeting to formally update the score, but I'd say: So I'd suggest the overall score here is now 46%, but there are clear actions we could take (land the test PRs, review IME proposal, etc.) to further improve it. |
@foolip ^ |
Perhaps you could call it 48%, to make the math work out evenly for the overall Investigation score? |
Discussed in the interop team meeting today. We decided to update the score to 46% as of Nov 25. @foolip to send PR. |
I've sent web-platform-tests/wpt.fyi#3058. |
Will confirm in the last meeting, but it seems like the end of year score will be 52%. |
@jgraham from what date should we consider the score to be 52%? |
Assume from the 15th of December. There's actually a chance of even more progress by EoY, since @johanneswilm seems to have written some last-minute input event tests. |
* Interop 2022: update editing investigation score See web-platform-tests/interop-2022-editing#10 (comment) * Update webapp/static/interop-data.json
When you think it's fair to say the progress of this investigation effort is no longer 0%, please let us know so we can update https://wpt.fyi/interop-2022.
We have a score for Viewport now in web-platform-tests/interop-2022-viewport#22 (comment), and it'd be good to show progress in small increments, rather than going 0→100% at the end of the year.
The text was updated successfully, but these errors were encountered: