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

Port to ROS2 #62

Open
2 tasks
130s opened this issue Sep 30, 2018 · 5 comments
Open
2 tasks

Port to ROS2 #62

130s opened this issue Sep 30, 2018 · 5 comments

Comments

@130s
Copy link
Member

130s commented Sep 30, 2018

Suggested at https://discourse.ros.org/t/ros2-perception-porting-status/6231

  • List up things to do to enable ROS2.
  • Implement them.

(As a maintainer though, I don't foresee I can dedicated any time on this any time soon while I'm happy to help reviewing contribution and making a necessary releases.)

@machinekoder
Copy link

@130s What's the requirements to become a maintainer? I've already ported it to noetic, can't be too hard to port it to ROS2 as well, since this would only involve changes in the node sources.

@130s
Copy link
Member Author

130s commented Nov 12, 2020

Thanks for the offer to be a maintainer!

  • I'd add you to an admin group ar_track_alvar but I can't seem to add you. @wjwwood Would you mind adding @machinekoder to the group? I've seen his great contribution in the OSS community.
  • @machinekoder Please add you in the package.xml as a maintainer. You can remove myself as I have no bandwidth unfortunately to continue.

@wjwwood
Copy link
Member

wjwwood commented Nov 12, 2020

I sent the invite.

@AndrewJSchoen
Copy link

I might be interested in testing this, if/when things are at that point.

@niiquaye
Copy link

niiquaye commented Jun 4, 2021

Is there any updates on this by any chance? Is it recommended we stick to using ros1 and this package or in my case a ros 1 bridge to ros2 to use this package?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants