asyncapi
recurring spec meeting
@dalelane @char0n @fmvilas @GreenRover
Hey folks, how about we start doing a monthly triage meeting to start working on the spec on a regular basis? One hour, once a month, to triage issues and push for new releases.
We could start in November - I can be the organizer to make sure it takes place, gets recorded, and stuff like that. Like doing a chair job.
We could push for https://github.com/asyncapi/spec/pull/1109 release in next window - January 2026
love the enthusiasm!
@fmvilas @char0n @dalelane @GreenRover
please select when we can do this meeting: https://whenavailable.com/invite/VbPXJe49EF90gtkfuBKI
waiting for answers until Nov 12, 2025
info for others, I ask only specific folks for RSVP as they are co-maintainers of the spec and are the most important audience for the meeting. Of course meeting will be public and anyone can join.
From voting, it looks like 2 dates are good for all. I chose Wednesday as I hate Mondays 😄
Meeting scheduled: https://github.com/asyncapi/community/issues/2141. All calendar links + Zoom and others are there.
@dalelane @fmvilas @char0n @GreenRover
The meeting took place 💪🏼 Notes and action items: https://github.com/asyncapi/community/issues/2141#issuecomment-3553310410
I'll keep this issue open if you do not mind, for coordination of setting up next meeting and also to show other community members we do these public meetings.
Time for another and last meeting this year.
Please select best time: https://whenavailable.com/invite/RchTFE6ohEhC3vxQj5JD (pool opened till Tuesday)
@dalelane @fmvilas @char0n @GreenRover
pending action items from last meeting @fmvilas confirm if you are still interested in doing release coordination for January @char0n: Create an issue about broken Markdown ToC anchors
for now agenda:
- please look at https://github.com/asyncapi/spec/pull/1135
- ROS2: @gramss and @amparo-siemens I see you addressed topic of
CODEOWNERSbutLook again at the binding name and share a more detailed clarification of why ROS2 is the best name.is missing as far as I can tell
Regarding ros vs ros2
ROS2 is in its 10th release already. Kilted (starting with A).
Also 99% of all official cli tools for ROS2 are using the ros2 identifier. Official naming would best case be ROS 2.
Some design patterns with ROS 1 would break in our binding. With the 2, it is solid clear that we are focusing on the API / design pattern breaking newer version of ROS.
Hope this clearifies this. :)
@gramss - Thanks for the clarification, that makes sense. (To be clear, this wasn't really about ROS 1, more about understanding whether calling it "ros2" was sufficiently "future-proof" in case a ROS 3 was likely to be imminent. The fact that you say ROS2 is in it's 10th release certainly addresses that!)
Time for another and last meeting this year.
...
for now agenda:
...
Would love to discuss https://github.com/asyncapi/spec/issues/1143 if we have time
Based on https://whenavailable.com/invite/RchTFE6ohEhC3vxQj5JD next triage meeting setup for next Thursday: https://github.com/asyncapi/community/issues/2187
cc @dalelane @fmvilas @char0n @GreenRover
of course if someone has some proposal that you want to push, discuss, feel free to join, although best if you suggest the topic earlier.
pending action items from last meeting
- @fmvilas confirm if you are still interested in doing release coordination for January
- @char0n: Create an issue about broken Markdown ToC anchors
issues to look at before the meeting:
- https://github.com/asyncapi/spec/pull/1135
- https://github.com/asyncapi/spec/issues/1143
Hi all,
- added research notes to https://github.com/asyncapi/spec/issues/1129 from which the https://github.com/asyncapi/spec/pull/1135 was produced
- added approval for https://github.com/asyncapi/spec/pull/1109 with an attached comment
- made myself familiar with https://github.com/asyncapi/spec/issues/1143
- created issue around navigation in https://github.com/asyncapi/spec/issues/1144