Outreach with the Rust Community

[ruffsl]

It'd be nice to get some more feedback on the design/implementation of rclrs from the larger Rust community, e.g. are there better approaches to wrapping the rcl c library, code generation, testing practices, API pattern that ROS users could benefit from. Additionally, many Rust users may appreciate what the rest of the ROS2 ecosystem has to offer in terms of robotic software development, growing the number of users and subsequent contributions.

[esteve]

@roboticswithjulia thanks for all interest in the project. However, nobody who's involved in the development of the project has given a talk yet because we know that it's still unstable and that would mislead users, making them feel frustrated when trying ros2-rust for their applications when things don't work as they expect.

It's important to manage their expectations regarding the project, I'm sorry to say it, but I watched your talk and some of the answers you gave during the Q&A were unfortunately not reflecting the reality of the project or just incorrect, and I hope it's not the case, but it might have misled users as to what to expect from ros2-rust. Right now we're being very careful when we discuss ros2-rust because it's still not stable and as it usually happens, the first impression is the one that matters the most.

In any case, I really appreciate your enthusiasm and I'm looking forward to seeing your first contribution soon! 🙂

This ticket is quite old (~6 years), we already have a design that we're following. I'll probably close this ticket sometime soon.

[roboticswithjulia]

I truly understand your concern about managing expectations for the ros2-rust project. You're absolutely right that presenting unstable projects can lead to user frustration when things don't work as expected. I apologize if my talk and Q&A session contained information that didn't accurately reflect the project's current state. I would greatly appreciate your feedback about which specific points were misleading or incorrect in my presentation. This would be invaluable for my own learning and to ensure I don't spread misinformation in the future. Rest assured, this will be the last time I speak publicly about the project. While I had hoped that discussing it might generate useful feedback before completion, I completely respect your position as one of the creators. You naturally have a much deeper understanding of the project's status, design direction, and development roadmap. Thank you for your kind words about my enthusiasm for the project. I'm looking forward to contributing in more constructive ways going forward.