ROS2 bindings

[renzo-sie]

Why do we need this improvement?

We need this improvement to seamlessly integrate ROS2, a widely-used framework in robotics, with AsyncAPI. This integration will enhance the capabilities of ROS2 by providing a standardized way to document and communicate its event-driven architecture. By including ROS2 bindings, we can ensure that ROS2 developers can leverage AsyncAPI's benefits for better interoperability, documentation, and tooling.

How will this change help?

This change will help by providing a standardized approach to describing ROS2 communication interfaces, enabling better tooling support, improved collaboration, and more efficient development processes. It will facilitate the generation of documentation, code, and other artifacts, thus reducing the manual effort required and minimizing the risk of errors.

Screenshots

No response

How could it be implemented/designed?

We will implement the ROS2 bindings similarly to other existing bindings in AsyncAPI. This involves:

• Defining the ROS2-specific protocol and message type bindings.
• Creating documentation and examples to guide users in applying these bindings.

🚧 Breaking changes

No

👀 Have you checked for similar open issues?

• I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue?

Yes I am willing to submit a PR!

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[renzo-sie]

Hi, is there any news on this issue? :) If I understand correctly, I still need to wait for a branch to be created to submit my code