-
Notifications
You must be signed in to change notification settings - Fork 234
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
Request for guidance: Collector SIG meeting timezones #2419
Comments
@svrnm any preference? 2 makes sense to me, but 1 seems good too |
I would prefer (1) over (2) -- we introduced that statement because we had non-PST meetings all over the place across different timezones and wanted to get some consistency. Here is another propsal:
This way we remove that admittedly arbitrary and very strict time blocks and SIGs can pick the timezone they prefer while remaining consistent |
I think the wording on Severin's last comment is the more sensible option. |
there's similar language at https://github.com/open-telemetry/community/blob/main/docs/how-to-handle-public-calendar.md#create-the-meeting:
|
In the repo readme, the following is stated about meeting timezones:
All Collector meeting times have been set to PT since most meeting attendees are in places where Daylight Savings Time is used. Since the notice conflicts with the meeting times, can we:
I think option 1 is sufficient, but want to get consensus. We could also change the one corresponding meeting time to fit this pattern, but I would prefer that the meeting time remains the same throughout the year for as many attendees as possible, which requires pinning to a timezone that uses DST.
The text was updated successfully, but these errors were encountered: