Agenda for Oct 27 meeting

[foolip]

Here's the agenda for our meeting on Thursday, Oct 27:

• Longer meetings (previously discussed but not decided)
• Positions spreadsheet
  • OK to make this public via GitHub comments?
• State of CSS 2022 preview (requires password, will be shared in private)
• MDN short surveys design #196 preview:
  • https://survey.alchemer.com/collab/7081564/MDN-Interop-2023-CSS-HTML
  • https://survey.alchemer.com/collab/7081727/MDN-Interop-2023-APIs-JavaScript
  • OK to launch on Friday and run for 1 week?
• Update grid/flex test-suites for 2023 #242 (background: Expanding 2021 and 2022 focus areas for 2023 #119)
• FYI: Clipboard API: SVG and custom types #241 split from Clipboard API #143

Previous meeting: #229

[nairnandu]

Brief meeting notes

Attendees: @bkardell @dlibby- @foolip @gsnedders @jensimmons @jgraham @meyerweb @nairnandu @nt1m @tantek

[foolip@] - Can we extend this weekly meeting to an hour?

• No objections - extend to an hour from the next instance onwards.

[foolip@] State of CSS survey will run till end of the month. 13k responses, as of now (more than the previous year)

• [jgraham@] Do we know when there will be an unbroken version of the results?
• Action Item - [foolip@] to ask Sasha for the raw data

[foolip@] MDN short survey design

• [foolip@] If we take the survey as designed, it is very narrow. 3 options were suggested - are we ok with any of the options?
• [nt1m@] posted some feedback on the survey - some questions appear in both CSS and JS surveys (should be one or the other).
• [foolip@] Web components - where should this be placed?
• [jensimmons@] web components could go in JS one and CustomPaint in the CSS one
• [foolip@] If there is room for it, would it be ok to include in both?
• [jensimmons] 2 chances would be given to these items as compared to others. Prefer it to be separated
• [foolip@] Neural Network API - leave it out
• [foolip@] Color spaces -
• [nt1m@] WebGL is more color spaces
• [jensimmons@] Suggest doing this async. foolip@ can take the decision on wording. We need to get this done soon.

[foolip@] FYI - test change proposal

• [jgraham@] we should make a decision on moving any 2022 areas to 2023. It probably does not make sense to do that automatically. What would be the process to pull a focus area forward?
• [foolip@] Agree on creating a process. There is a list of grid and flexbox tasks - any objections with looking at it next year?Discuss next steps in the following meeting.

[foolip@] Positions process

• Need more discussion around this. Agreed to continue the conversation next time.