G.A. vd. Hoorn

> There has been discussion on if we should have organization level issue templates instead of each repository. https://github.com/ros2/.github/issues/2?

> @MiguelCompany i am okay with backport for jazzy, lets hear from other opinion. If this hasn't yet been backported, I would really appreciate a backport to Jazzy.

It's ROS 1, AFAIK, but @rhaschke's team/colleagues have been working on: [ubi-agni/mujoco_ros_pkgs](https://github.com/ubi-agni/mujoco_ros_pkgs).

Hi, thanks for the PR, really appreciated. I'm going to need a little more time before I can review it. Just thought I'd let you know.

> We could also disclose an algorithm to perform the check, but it would not fit very well into how path planners work... MoveIt does (did?) have support for custom...

Nice work. A high-level comment and a question: - would there be a way to implement this without adding more `static` variables? Some of the added functions don't take any...

It would not be much work bumping `rmw_microxrcedds` to include the fix and use it as part of `libmicroros`. We could also wait for a release upstream and then bump...

I believe this was addressed and is no longer an issue starting with release `0.2.1`. @jimmy-mcelwain: if you agree, could you close this?

> It just notifies the user that an RCL(C) API error occurred and gives the integer value of the rcl_ret_t value associated with that error that the user has to...

> Also, while I agree that the previous approach with the "shadow codes" would require maintenance in case there are changes to types.h in the future, won't we need to...