Call for Volunteers - ROS Node Configuration #3636
Replies: 3 comments 4 replies
-
Here are some updated instructions from Kasper, wonderful to see people are starting to fill in the spreadsheet and take on some nodes. Anyone modifying nodes also please feel free to join an OADKit WG call and say hello. Your contributions are highly appreciated. |
Beta Was this translation helpful? Give feedback.
-
I have a thought with regard to the package building. Let's take the node I think it has something to do with the
Maybe it would be a good idea to write this into the guideline since some nodes only achieve the launch dir sharing but not the config dir. |
Beta Was this translation helpful? Give feedback.
-
@BonoloAWF @xmfcx : Kindly provide access to push code to main branch below ids |
Beta Was this translation helpful? Give feedback.
-
Background
In the Open AD Kit WG, we recently came to consensus on the structure of how ROS nodes should be configured. We're now asking for volunteers to help us implement and upstream these changes!
The 4th phase is the last phase in a DevOps Dojo, which focuses on integration of the new solution. See autowarefoundation/autoware.universe#2652 for more details.
Instructions
You help by choosing a ROS node in the Universe/Core repo and make changes according to the new coding guidelines. Once the ROS node(s) have been allocated to you, you can start making changes and follow the normal procedure of upstreaming code.
See DevOps Dojo: ROS Node Configuration - Step by Step Instructions for detailed instructions.
Necessary skills:
If you don't have these skills, don't worry! An important part of the DevOps Dojo work is continuous learning, we're here to assist you!
Contact
If you want to participate, need access, have questions, etc, please reach out to:
We appreciate your interest and participation!
Beta Was this translation helpful? Give feedback.
All reactions