-
-
Notifications
You must be signed in to change notification settings - Fork 753
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
[📑 Docs]: Tutorial for using ROS2 with AsyncAPI #3054
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 @renzo-sie what's the update of this issue? |
Hi, @sambhavgupta0705, I was expecting a response that an branch would be open for me, where I can upload my code, and then set a pull request. Is this still the case? :) |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Hello, @renzo-sie , I would like to work on this issue could you please assign it to me |
Hi @harshita9104 , thanks for your support offering! I was hoping to resolve first this issue (asyncapi/bindings#254 (comment) ) before moving on with this issue. Thanks again! :D |
What Dev Docs changes are you proposing?
I will show provide examples how to use ROS2 with AsyncAPI. This will also show how to use ROS2 bindings: asyncapi/bindings#254 (comment)
Code of Conduct
The text was updated successfully, but these errors were encountered: