Chris Lalancette

Just as an FYI, I went in here and cleaned up the tutorials in question pretty heavily. In particular, I made sure that the C++ and Python versions were as...

> This relates to [ros2/design#314](https://github.com/ros2/design/issues/314); Yes, I'd very much like to get a better idea of the bigger picture via that issue before we add more configuration options.

> Can you help me understand what you mean by the bigger picture here so we can help move this forward? This missing feature has greatly reduced the usability of...

> Where should this documentation live? Is that something that should be done here in this repo or should it be somewhere else? Well, in my mind there are 2...

> To make sure I understand you clearly, the things that have to happen before we can even consider moving towards functional parity with ros1 logging configuration are these: >...

I've retargeted this to the `rolling` branch, and I've also changed the if structure so that it throws an exception when you pass a pattern that isn't supported. I *think*...

> I jumped to the [Building ROS 2 on Windows](http://docs.ros.org/en/galactic/Installation/Windows-Development-Setup.html) instructions, and noticed that there were a few prerequisites under [Additional prerequisites](http://docs.ros.org/en/galactic/Installation/Windows-Development-Setup.html#additional-prerequisites) that are **not** listed on the [Installing ROS...

This actually does already exist, it maybe just isn't well documented. If you call: ``` node.get_logger().info('my log', throttle_duration_sec=1) ``` Then it will only log once per second, regardless of how...

This was actually solved via https://github.com/ros2/ros2_documentation/pull/3025 , so closing this out.

> The **Efficient Intra Process Communication** guide seems heavily outdated, it mentions that unique_ptr is the only way to achieve zero-copy intra process comms, but there's been major improvements and...