-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
TPAC 2020: HTML Standard meeting interest #5856
Comments
Here are a few things I'd like to discuss:
|
I'd like to discuss #6040 Which part of TPAC would these discussions take place in? It looks like there are are "Group Meetings," "Joint Meeting Week," and "TPAC Breakout week." |
I think we might be too late to join the official schedule, but I'm happy to set up a meeting similar to the TPAC Breakout week meetings early November. If it's just the three of us I'm not sure how much progress we can make though. |
See also WICG/webcomponents#877 |
@vmpstr and I would also like to attend. I am interested in the topics @zcorpan raised as well as the one @josepharhar raised. Timezone: North America for both of us |
If #6040 can't be scheduled on the 26th of the breakout week and is instead on the 27th-30th and I'm not available, it's no problem - @chrishtr and @vmpstr are on the same page as me about the feature and can go instead of me |
I think we missed the deadline (yesterday) to propose breakout sessions. I'll email dom to see if we can still add the ones discussed above. |
We have a breakout scheduled for 26 October 15:00–16:00 UTC: https://www.w3.org/2020/10/TPAC/breakout-schedule.html#whatwg |
Heads up that the breakout starts in ~20 minutes. I've created a Google Doc with relevant links, the agenda, and we can use this for meeting notes: https://docs.google.com/document/d/1fGGOXKC_zM7cYfdZYS3Ns3W2JpjaRwCRhP-5c32BV2s/edit?usp=sharing |
As discussed at whatwg/meta#171 we have the option to participate in W3C's TPAC.
If you're interested in meeting with HTML editors and the wider community please respond to this issue (or reach out privately) and indicate:
E.g.,
The text was updated successfully, but these errors were encountered: