Esteve Fernandez

@luca-della-vedova would it make sense to switch to https://nexte.st/ ? It'd mean depending on the `cargo-nextest` crate, but it provides output in the JUnit format, which colcon already has parsers...

> Not support doctests for which we would still need to fallback to normal cargo test (as documented https://github.com/nextest-rs/nextest/issues/16), which would bring us again to "how do we format the...

@ashquarky thanks for your interest in `ros2-rust`. Adding support for building Debian packages out of `ros2-rust` is not currently possible, we'd need at least these two before we can do...

@romainreignier we publish our generated documentation on https://docs.rs/rclrs/latest/rclrs/ and https://docs.rs/rosidl_runtime_rs/latest/rosidl_runtime_rs/, but it's true we should add a link to both, I'll do that later today.

> Why not advance the workflow to publish to https://docs.rs/? github pages would be an extra target to worry about. Because docs.rs only generates documentation for published crates, logging is...

> I think as long as the current documentation of rclrs does not contradict the current state of development, it should be ok. The current documentation on docs.rs matches the...

> If in doubt, you could also add a disclaimer there to point out that the current documentation on [docs.rs](https://docs.rs/) is out of date. It is not out of date,...

@avanmalleghem thanks for the PR, closing since we have a logging demo now. Thanks.

@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...

@Guelakais do you happen to have the `builtin_interfaces` repository in your workspace? If so, you'd need to remove it (or maybe even remove the entire workspace and start from scratch)....