You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👋🏼 Howdy everyone, hope you're having a great day, week, November, Q4, etc., etc.!
At TPAC 2023, the Web Components Community Group resolved with implementors to have a "Quarterly Face-to-face", and through out the course of 2024, we had some great sessions in Q1, Q2 and at TPAC, as evidenced by the amazing progress happening across a number of highly important APIs and features; like Reference Target, Scoped Registries, and :has-slotted, et al. Be sure to check through how we did on action items from those meetings in these issues:
If any of those actions items have your name on them...you now what to do 😉
Let's keep up the pace and come together to structure the work we'll be addressing in 2025 with out next face-to-face (virtually, unless other wise desired) in Q1.
👀 ACTION ITEM 👀
If the last week on January/first week of February works generally, I can share a when2meet here to gather more precise availability. Happy to take alternative suggestions if there are specific individual or professional requirements already placed on those two week. Look for a when2meet around the 6th of December if there isn't any major push back to this time frame.
Keep in mind, we've seen that a minimum of two separate two hour session are what's needed to be fully productive with the amount of work we're looking to do, so keep that in mind while sharing your availability.
At current, we have about two months to clarify agenda items for the discussion, so please share your desires in that area below. There may be some lingering questions around the APIs shared above, so we can definitely prioritize anything that remains in those areas by that point. Hot button issues that might be good places to start:
Declarative CSS Module scripts
DOM Parts
style and theme APIs
HTML Module scripts, or
Declarative Custom Element
Make sure to get your burning desires into a comment so we can have a proper agenda well before to prepare attendees for highest productivity.
The text was updated successfully, but these errors were encountered:
👋🏼 Howdy everyone, hope you're having a great day, week, November, Q4, etc., etc.!
At TPAC 2023, the Web Components Community Group resolved with implementors to have a "Quarterly Face-to-face", and through out the course of 2024, we had some great sessions in Q1, Q2 and at TPAC, as evidenced by the amazing progress happening across a number of highly important APIs and features; like Reference Target, Scoped Registries, and
:has-slotted
, et al. Be sure to check through how we did on action items from those meetings in these issues:If any of those actions items have your name on them...you now what to do 😉
Let's keep up the pace and come together to structure the work we'll be addressing in 2025 with out next face-to-face (virtually, unless other wise desired) in Q1.
👀 ACTION ITEM 👀
If the last week on January/first week of February works generally, I can share a when2meet here to gather more precise availability. Happy to take alternative suggestions if there are specific individual or professional requirements already placed on those two week. Look for a when2meet around the 6th of December if there isn't any major push back to this time frame.
Keep in mind, we've seen that a minimum of two separate two hour session are what's needed to be fully productive with the amount of work we're looking to do, so keep that in mind while sharing your availability.
At current, we have about two months to clarify agenda items for the discussion, so please share your desires in that area below. There may be some lingering questions around the APIs shared above, so we can definitely prioritize anything that remains in those areas by that point. Hot button issues that might be good places to start:
Make sure to get your burning desires into a comment so we can have a proper agenda well before to prepare attendees for highest productivity.
The text was updated successfully, but these errors were encountered: