# Rust working group meeting 2021/10/13

**URL:** <https://discourse.openrobotics.org/t/rust-working-group-meeting-2021-10-13/22674>\
**Category:** ROS General\
**Tags:** wg-rust\
**Created:** [October 13, 2021, 9:55am UTC](https://discourse.openrobotics.org/t/rust-working-group-meeting-2021-10-13/22674 "2021-10-13T09:55:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![esteve](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/esteve/32/12_2.png) [@esteve](https://discourse.openrobotics.org/u/esteve)\
**Post date:** [October 13, 2021, 9:55am UTC](https://discourse.openrobotics.org/t/rust-working-group-meeting-2021-10-13/22674/1 "2021-10-13T09:55:56Z")

</div>

Reminder that the Rust working group meeting will take place today 2021-10-13T14:00:00Z

> **[Meet](https://meet.google.com/unsupported?meetingCode=kco-rxud-idn&ref=https:%2F%2Fmeet.google.com%2Fkco-rxud-idn?authuser%3D0%26hs%3D122)**
>
> Real-time meetings by Google. Using your browser, share your video, desktop, and presentations with teammates and customers.

---

<div class="post-metadata">

**Author:** ![esteve](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/esteve/32/12_2.png) [@esteve](https://discourse.openrobotics.org/u/esteve)\
**Post date:** [October 13, 2021, 3:21pm UTC](https://discourse.openrobotics.org/t/rust-working-group-meeting-2021-10-13/22674/2 "2021-10-13T15:21:34Z")

</div>

A summary for those who couldn’t attend:

- ros2\_rust will drop its message generation pipeline in favor of r2r’s
- r2r will test the colcon-cargo integration
- ros2\_rust and r2r will combine efforts by first working on a core API that will resemble ROS2’s more, and r2r will build its API on top of that. The goal of this is so that ROS2 developers can start developing programs in Rust with a familiar API, whereas more experienced Rust developers can use a more idiomatic API to access ROS2
- the core API of ros2\_rust will aim to be no\_std so that it can target embedded platforms

@jhdcs anything I forgot?

---

<div class="post-metadata">

**Author:** ![jhdcs](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/jhdcs/32/8074_2.png) [@jhdcs](https://discourse.openrobotics.org/u/jhdcs)\
**Post date:** [October 13, 2021, 3:53pm UTC](https://discourse.openrobotics.org/t/rust-working-group-meeting-2021-10-13/22674/3 "2021-10-13T15:53:28Z")

</div>

No, that sounds about right! Only question I have is, do we create a new project for the new `ros2_rust_core?` Or make it a crate within the existing `ros2_rust`?

No matter what, I think we should create a bunch of issues that maps out how we’re going to create the core.

---

<div class="post-metadata">

**Author:** ![esteve](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/esteve/32/12_2.png) [@esteve](https://discourse.openrobotics.org/u/esteve)\
**Post date:** [October 14, 2021, 2:47pm UTC](https://discourse.openrobotics.org/t/rust-working-group-meeting-2021-10-13/22674/4 "2021-10-14T14:47:51Z")

</div>

I think `ros2_rust` is fine, since the current API is more or less what the core crate will look like and upon which `r2r` will eventually be built. We can start a separate branch that will be merged onto the current main branch of `ros2_rust`

---

<div class="post-metadata">

**Author:** ![jhdcs](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/jhdcs/32/8074_2.png) [@jhdcs](https://discourse.openrobotics.org/u/jhdcs)\
**Post date:** [October 14, 2021, 3:06pm UTC](https://discourse.openrobotics.org/t/rust-working-group-meeting-2021-10-13/22674/5 "2021-10-14T15:06:59Z")

</div>

Ok. I’ve been working on a crate within `ros2_rust` called `rclrs_core` that’s basically attempting to replicate `rclrs` within `no_std`. Let me set up a PR for the error stuff I’ve been working on…