-
Notifications
You must be signed in to change notification settings - Fork 211
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 roadplan #59
Comments
I'm interested too. Anybody else willing to join in the effort? I have not ported any package to ros2 yet, but willing to take the plunge. |
@blablebli-robots @imstevenpmwyca hey guys, I just finished porting this to ROS2 and it tested it with TB3 simulation robot. Check it out https://github.com/robo-friends/m-explore-ros2 |
Hi @charlielito Will you integrate your work into this repo? Maybe in a ros2 branch, @hrnr? The Open Source philosophy behind ROS involves contributing to the author's repository so it doesn't seem like you're taking away their work and their legitimate authorship. Thanks for your effort, @charlielito |
For sure I am willing to make the contribution to this repo. The reason I created another one is because this repo seems to be dead since @hrnr doesn't even responded to this issue and the last commit is almost from 1 year ago. Also note that I am referring to this repository in the first line of the README of my ros2 port :) |
Hi @charlielito Yes, you are right. This repo shows little activity. We are planning to use this software in ROS2 this semester. If @hrnr doesn't reply in a couple of weeks, I find it reasonable to start using and contributing to your repo. Thanks again for your work |
Hi,
I wouldn't call this repository completely dead, I see the status as under
maintenance, with little active development under moment.
I'm happy to look at including ROS 2 version of nodes though. Clear benefit
here would be to share the actual algorithms here.
I'm also fine and happy if you keep it in a fork. Look at the license,
beyond what is written there I don't have any special rights or ownership.
No need to feel bad about forking unless you present it as your own work.
With that said it would be good to choose a different name if you'd publish
your forked package in the ROS repositories.
Cheers,
Jiri
|
Hi @hrnr Nice to see that this repo is alive 💪 Could you please create a Thanks to both |
Is there any intention of migrating this package to ROS2?
The text was updated successfully, but these errors were encountered: