Skip to content
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

Break out msgs into different package or repo #20

Closed
akashjinandra opened this issue Feb 9, 2024 · 3 comments
Closed

Break out msgs into different package or repo #20

akashjinandra opened this issue Feb 9, 2024 · 3 comments

Comments

@akashjinandra
Copy link

Hello, we are starting to work this repo and were wondering if it was possible for you guys to break out the message files into a different package and or repo, this seems to be the standard for most ros packages/repos. This allows us to different machines/workspaces be able to listen to the messages and not have to build the driver everywhere. Please see the examples here: https://github.com/ros-planning such as moveit_msgs, nav_msgs, etc. Please let me know what you think of this.

@tbohnma
Copy link
Collaborator

tbohnma commented Feb 27, 2024

Hello, thanks for your proposal. This seems to be a legit idea to re-organize our design.
We are currently close to our next release, but will consider you thoughts for the next version.

@akashjinandra
Copy link
Author

Hello, is there any more thought on doing this?

@tbohnma
Copy link
Collaborator

tbohnma commented Jan 23, 2025

Hello, we have changed the ROS driver according to your proposal and sent you the release candidate of the new ROS repo.
We will release the repo in Q1/2024.
I will close the ticket for now. Thanks for your thoughtful feedback!

@tbohnma tbohnma closed this as completed Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants