Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)

@rniwa agreed!

I'm not sure if there's a more official calendar than that of the [Web Components CG](https://calendar.google.com/calendar/embed?src=o25bim5rvcu42mfnqilirpmp44%40group.calendar.google.com), so I've added those events there:

- Monday, April 17th 12pm to 4pm ET ([link](https://calendar.google.com/calendar/event?eid=MHZpN29qc281bWVqazkzdHRqdW1nMmE0djIgbzI1YmltNXJ2Y3U0Mm1mbnFpbGlycG1wNDRAZw&ctz=GMT-04:00))
- Thursday, April 20th 12pm to 4pm ET ([link](https://calendar.google.com/calendar/event?eid=M3NpazkwNXFuZWRzY2JqNmhiZThkZnVwYWcgbzI1YmltNXJ2Y3U0Mm1mbnFpbGlycG1wNDRAZw&ctz=GMT-04:00))

I added the handful of people to the event on this thread who's contact info I already have, and would be pleased to do the same with the rest of you. The meetings are in a Google Calendar, so they always get associated to a Meet video call, happy to try to set up something else if that would preferable, but please let me know ASAP if some effort needs to be put into finding an alternate call strategy.

## Preparation

This leaves us with about 4 weeks until the sessions, and a lot of great topics to discuss. Here's a list of all the points from above (call me out if I've missed any):

- scoped custom element registries @mfreed7 
- Specific accessibility pain points and general roadmap planning around accessibility-focused features. @annevk 
  - Cross root aria
  - Other current proposals
- ElementInternals and ARIA Mixin @nolanlawson 
- Consider how every feature interacts with declarative shadow DOM, especially a11y @justinfagnani 
- Selection API @smaug---- 
- Web Components pain points in general. @annevk 
- declarative APIs (components, templates, data stores) @sashafirsov 
- Shadow DOM issues ([here](https://github.com/search?q=org%3Awhatwg+label%3A%22topic%3A+shadow%22+is%3Aopen) and [here](https://github.com/WICG/webcomponents/labels/shadow-dom)) @annevk 
- Custom Element issues ([here](https://github.com/search?q=org%3Awhatwg+label%3A%22topic%3A+custom%20elements%22+is%3Aopen) and [here](https://github.com/WICG/webcomponents/labels/custom-elements)) @annevk 

We could also draw further discussion from the [WCCG' 2022 report](https://w3c.github.io/webcomponents-cg/2022.html).

It would be most productive if we could get some "topic owners" (I've listed roughly who originally proposed the topic above) that could at least introduce the subject for discussion or possibly even gather some people for a pre-F2F-F2F/email threads so as to grease the skids of recent development and possible decisions. Thoughts?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/978#issuecomment-1466138136
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/978/1466138136@github.com>