-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2025 Q1 Face-to-face #1083
Comments
Howdy all! 👋🏼 Here's the When2Meet for this session. Pleas share your availability over the course of these three weeks with the understanding that we'd be best served by AT LEAST two separate two hour sessions. 📆 Separately, the WCCG will be having a it's December meeting on Tuesday December 16 at 7pm ET if you want to get in on an early pass on any of these topics. The WCCG intends to also have a January meeting before the face-to-face to continue preparation, so keep an eye out on this calendar or in Discord for more information as it gets scheduled. 🗒️ |
I would love for this to move along: "RESOLUTION: elementInternals.type='button' enables custom elements to get button-like semantics" |
@jpzwarte for the JS API outlined in the resolution, have you looked at adding any Web Platform Tests to support implementors in seeing the feature unfilled? Other than raising this as a priority, are there remaining discussion points to work through? |
I haven't, but that is definitely something i can take a look at. As far as open questions
|
Right now the two session for this are looking like they will fall on February 7th and 14th at 1pm ET. If you don't like how that sounds, be sure to share you availability to this when2meet. I'll look to add these sessions to the calendar by the 10th of January at the latest, so look at have your availability in before by Monday or so. |
Isn't 2/14 Valentine's Day? It might make it harder for people in Europe to attend it if we schedule it at 1pm ET on 2/14. |
@rniwa if you have some suggestions on people in Europe that we could tag in to ensure we get their availability included in the scheduling, please do! 🙇🏼♂️ It's difficult to speculative schedule, so working from what appears to be the best days/times from those who've shared their info to the when2meet feels like the best path forward. |
👋🏼 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: