# NGINX Community Call

**URL:** <https://community.nginx.org/t/nginx-community-call/9520>\
**Category:** Events\
**Tags:** community-call\
**Created:** [May 19, 2026, 9:33pm UTC](https://community.nginx.org/t/nginx-community-call/9520 "2026-05-19T21:33:53Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![heo](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/heo/32/5_2.png) [@heo](https://community.nginx.org/u/heo)\
**Post date:** [May 19, 2026, 9:33pm UTC](https://community.nginx.org/t/nginx-community-call/9520/1 "2026-05-19T21:33:53Z")

</div>

**We’re launching quarterly NGINX Community Calls and invite you to join the first call in July!**

These quarterly, public meetings are an opportunity for direct collaboration and transparent development for users, contributors, and the NGINX team.

All experiences levels are welcome, and beginners are encouraged to attend.

🗓Wednesday, July 22, 2026  
🕘 9:00am PT / 12:00pm ET / 17:00 GMT

> **Call Agenda:**
> 
> 1. Introduction, Welcome
> 2. Community announcements
> 3. Roadmap discussion
> 4. PRs, Issues discussion _(bring a PR/Issue you’d like to discuss!)_
> 5. Bring Your Config / Q&A

> **Event**
>
> **Starts:** July 22, 2026, 12:00pm (America/New\_York)\
> **Ends:** July 22, 2026, 1:00pm (America/New\_York)\
> **Location:** https://f5.zoom.us/j/91031737379?pwd=l0wQEELYVVtW0baiBfsCWWw3rAspTm.1

> You can add the event to your calendar by selecting the three dots on the module above and selecting “add to calendar”.

Zoom Link: [Launch Meeting - Zoom](https://f5.zoom.us/j/91031737379?pwd=l0wQEELYVVtW0baiBfsCWWw3rAspTm.1)  
Meeting ID: `910 3173 7379`  
Passcode: `937314`

If you have questions or provide comments in advance, we’ll see your replies in the comments below.

Looking forward to seeing you there!

---

<div class="post-metadata">

**Author:** ![heo](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/heo/32/5_2.png) [@heo](https://community.nginx.org/u/heo)\
**Post date:** [May 20, 2026, 12:04am UTC](https://community.nginx.org/t/nginx-community-call/9520/4 "2026-05-20T00:04:38Z")

</div>

Pinned globally on May 20, 2026, 12:04am UTC



---

<div class="post-metadata">

**Author:** ![robb\_fr](https://avatars.discourse-cdn.com/v4/letter/r/a6a055/32.png) [@robb\_fr](https://community.nginx.org/u/robb_fr)\
**Post date:** [May 21, 2026, 5:47am UTC](https://community.nginx.org/t/nginx-community-call/9520/5 "2026-05-21T05:47:09Z")

</div>

Hey, is it planned, as it was with the NGF call, to have both AMER friendly and EMEA friendly editions regarding the hours of the call?

Thanks!

---

<div class="post-metadata">

**Author:** ![heo](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/heo/32/5_2.png) [@heo](https://community.nginx.org/u/heo)\
**Post date:** [May 21, 2026, 3:38pm UTC](https://community.nginx.org/t/nginx-community-call/9520/6 "2026-05-21T15:38:29Z")

</div>

Thanks for asking! So far, we’re sticking with one call instead of alternating – the NGINX teams (and notably, the NGINX open source engineers) are in huge span of timezones. The NGF community calls are easier to alternate given the team split in the US and EU.

Would this scheduled time be a blocker for your participation? I’m taking note!

---

<div class="post-metadata">

**Author:** ![robb\_fr](https://avatars.discourse-cdn.com/v4/letter/r/a6a055/32.png) [@robb\_fr](https://community.nginx.org/u/robb_fr)\
**Post date:** [May 22, 2026, 11:16am UTC](https://community.nginx.org/t/nginx-community-call/9520/7 "2026-05-22T11:16:30Z")

</div>

Hello, thanks for your answer, this would of course not be a hard no (but of course, if there are alternative times in the future, that would be even better 🙂)

---

<div class="post-metadata">

**Author:** ![AJCxZ0](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/ajcxz0/32/3265_2.png) [@AJCxZ0](https://community.nginx.org/u/AJCxZ0)\
**Post date:** [May 27, 2026, 11:56pm UTC](https://community.nginx.org/t/nginx-community-call/9520/8 "2026-05-27T23:56:32Z")

</div>

How will you be engaging folks during the meeting?

- Allowed voice (and video) by host with raised hand
- Question posted to Q&A answered during the meeting
- Question posted to Q&A maybe answered at the end of the meeting when context may be lost, time is running out, and folks may have left
- Responses to chat from host(s) by voice
- Responses to chat from host(s) in chat
- Nothing. Shut up and pay attention.

I suggest making the rules of engagement clear before and again at the start of the meeting.

May we have an iCalendar/ics for our calendars?

---

<div class="post-metadata">

**Author:** ![heo](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/heo/32/5_2.png) [@heo](https://community.nginx.org/u/heo)\
**Post date:** [May 28, 2026, 1:47pm UTC](https://community.nginx.org/t/nginx-community-call/9520/9 "2026-05-28T13:47:57Z")

</div>

> [@AJCxZ0](#):
>
> I suggest making the rules of engagement clear before and again at the start of the meeting.

This is a great suggestion. Thank you! Setting expectations in advance is important.

It’ll be some variation of the top few bullets. Active discussion and dialogue is a driving intention for these calls so certainly not a “shut up and pay attention” dynamic. Community meeting, not webinar!

> [@AJCxZ0](#):
>
> May we have an iCalendar/ics for our calendars?

If you follow the three dots on the event module, it has an “add to calendar” option. Adding that in the top post for clarity.

 ![Screenshot 2026-05-28 at 9.32.43 AM](https://d7a5pgbt9tjl6.cloudfront.net/original/2X/e/eae04fb3eeffe3901e8dbabe5e68a550c7527bb6.png)

---

<div class="post-metadata">

**Author:** ![AJCxZ0](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/ajcxz0/32/3265_2.png) [@AJCxZ0](https://community.nginx.org/u/AJCxZ0)\
**Post date:** [May 29, 2026, 12:25am UTC](https://community.nginx.org/t/nginx-community-call/9520/10 "2026-05-29T00:25:18Z")

</div>

> [@heo](#):
>
> Community meeting, not webinar!

That is good to hear.

> [@heo](#):
>
> If you follow the three dots on the event module, it has an “add to calendar” option.

So it does. Thank you for pointing me to this.

---

<div class="post-metadata">

**Author:** ![heo](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/heo/32/5_2.png) [@heo](https://community.nginx.org/u/heo)\
**Post date:** [June 22, 2026, 9:41pm UTC](https://community.nginx.org/t/nginx-community-call/9520/11 "2026-06-22T21:41:35Z")

</div>

Hello everyone!

We are rescheduling the NGINX Community Call for July 22nd, to support personal circumstances for key NGINXers.

Thank you for understanding. Hope to see you in July!
