[Announcement] rplidar_ros2_driver: A Modern C++ (C++17) Driver with Lifecycle Support

Liking a post does not mean that you officially endorse the post or that you agree with every possible extracted snippet. Sometimes I like things to just to acknowledge that I’ve seen them. I also liked the original post. I think an improved, modern, RPLidar package is a good thing. I also think it is totally healthy and productive to acknowledge when things appear to be AI generated.


About the OpenRobotics’ LLM views, They are discouraging a lot of users with this attitude. (I followed it since it was a real Foundation, I started with ROS 1 Indigo). But this is something else. Can you you tell us where the official guidelines discourage users from writing custom ROS packages (not the contributions to the official repos) using LLMs, and sharing them with the community?

We do not discourage LLM generated posts. We do ask that LLM content be clearly marked as such.


If there were no people like Steve Macenski (which approved multiple PRs of mine, God bless the neighborhood navigator), what would be the current state of the ROS? I opened a PR to the teleop_tools, tried to talk with the maintainers about sending another PR with a fix I am using locally, not using LLMs, but still, I did not hear a ping for almost a year.

A one-line-change PR of mine, to ROS 1, was merged after 1+ years, long after I switched to ROS 2.

None of those PRs were written using LLMs.

You cannot see me crying in this forum because of silent PRs, I understand that the maintainers could be busy.

None of those Github orgs are managed by the OSRA. ROS is a huge project maintained by volunteers, there are lot of places where we need more volunteer support. My advice is, as always, if you want your PR reviewed promptly, help out the maintainer by reviewing another pull request.


If I write “ROS2” instead of “ROS 2”, I can be judged by the Open Robotics nonprofit corporation, but not when bullying new users in the community?

Encouraging people to use the official ROS brand guidelines is not “judging”. They were designed to help communicate that ROS 2 is a version of ROS not a new thing. And planning that out and sticking to it through the transition is going to make our life easier going forward.

I wouldn’t characterize @peci1 comments as bullying. Pointing out that the project appears to be generated by an LLM provides additional useful context to potential users. The responses and clarifications have been helpful to understand more about the announced software.

3 Likes