Agenda for Aug 25 meeting

[foolip]

Here's the agenda for our meeting tomorrow:

• Document the Interop 2023 proposals process for the public #115
  • More review welcome. Seeking consensus to merge as a starting point if no specific feedback.
  • Investigation efforts are not spelled out in this documentation yet. Make it prominent and ask contributors to pick, with a different issue template? Or mention it as an option and clearly not the main path?
• Create the Interop Team Charter #102
  • Updated to list the organizations (IETF, Khronos, TC39, W3C, and WHATWG) test suites (WPT) with no "etc.", but allowing for exceptions on a case-by-case basis.
  • Requirements for scoring results from Test262 #117
  • On "specification" vs. "standard", "specification" was kept as the broader term. Precisely what is considered a standard varies. WPT tracks "most up-to-date spec" in practice, whether WHATWG Living Standard or W3C Editor's Draft. OK to leave this wording alone?
  • On W3C Working Group vs. Community Group, discussed last week, but no change made. Clarify if consensus is "only WGs", "no CGs", or something else. Examples to consider: https://gpuweb.github.io/gpuweb/, https://webassembly.github.io/spec/core/, https://wicg.github.io/speech-api/
  • Big outstanding bit is a CONTRIBUTING.md.
• Expanding 2021 and 2022 focus areas for 2023 #119
  • FYI, no decision required today, please review
• Pending test change proposals:
  • Review html/semantics/forms/the-input-element/range.html #107
  • Remove css-scroll-snap/capturing-snap-positions.html  #108
  • Interpolation color space for gradients #109
  • Remove test relying on contain-intrinsic-size #112
• Investigation effort updates
  • Editing (@jgraham): https://github.com/web-platform-tests/interop-2022-editing
  • Pointer and Mouse Events (@flackr): https://github.com/web-platform-tests/interop-2022-pointer
  • Viewport (@bramus): https://github.com/web-platform-tests/interop-2022-viewport
    • Meeting 3 (2022-08-24) interop-2022-viewport#4 (comment)
    • Meeting 4 (2022-09-07)  interop-2022-viewport#20

Previous meeting: #110

[foolip]

Brief notes from the meeting. There was a miscommunication and nobody took notes live, so this is from memory.

Present: @bkardell @dlibby- @foolip @jensimmons @meyerweb @robnyman @tantek @una

We spent most of our time discussing the first two agenda items:

• Document the Interop 2023 proposals process for the public #115
• Create the Interop Team Charter #102

Investigation efforts

We still need to define how to propose investigation efforts in #115, but it's also clear we don't have clarity within the team exactly what kind of task could make sense for an investigation effort. The case in question is where we've identified something missing/wrong in a spec, should we accept tasks which amount to "work within the working group to resolve the spec issue during 2023." Writing tests is not controversial. We need to have @jgraham for this discussion, as the best advocate for investigation efforts, so we tabled it.

Standards track

For the charter we say just "specification", @foolip didn't know what exactly to write for each standardization org, requesting concrete wording suggestions to review. @jensimmons gave examples of what "standards track" would mean in the W3C and mentioned that @karlcow might be able to help. @robnyman will look at scheduling a meeting at a Japan-friendly time to go through both our public docs and charter.

Reviewing markdown

It came up that reviewing diffs of markdown is inconvenient, so I've just filed #120 to show how I do it.