AsyncAPI Community Working Group Meeting, 15:00 UTC Tuesday February 11th 2025

[asyncapi-bot]

Meeting Info	Details
Purpose	Provide updates on the progress the builders are making on the different programs they're leading.
Time	15:00 UTC | Translate to your time zone with the time zone converter.
Meeting Place	Link
Zoom	Join live.
YouTube	Watch live and interact through live chat.
Twitch	Watch live.
Twitter	Watch live.
LinkedIn	Watch live.
More Info	Details
Meeting Recordings	YouTube Playlist.
AsyncAPI Initiative Calendar	Public URL.
iCal File	Add to your calendar.
Newsletter	Subscribe to get weekly updates on upcoming meetings.

Agenda

AsyncAPI Community Working Group Meeting:

The AsyncAPI Community Working Group is an umbrella for all community initiatives and programs at AsyncAPI. The CWG meeting aims to increase visibility and provide updates on the progress the builders are making on the different programs they're leading. These are the current initiatives and programs led by outstanding community builders:

• AsyncAPI Bounty Program - Ash
• AsyncAPI Grant Program - Thulie & Lukasz
• AsyncAPI Conference 2025 - Thulie
• Maintainership Program - Ace
• AsyncAPI Ambassador Program - Thulie
• Student Ambassador Program - Bami
• Working Groups - Bami
• AsyncAPI Website - Akshat

---

Objective: Provide updates on the progress the builders are making on the different programs they're leading.

1. Welcome and agenda alignment (3:00 PM - 3:05 PM) ➢ Facilitator: Thulie.
   ➢ Welcome all team members to the meeting.
   ➢ Briefly share the agenda of the meeting.

---

2. AsyncAPI Conference 2025 (3:05 PM - 3:25 PM) ➢ Facilitator: [Thulie]
   ➢ Conference website updates and tasks
   ➢ Call for Speakers for Singapore
   ➢ Call for Conference Sponsors
   ➢ Check with Akshat why the website banner is no longer on all the pages
   ➢ Plans to grow the conference beyond the main conferences

---

3. AsyncAPI Website (3:25 PM - 3:40 PM) ➢ Facilitator: [Akshat]
   ➢ Doc maintainers for the AsyncAPI website
   ➢ Can there be a better way to maintain the docs for AsyncAPI (that are shown inside the website)? (Need opinions regarding centralizing the docs, from docs contributor's perspective)
   ➢ Website Redesign and the dark theme (how much do you think it's critical for the website)
   ➢ Discuss with Bami how localization inside the website can be effective in catching the audience.

---

4. Program/ Initiative (3:40 PM - 3:55 PM) ➢ Facilitator: [Lukasz]
   ➢ New Governance Board chore: introduce governance board #1634
   ➢ 2025 Budget Budget 2025 #1681

---

5. Wrap-up, action items, and next steps (3:55 PM - 4:00 PM) ➢ Facilitator: Thulie
   ➢ AsyncAPI Bounty Q2 estimated to start March 2nd
   ➢ Summarize key decisions and action items from the meeting.
   ➢ Confirm the date, time, and agenda for the next meeting.

Notes

Add notes here after the meeting.

[thulieblack]

Hi @aeworxet @AceTheCreator @derberg @iambami @akshatnema, first community/wg meeting is happening in 2 weeks,. Please add your agendas and action items, things you'll like to be discussed.

[aeworxet]

I need to either announce or not announce the submission of GitHub issues for the Bounty Program 2025-Q2 on March 3. To make this matter clear, I need the 2025 budget to be TSC-approved before March 1. Is this possible?

Additionally, I would suggest adding to the vote on the 2025 budget the proposal to adopt this schedule for the budgetary process (maybe shifting the budgetary period from the calendar year to a fiscal year, though with reapprovals every six months, I don't expect this to be necessary).

[akshatnema]

Topics I want to discuss:

• Regarding the doc maintainers for the AsyncAPI website
• Website Redesign and the dark theme (how much do you think it's critical for the website)
• Discuss with Bami, how much localization inside the website, can be effective for catching the audience.
• Can there be a better way to maintain the docs for AsyncAPI (that are shown inside the website)? (Need opinions regarding centralizing the docs, from docs contributor's perspective)

[thulieblack]

A reminder to add your items by tomorrow!

[derberg]

I can do Q&A on budget if needed -> #1681

[thulieblack]

1. Conference website updates and tasks
2. Call for Speakers for Singapore
3. Check with Akshat why the website banner no longer on all the pages
4. Share plans to grow the conference beyond the main conferences
5. Call for Conference Sponsors

[thulieblack]

AsyncAPI Community Working Group Meeting Agenda:

1. Welcome and agenda alignment (3:00 PM - 3:05 PM) ➢ Facilitator: Thulie
   ➢ Welcome all team members to the meeting.
   ➢ Briefly share the agenda of the meeting.

---

2. AsyncAPI Conference 2025 (3:05 PM - 3:25 PM) ➢ Facilitator: Thulie
   ➢ Conference website updates and tasks
   ➢ Call for Speakers for Singapore
   ➢ Call for Conference Sponsors
   ➢ Check with Akshat why the website banner is no longer on all the pages
   ➢ Plans to grow the conference beyond the main conferences

---

3. AsyncAPI Website (3:25 PM - 3:40 PM) ➢ Facilitator: Akshat
   ➢ Doc maintainers for the AsyncAPI website
   ➢ Can there be a better way to maintain the docs for AsyncAPI (that are shown inside the website)? (Need opinions regarding centralizing the docs, from docs contributor's perspective)
   ➢ Website Redesign and the dark theme (how much do you think it's critical for the website)
   ➢ Discuss with Bami how localization inside the website can be effective in catching the audience.

---

4. Update from ED (3:40 PM - 3:55 PM) ➢ Facilitator: Lukasz
   ➢ New Governance Board chore: introduce governance board #1634
   ➢ 2025 Budget Budget 2025 #1681

---

5. Wrap-up, action items, and next steps (3:55 PM - 4:00 PM) ➢ Facilitator: Thulie
   ➢ AsyncAPI Bounty Q2 estimated to start March 2nd.
   ➢ Summarize key decisions and action items from the meeting.
   ➢ Confirm the date, time, and agenda for the next meeting.

[thulieblack]

Summary

--

AsyncAPI Conference Progress and Plans
Thulie led a meeting discussing the progress and future plans for the AsyncAPI Conference. She mentioned that the conference website is almost ready, with a pull request halfway done, and expected to be completed by the end of the week or early next week. Thulie also introduced Anushka and Olumide who will take over communication and design task,s respectively. The call for speakers for the Singapore conference is ongoing, with Lukasz and Mommy promoting it through emails and social media. Thulie also highlighted the need for financial sponsors to enhance the conference experience and encouraged everyone to share the information on social media.

Website Banner Visibility and Expansion
Thulie expressed concern about the visibility of the CFP banner on the website, which was only visible on the welcome page and not on other pages. Akshat agreed to look into the issue and hoped to resolve it within a few days. Thulie also proposed expanding the conference beyond the main ones, suggesting the inclusion of meetups as part of the conference. Akshat agreed with this idea, expressing a desire to see the conference expand to include India.

Bengaluru Conference and Meet-Up Planning
In the meeting, Thulie, Lukasz, and Akshat discussed the possibility of organizing a conference or meet-up in Bengaluru. They agreed that it would be easier to organize a meet-up and then expand it to a full conference. They also discussed the importance of marketing and promoting the event to the local tech community in Bengaluru. Akshat suggested reaching out to more people in Bangalore, including Ruchi, who had previously attended a conference. The team also acknowledged the need for a venue sponsor for the event.

Improving Meetup Structure and Sponsors
Thulie discussed the need to improve the structure of meetups and the process of organizing them under the conference working group. She proposed setting up a separate section on the conference website detailing the requirements for hosting a meetup, including a three-month advance notice and adherence to speaker guidelines. Thulie also mentioned plans to grow the conference beyond the main event. Bami clarified that the meetups would not be exclusive to student ambassadors, and all meetups would follow the same guidelines. Lukasz reported that at least one gold sponsor had been secured for the conference. Akshat, the core maintainer of the website, confirmed that Quetzalli would continue to contribute to the documentation, with Rohit also becoming a maintainer and Prince taking over the triager role.

Website Improvements and Localization
The team discusses several topics related to documentation and website improvements. Akshat proposes moving certain documentation parts to a separate repository, but Thulie emphasizes the importance of having preview deployments for reviewing changes. Lukasz suggests that previews can be technically enabled in other repos, though some setup is required. The group also considers implementing a dark theme for the website, with Thulie expressing support for this feature. Lastly, they discuss website localization, with Bami suggesting using Google Analytics to determine which non-English speaking countries access the site most frequently to prioritize language translations for an MVP.

Governance Model and Board Roles
Thulie and Akshat discussed the submission of an application, with Akshat expressing his tardiness. Thulie mentioned that the application had been submitted and that they could still make some additions before the deadline at 6 pm UTC. Lukasz then presented two topics for discussion. The first was about the suggestion to replace the current governance model with a board of people, to ensure the project's security and prevent a single person from having too much control. The second topic was about the roles and responsibilities of the Governance Board members, with Akshat expressing his concern about the time commitment required. Lukasz suggested that the duties could be split among the board members and that he would be available to help with the transition.

Budget Proposal and Bounty Programs
Lukasz discussed the budget proposal, which is still under discussion. He encouraged the community to review the proposal and raise any questions by Friday. He also mentioned a new bounty program starting on March 2nd. Thulie then took over, discussing the Asyncapi Q2 bounty program and the upcoming Governance Board. She also reminded the team about the GSOC application deadline and encouraged them to submit their proposals. Thulie ended the conversation by thanking everyone for their participation and encouraging them to reach out with any questions or concerns.

The next meeting #1713