Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update community meeting frequency to fortnightly #16189

Merged
merged 1 commit into from
Jul 11, 2023
Merged

Update community meeting frequency to fortnightly #16189

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ Now it's time to dig into the full etcd API and other guides.

### Community meetings

etcd contributors and maintainers have monthly (every four weeks) meetings at 11:00 AM (USA Pacific) on Thursday.
etcd contributors and maintainers meet every two weeks at 11:00 AM (USA Pacific) on Thursday.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we have two times; One is the existing one, and the other one is an APAC or EMEA friendly time?

  • 11:00 AM USA Pacific (keep the existing one as it's)
  • Can we raise a discussion topic in etcd-dev and the etcd slack channel?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we want to do two different times for the meetings it might be difficult for @serathius who does the organising and video uploads to make it to both. We would need to make sure someone could run each one, it makes things a bit more complicated maybe.

In terms of the feedback from the community I think the main thing was the community wanted to meet more often to allow more time to discuss agenda items. If we have split meeting times then we won't actually be achieving the community feedback of meeting more regularly as there will still only be one meeting per month for each timezone and it is unlikely people will be able to make both timezones? We would probably need to make the meetings longer to achieve the goal in that case which isn't what the community wanted in the survey results.

We would also need to think about how duplication of discussions between regions is handled. If something is discussed at one meeting but only few people can make it, does it have to be discussed all over again at the other meeting and how does that impact decision making?

I'm not opposed btw, just want to make sure we think it through and deliver on the feedback the community gave us in the survey.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

feedback the community gave us in the survey

What's the feedback on the timezone in the survey?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here are the 11 exact responses we received, some people did not enter anything for this question:

PST/PDT
PST
India
GMT+2
PST
CEST
China Beijing
PDT
ET
NZST
EST

So the most common is PST/PDT with a scattering of others that make it impossible to have a time that works for everyone. The time we have currently can work for quite a few of us though:

image

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thx for the info. It isn't a big problem to me, but let's see other's feedback.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think good to merge this PR and continue checking if separate meeting is needed for the APAC / EMEA. If so, it will be good if we can identify someone from that region who can lead the call. Thanks!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree to submit the PR.

Also agree that we should have both AMER and APAC/EMEA friendly meetings. I can to run either or both meetings.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was looking at the time table again, how about we have Wednesday 11pm PST once/4 weeks and Thursday 11am PST once/4 weeks?

image

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it makes no sense to adjust the meeting based on guesses about user preference. Could we send a separate survey that will target users that cannot attend the meeting due to timezone. It should give us idea on how many they are and how to best accommodate them.


An initial agenda will be posted to the [shared Google docs][shared-meeting-notes] a day before each meeting, and everyone is welcome to suggest additional topics or other agendas.

Expand Down
Loading