AsyncAPI Spec Triage , 14:00 UTC Wednesday November 19th 2025

[asyncapi-bot]

Meeting Info	Details
Purpose	First meeting to kick of more regular work on spec issues triage and regular work to resurrect regular releases.
Time	14: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

Don't wait for the meeting to discuss topics that already have issues. Feel free to comment on them earlier.

1. Q&A
2. Place for your topic
3. Q&A

Notes

Add notes here after the meeting.

[derberg]

Recording: https://www.youtube.com/watch?v=G2JTsDe0h-g

• Spec triage board: Spec Triage (view)
  All code owners are invited. I suggest that we pull in the TODO issues we want to discuss before the next meeting, so all of us can see them and, if possible, familiarize ourselves with them before the meeting.

• feat: add ROS 2 bindings to the official specification spec#1109 is a good January release candidate. Siemens work TODO below and more details in the recording:

  • Look again at the binding name and share a more detailed clarification of why ROS2 is the best name.
  • Update PRs in the bindings and spec JSON Schema repositories with changes in CODEOWNERS.

• We did a quick, easy review of docs: clarify that applications may also expose the protocol spec#1128 and, after gathering 3 approvals, merged it to master.

• Folks, please have a closer look at feat: Add AND logic support for multiple security schemes (#1129) spec#1135 before the next meeting. Drop comments, ask questions. Some aspects of this PR were already discussed during the meeting, so follow up with the recording.

• TODOs:

  • @derberg: Ping Siemens
  • @derberg: Check with @fmvilas if he is still interested in doing release coordination for January
  • @derberg: Schedule the next meeting next month
  • @char0n: Create an issue about broken Markdown ToC anchors

[gramss]

@derberg saw the notes. @amparo-siemens let's sync about this next week.