Added rosidl_rust repository

[esteve]

Reverts #1677

[ahcorde]

• Linux
• Linux-aarch64
• Linux-rhel
• Windows

[christophebedard]

@mjcarroll from my understanding (and based on my experience with ros2_tracing), if ros2-rust/rosidl_rust is getting added to ros2/ros2, and if it points to main instead of a specific commit or tag, then maintainers of ros2-rust/rosidl_rust should have/be given access to ci.ros2.org, correct? Because then any change getting merged into ros2-rust/rosidl_rust should be tested on ROS 2 CI.

[mjcarroll]

@mjcarroll from my understanding (and based on my experience with ros2_tracing), if ros2-rust/rosidl_rust is getting added to ros2/ros2, and if it points to main instead of a specific commit or tag, then maintainers of ros2-rust/rosidl_rust should have/be given access to ci.ros2.org, correct? Because then any change getting merged into ros2-rust/rosidl_rust should be tested on ROS 2 CI.

This matches my understanding. @esteve is this something that you would be okay with and interested in doing?

[esteve]

@christophebedard @mjcarroll sorry for the slow response, I've been mostly sick since last time. I already have access to ci.ros2.org, perhaps as having been a member of some team or something like that. In any case, yeah, I agree that it rosidl_generator_rs should be tested via the ROS 2 CI. We already have a CI setup in the ros2-rust org, but it tests only the ros2-rust-specific packages, and not as part of a larger ROS 2 system.

[christophebedard]

There are no new changes since ros2-rust/rosidl_rust#3 and CI looks good; I think this is ready.

[esteve]

@christophebedard @mjcarroll do you guys have any more feedback I should address? Once this is merged, I'd like to write a post on Discourse about it, so excited to be getting Rust into ROS!

[mjcarroll]

@esteve if you would like, when the kilted release post goes up tomorrow, maybe a good place to comment?