AsyncAPI Community Working Group Meeting, 15:00 UTC Tuesday February 25th 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.

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:20 PM) ➢ Facilitator: Olumide
   ➢ Singapore speakers will be announced soon
   ➢ We have some conference tasks that need contribution
   ➢ Call for Conference Sponsors
   ➢ Conference Coordinators to start collaborating with marketing and designers to start preparing materials for Munich and Lagos

---

3. AsyncAPI Community (3:20 PM - 3:55 PM) ➢ Facilitator: Thulie
   ➢ Remove the #general channel -- Lukasz
   ➢ Alignment with maintainers and mentors on why we should prioritize Maintainership!
   ➢ Have an educational call with Mentors before any program starts as a requirement
   ➢ We're growing, and it's time to reevaluate how we do mentoring programs and mentee application criteria. For instance, to apply to a program, you must have made proper contributions for 3 months to the project. (Take Inspiration from the Bounty Program).
   ➢ An Advisory Board to review and select projects and maybe proposals, too?
   ➢ Creation of new documentation for mentors and mentees
   ➢ Update requirements to become a Maintainer?
   ➢ Automate Eve/Chan to respond to messages such as --, "Assigne me this issue/ Can I work on this issue."

---

4. Wrap-up, action items, and next steps (3:55 PM - 4:00 PM) ➢ Facilitator: Thulie
   ➢ Budget Voting Budget 2025 #1681 and AsyncAPI Bounty Q2 issue submission fromMarch 3 - 31.
   ➢ Summarize key decisions and action items from the meeting.
   ➢ Next meeting on March 11 at 3 PM UTC, start to share your agenda items.

Notes

Add notes here after the meeting.

[thulieblack]

@AceTheCreator @derberg @aeworxet @akshatnema @iambami @SaxenaAnushka102 @Oloso-surur

Please add your agenda items before Friday thanks 😀

[derberg]

item: should we remove #general channel 😅

[thulieblack]

I have some items from the community side:

• Automate the bot to respond to messages such as --, "Assigne me this issue/ Can I work on this issue."
• Align and educate maintainers and mentors on why we should prioritize Maintainership!
• Reevaluate and change how we do mentoring programs and mentee application criteria. For instance, to apply to a program, you must have made proper contributions for 3 months to the project. (Take Inspiration from the Bounty Program).
• Have proper documentation for both Mentors and Mentees
• Have an Advisory Board to review project ideas and maybe proposals?
• Change requirements of new maintainers?

[Oloso-surur]

AsyncAPI Conference 2025 (3:05 PM - 3:15 PM) ➢ Facilitator: [ Olumide]

➢ CfP for Singapore closing on Sunday - 30th of February, 2025 and speaker announcement t be made the following week.

Link: https://buff.ly/4htStVo

➢ Conference tasks that needs contribution

Link: AsyncAPI Conference (view)

➢ CfP planning and preparation or Munich and Lagos conferences and the design needed

➢ Prospectus for sponsors to be shared with the community.

Link:
https://conference.asyncapi.com

[TRohit20]

Given the influx of interest in participation for our mentorship programs have consistently gone up over the last 3 years, I was thinking if we should add to our criteria of selection, a certain brief period of contribution prior to the program selection period.

How to measure?

• not by the number of PRs opened, but the quality of communication pre & on-going PR.
• Often our PRs take lot of iterations, so communication, patience take precedence along with technicals
  This is a great indicator of 2 things:

1. If the person can persist and carry out the commitment to fruition over time along with learnings :)
2. Someone who contributes so regularly at that point is more likely to stick around post the program too and help out or contribute in some sense or another in their own limited capacity as a lot of us already do.

• This also directly pairs in with maintainership allowing us to identify peers and help them grow in the same direction.

[aeworxet]

Request to @asyncapi/tsc_members to complete the voting for the Budget 2025 at #1681.

[thulieblack]

@TRohit20, your suggestions are in line with what I have, so I'll consolidate them into one with the community items

[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:20 PM) ➢ Facilitator: Olumide
   ➢ Singapore speakers will be announced soon
   ➢ We have some conference tasks that need contribution
   ➢ Call for Conference Sponsors
   ➢ Conference Coordinators to start collaborating with marketing and designers to start preparing materials for Munich and Lagos

---

3. AsyncAPI Community (3:20 PM - 3:55 PM) ➢ Facilitator: Thulie
   ➢ Remove the #general channel -- Lukasz
   ➢ Alignment with maintainers and mentors on why we should prioritize Maintainership!
   ➢ Have an educational call with Mentors before any program starts as a requirement
   ➢ We're growing, and it's time to reevaluate how we do mentoring programs and mentee application criteria. For instance, to apply to a program, you must have made proper contributions for last 3 months to the project. (Take Inspiration from the Bounty Program).
   ➢ An Advisory Board to review and select projects and maybe proposals, too?
   ➢ Creation of new documentation for mentors and mentees
   ➢ Update requirements to become a Maintainer?
   ➢ Automate Eve/Chan to respond to messages such as --, "Assigne me this issue/ Can I work on this issue."

---

4. Wrap-up, action items, and next steps (3:55 PM - 4:00 PM) ➢ Facilitator: Thulie
   ➢ Budget Voting Budget 2025 #1681 and AsyncAPI Bounty Q2 issue submission from March 3 - 16.
   ➢ Summarize key decisions and action items from the meeting.
   ➢ Next meeting on March 11 at 3 PM UTC, start to share your agenda items.

[Shurtu-gal]

item: should we remove #general channel 😅

Reason being?

[thulieblack]

Join the meeting 👌🏿

…

On Fri, 21 Feb 2025, 13:43 Ashish Padhy, ***@***.***> wrote: item: should we remove #general channel 😅 Reason being? — Reply to this email directly, view it on GitHub <#1713 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP6QMET3TGIIONIAXBNARFT2Q4GP5AVCNFSM6AAAAABW5N4UQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZUGMZTGMBVG4> . You are receiving this because you commented.Message ID: ***@***.***> [image: Shurtu-gal]*Shurtu-gal* left a comment (asyncapi/community#1713) <#1713 (comment)> item: should we remove #general channel 😅 Reason being? — Reply to this email directly, view it on GitHub <#1713 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP6QMET3TGIIONIAXBNARFT2Q4GP5AVCNFSM6AAAAABW5N4UQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZUGMZTGMBVG4> . You are receiving this because you commented.Message ID: ***@***.***>

[derberg]

Reason being?

it's flooded with messages from GSoC, basically spammed - and looks like AsyncAPI is an organization that's purpose is just to do mentorship. IMHO "general" makes people lazy. No "general", then people need to think and search for the right channel to interact. No "general" then people first would land in "introduction" channel

[fmvilas]

What about limiting who can publish there to Thulie, Lukasz and, in the future, the Governance Board?

[derberg]

one of the options - but most important, since we have now #announcements, is #general really needed as it is - maybe it should be renamed to announcements (as largest channel)