-
Notifications
You must be signed in to change notification settings - Fork 28
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
New introduction #132
New introduction #132
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The result of wordsmithing live in #131
@jensimmons @jgraham I made one additional small edit to merge the second paragraph. If either/both of you can review, feel free to merge this so the README is up-to-date when people start looking. |
Similar to [Interop 2022](https://wpt.fyi/interop-2022), this will be a public metric based on the progress of selected focus areas and investigation efforts. The overall timeline for the planning process is: | ||
Similar to [Interop 2022](https://wpt.fyi/interop-2022), the tests selected will be continuously run on automated testing infrastructure. The test pass rates for each browser rendering engine will be displayed on the Interop 2023 Dashboard — displaying the percentage of passing tests in each chosen area, and an overall total score. The dashboard will also display scores for group progress on particular Investigation Efforts selected for the the Interop team to work on throughout the year. | ||
|
||
Interop 2023 is tightly focused on technology that is already specified in web standards. This is not a place to invent new web technology, nor solve complex problems that need web standards. That work should happen in the standards bodies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interop 2023 is tightly focused on technology that is already specified in web standards. This is not a place to invent new web technology, nor solve complex problems that need web standards. That work should happen in the standards bodies. | |
Interop 2023 is tightly focused on technology that is already specified in web standards. This is not a place to invent new web technology; that work happens in existing standards bodies. |
Or I'm not sure quite what the second clause was trying to say that's different from the first. Maybe it was trying to make the distinction between really novel standards and major (non-interop motivated) changes to existing standards? If so perhaps "This is not a place to invent new web technology, nor make novel additions to existing specifications." (there are some edge cases there with investigate, but it probably doesn't matter).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the simplification of the first clause. Did you mean to suggest a semicolon though? IIRC you suggested it in the other place:
Interop 2023 is not a venue for specifying new features; that work happens in working groups within organizations such as W3C and WHATWG.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, a semicolon works.
Co-authored-by: jgraham <james@hoppipolla.co.uk>
Potential new introduction to help anyone who doesn't already understand what this project is.