-
-
Notifications
You must be signed in to change notification settings - Fork 112
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 Scheduling and Hosting Permissions for Bi-Weekly Design Meetings #1579
Comments
Definitely makes sense, especially that there are some folks in community interested to talk about design. Here is a doc about how to become meetings organizer: https://github.com/asyncapi/community/blob/master/MEETINGS_ORGANIZATION.md#how-do-i-register-for-a-new-regular-meeting At the moment we have TSC approval for 8 accounts on zoom, and all are occupied but not all are really used, so lemme ping folks so they can confirm if they plan to organize meeting in close future: do you folks still need AsyncAPI zoom account? |
@derberg you can definitely use mine for now as I dont plan to host anything in the near future ✌️ |
thanks @jonaslagoni @Mayaleeeee please open a PR to add your email (the one you will use with AsyncAPI Zoom) to https://github.com/asyncapi/community/blob/master/.github/workflows/create-event-ad-hoc.yml#L33 and remove |
Thanks for the update, @derberg I will open a pr for that later this week. However, for the meeting on Thursday, I'll reach out to @iambami to help schedule the meeting for me. |
Description:
We've been holding regular bi-weekly design meetings and want to keep that sequence. Our next meeting is planned for Thursday, November 21st, 2024, at noon UTC. To help streamline the process and avoid delays, I'd like to request the ability to schedule and host these meetings.
Why this Request?
Even though I'm hosting these meetings, I rely on others to start or schedule them. Having direct access would allow me:
Meeting Links:
Links to our previous design meetings can be found here and here.
Thank you!
The text was updated successfully, but these errors were encountered: