Agenda, Aug 17th 2023

[chrishtr]

1. Review Apple's proposal for the 2024 test selection process:
   Add a proposal for the Interop 2024 process #390

2. Review James's proposal for the proposal submission template:
   Update focus area issue template for 2024. #385

3. Charter approval
   Create the Interop Team Charter #102

4. Test change proposals
   https://github.com/web-platform-tests/interop/issues?q=is%3Aissue+is%3Aopen+label%3Atest-change-proposal

[chrishtr]

Action items:

• Sam to write two PRs and land them, to define the needs of 2024 feature proposals, and the timing for proposal submission
• James to finish a PR for the submission template
• Boaz to write a comms doc about 2024 announcements
• Everyone: continue commenting on the charter PR to help finish it off
• Everyone: review the above PRs

Notes:

Apple proposal:

James: open thoughts about how to do grouping. When should this grouping happen during the process?
Tim: it’s proposed to be the very last step.
James: think that might be a problem, because there is a step before that where each org pushes forward N proposals, but what if these proposals are of widely different sizes? Or if things will end up merged, why not vote on the merged list as a single item?
Sam: yes the tension is there. E.g. last year we ended up cutting down the scope of some areas during the selection process. (Or we might this year.) e.g. pointer events.
James: maybe we can give a number of points to each group?
Chris: maybe just remove the “N” number and expect organizations only to advance proposals that seem strong, not just pushing forward every single thing.
James: maybe that would be ok?
Sam: goal is to reduce work in round three, though admit any of the ideas has pros and cons.
Tim: these intermediate rounds are supposed to be fast, again in order to reduce work.
James: might end up with more again this year.
Chris: good point, we may not end up needing to filter a lot.
Sam: there is also the issue of carrying over issues from last year. If there are a number of them, that might reduce the space for new proposals.
James: it’s possible that 2023 features will increase their score quite a bit by December. OTOH each vendor probably knows whether they will be able to make that progress by EOY.
Chris: need to decide on the proposal template *and* the time period for the submission period asap. The rest can be debated if necessary later.
Boaz: think it would be good to have clarity.
James: won’t be able to provide full clarity on how we rank, but the factors need to be clear to proposal authors.
Sam: we can split out the stuff in PR 390 above process into a separate PR and land it.
Chris: suggest we land the first part of PR 390, plus as much of the list of dates as possible, ASAP. And discuss details of how to filter later.
James: suggest we commit to Nov 30 as our date for internally deciding in this group, and some other date to tell proposal authors.
Boaz: suggest that we be more clear in the public guidance about the fact that each company will create its own list of priorities based on the stated factors.
https://web.dev/submit-your-proposals-for-interop-2023/ happened last year, repeat that?
Chris: +1
We need new PRs for:
Parts of PR 390 that are consistent year-to-year (Sam will do it)
Announcing 2024 (Sam will do it)
Let’s try to ship these by the end of August. Sam will get it done right way so we can hopefully agree on these two PRs at the meeting next week.

Focus area issue template
Boaz: LGTM!
Chris: left some comments on the PR, seems good otherwise
Brian: LGTM
Dan: LGTM
Sam: just need to make sure it aligns with the other two PRs. Perhaps tweak wording to align also?
James: we should only land PR 385 when we are actually opening the proposal period (e.g. Sep 14 if that ends up the date)
Chris: any reason not to start before Sep 14?
Sam: not sure?
James: one reason not to go earlier is maybe vacations. Soft launching earlier seems find.
Boaz: we should have a doc with comms info for company teams working on that. And blog post timing recommendations?
Chris: A blog post as earlier as Sep 1 would be fine IMO. We can do an email thread coordinating.
Chris: back to James’ PR. Finish and get reviewed by next week, land when we want the issue template to be live.

Charter:
Dan: still discussing within Microsoft about whether to block on the public/private discussion point.
Dan: want to be make sure it says the right stuff.
Sam: also want to make an edit. Will go check with team and report back next time.
Dan will unresolve comments regarding suggested edits.

Test change proposals:
AI for everyone: go through the proposals and try to get consensus on them before next meeting.