-
-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ROS2 bindings #254
Comments
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. |
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 |
@renzo-sie hey, sorry for the delay. Can you provide some example AsyncAPI document with these new binding included, with comments what these binding properties are for, so it is easier to understand what you need. It will also clear out where these bindings be located, in what AsyncAPI objects, like channel or others. Are you aware that in case of bindings, it is not enough to contribute binding, you also have to become a maintainer of it? |
Hi @derberg , thanks for the response! You can set @gramss (https://github.com/gramss) as the main mantainer for this binding, and me as the second contact. Would be nice to show this binding in the next ROS event in germany next week :) (https://roscon2024.de/) |
Hi @derberg, Here is the new version of the ROS 2 bindings: Did you had a chance to review the document ? :) |
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:
🚧 Breaking changes
No
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: