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
Today we held our biweekly triage call (#9193) and I will post the meeting notes there in a bit. The next one is scheduled for May 18, 4 pm PDT. Note that this is 2 weeks later in an America+APAC friendly time.
People interested in attending the next call please respond here or reach out privately to me or the spec editors. We will be tagging issues for the next call again using the agenda+ label in all WHATWG repos and we would like to invite anyone that can contribute to said issues to join us.
The text was updated successfully, but these errors were encountered:
Olli brought to my attention that this instance falls on a holiday in several parts of Europe and I wonder if we will have broad enough participation for a useful meeting. @annevk are you still planning to attend?
Is anyone else from WebKit and Gecko planning to attend but hasn't RSVP'd already?
@past I never attend this time slot. @marcoscaceres and @nt1m might be there for WebKit. Perhaps they should be added to the recurring invite (though they have access to the relevant details either way).
I have received more declines since my previous comment and it seems we won't have any HTML spec editors attending or any of the people who suggested agenda topics, so I am going to cancel this instance and file the next one.
Today we held our biweekly triage call (#9193) and I will post the meeting notes there in a bit. The next one is scheduled for May 18, 4 pm PDT. Note that this is 2 weeks later in an America+APAC friendly time.
People interested in attending the next call please respond here or reach out privately to me or the spec editors. We will be tagging issues for the next call again using the agenda+ label in all WHATWG repos and we would like to invite anyone that can contribute to said issues to join us.
The text was updated successfully, but these errors were encountered: