-
Notifications
You must be signed in to change notification settings - Fork 20
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
2024 Meeting Schedule #159
Comments
"June Week of 17-21" is over Juneteenth (Wed June 19), a US federal holiday. "October 12 & 14" is probably a typo for November? |
Change October 12 & 14 to November 12 & 14. |
We can slide the June meeting later? |
@michaelkleber, thanks for calling out Juneteenth.
I'm more constrained the week after - I have plans in Massachusetts starting Thursday afternoon, 27 June - but I have no reason to believe that's a conflict for others in the group. FWIW, I answered the survey based on the original dates. |
I am inclined to move off the week of Juneteenth because if we do have a meeting in the US, getting people to work to open the building up might be a challenge. I also am inclined to want slide the date farther away from the May meeting towards the September meeting because 5 weeks might not be enough time for people to progress. |
@seanturner given that the Feb meeting will not be F2F, what timezone do we intend to hold the virtual meeting in? |
Please check out the 1st post in this issue for an update to the proposed 2024 meeting schedule. |
The April date clashes with the AC meeting in Hiroshima. |
Alternatives for April
|
If you are listing options, then going ahead is still an option. We might not get any W3C team support and would have to check if anyone would prefer to go to Hiroshima instead. While it would be good to have team people involved and there is some risk of missing someone who prefers Hiroshima, that might still be a risk worth taking. |
Where are you planning to hold the f2f? |
A venue in Boston was the idea, apparently. |
The in-person meetings seem much better attended and to be much more productive. Yes, the travel is a burden but it's also quite a burden to attend a virtual meeting designed for a timezone that's not yours. I'm a little surprised to read there will be fewer f2f this year, but I didn't see the survey results. |
Hey Chairs, can you get this year's meetings listed on the official PATCG calendar? |
Okay let me get the Feb dates in at least. |
During the February meeting, there was a suggestion that we should have a meeting in July; there are a lot of weeks between May and September. This is breaks from our normal meeting pattern so we need to determine whether we would have enough participants for a productive meeting. Please fill out the following form to help us figure out when we might get the most participants; if you have any issuing filling out the form, please let the chairs know via email and we can make sure add your preferences to the entries. Also note that if we have this meeting, the timezone would be the "A" timezone (see top post) and we would change the November and December timezones to "B" and "C". |
Note that we decided to include a July interim and shift the November and December timezone. I will work to get the Calendar invites up. |
REVISED 20240610
We have revised the 2024 meeting plan for any number of reason. Please let us know if this vaguely works.
In 2024 we will continue to hold meetings, but more on an 8 week cycle skipping July. Review the meeting dates below and let us know if any of these dates clash with something else that the majority of you might be at. Note the Feb 6 dates actually clashed with a W3C European Member Meeting; see W3C Calendar.
We will continue to alternate timezones (with daylight saving time changes not being uniform around the world these times might shift one hour earlier or later depending on when the occur throughout the year):
The initial set of proposed dates are:
For a discussion about the location of the additional F2F meeting; see #160. We will strive to do Tuesday-Wednesday or Wednesday-Thursday so there is less chance of travel on a weekend.
We have decided (at the May meeting) to have a July virtual meeting. And, we decided to shift the November and December times from A & B to B & C)
The text was updated successfully, but these errors were encountered: