search

open-telemetry / community

OpenTelemetry community content
https://opentelemetry.io
Apache License 2.0
742 stars 226 forks source link

Back-to-back meetings on same zoom channel #824

Closed trask closed 2 years ago

trask commented 2 years ago

Hey all,

The new Instrumentation: Messaging SIG uses the same zoom channel as, and occurs right before, the Java SIG on Thu morning.

I think we were able to reset the recording this morning by having everyone log out and log back into the meeting, but would be great if we can avoid this.

Given the number of Thu morning meetings, maybe we need another Zoom room?

Thanks, Trask

mtwo commented 2 years ago

Shoot, yeah, with our current set of three Zoom rooms we can’t make any improvement. Given that we have two simultaneous meetings at 8:00 AM PT and three simultaneous meetings at 9:00 AM PT, we will need five Zoom rooms.

@amye is it possible for us to get two more Zoom rooms, or are we maxed out at three? If we're able to get more, shall I file a CNCF helpdesk ticket?

amye commented 2 years ago

Servicedesk please, someone will be able to look into this for you.

mtwo commented 2 years ago

Will do

From: Amye Scavarda @.> Sent: Thursday, September 2, 2021 1:05 PM To: @.> Cc: Morgan @.>; @.> Subject: Re: [open-telemetry/community] Back-to-back meetings on same zoom channel (#824)

Servicedesk please, someone will be able to look into this for you.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopen-telemetry%2Fcommunity%2Fissues%2F824%23issuecomment-912015071&data=04%7C01%7C%7C48fc044fd3a44893248f08d96e4cfb1c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637662099168797900%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=svT5sky7v7kqDtiW%2Fcdyt%2F4NEnIlpZzVRb2711UdFHk%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAIXLK2LNG6WERAY72QUAP3T77KHXANCNFSM5DJTS4DA&data=04%7C01%7C%7C48fc044fd3a44893248f08d96e4cfb1c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637662099168797900%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=i9SiQKihFgncY3pwZmWNcMYXEplzUYJ%2FxfA0O6vKBSE%3D&reserved=0.

SergeyKanzhelev commented 2 years ago

hm, we have 4 now: https://github.com/open-telemetry/community/issues/763

SergeyKanzhelev commented 2 years ago

I see, there are 5 meetings back to back or the same time

trask commented 2 years ago

@mtwo any update on this?

amye commented 2 years ago

Servicedesk.cncf.io is where this should be filed, we cannot track GH

mtwo commented 2 years ago

@trask apologies, this fell off of my radar until yesterday. Filing today.

mtwo commented 2 years ago

Looks like my service desk account was tied to my old work email address. I've put in a request to get an account tied to my personal email address, and I'll request the two Zoom rooms once I gain access.

mtwo commented 2 years ago

I'm in (thanks @amye)! Filed CNCFSD-937.

arminru commented 2 years ago

@mtwo Please make sure that the Zoom account host keys referenced in the document added in #618 still continue to work in case we have to mute or kick any Zoom bombers.

mtwo commented 2 years ago

Will do - currently investigating whether we can use a Google calendar integration for unique meeting codes. It turns out that the Kubernetes community is having the same challenge as us too, but so far they’re sticking with Zoom rooms and a very large number of Zoom accounts (same as what we do today).

From: Armin Ruech @.> Sent: Tuesday, October 5, 2021 8:07:27 AM To: open-telemetry/community @.> Cc: Morgan McLean @.>; Mention @.> Subject: Re: [open-telemetry/community] Back-to-back meetings on same zoom channel (#824)

@mtwohttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmtwo&data=04%7C01%7C%7C8d5a99c443e24b30666d08d98811d8e8%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637690432511445184%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=rqAprf4OzVb%2Bs1AYOuBFa6sUtMqLmZGGH7ENhO5wixY%3D&reserved=0 Please make sure that the Zoom account host keys referenced in the document added in #618https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopen-telemetry%2Fcommunity%2Fpull%2F618&data=04%7C01%7C%7C8d5a99c443e24b30666d08d98811d8e8%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637690432511445184%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=E9uyTXctxnTZ4NghUE67GlGS1DQ09Ss%2FJWnwj7RhSao%3D&reserved=0 still continue to work in case we have to mute or kick any Zoom bombers.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopen-telemetry%2Fcommunity%2Fissues%2F824%23issuecomment-934496007&data=04%7C01%7C%7C8d5a99c443e24b30666d08d98811d8e8%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637690432511455174%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=REmiAutAQUGuzSvRR%2FR4z8OVx1X%2F6rt3m6pI8hyUfwk%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAIXLK5QZRQVIV7BW7ZSXRTUFMIC7ANCNFSM5DJTS4DA&data=04%7C01%7C%7C8d5a99c443e24b30666d08d98811d8e8%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637690432511455174%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TRNCsnxSfZRb390rWJUshc4c9Po3rKt8Yo%2Bj1tdwfY4%3D&reserved=0.

trask commented 2 years ago

@mtwo checking in on progress, as this continues to be a problem on Thursday mornings, thx

trask commented 2 years ago

@mtwo bump, we continue to have problems on Thu mornings with back-to-back Messaging SIG and Java SIG meetings using the same zoom channel

mtwo commented 2 years ago

After a few weeks of testing (ensuring that simultaneous meetings work, etc.), I created a shiny new Google account for the project last night (it's tied to the GC mailing list) and I just finished generating unique IDs for each meeting!

This should now be fixed. I'm going to close the issue and I will remove the Zoom links in our community pages later today. Please ping me on Slack if a meeting doesn't work.