Tomoya Fujita

> it really is necessary because of some devices only supporting middleware 1 and the other only middleware 2, and yet they have to be combined into a single system....

> We are essentially taking current bugs (inter-service operability between CycloneDDS and our other RMWs), and upgrading them to policy. ah, that is true, there is already issue and discussion...

> we are the only ones who do it without requiring support for yet another bad specification (RPC over DDS). When all the pros and cons are considered of the...

IMO, I believe this is gonna be good for ROS local community, I will second this approach. > Unless a very small subset of the documentation is translated (e.g., installation...

IMO, I would like to keep `examples` and `demos` as simple as possible to `how to call or demonstrate ROS 2 APIs or Features`, not so much related to how...

i would like to revise https://github.com/weaveworks/weave/issues/3960#issuecomment-1396556847, anyone working to address this issue to support multi-arch image?

okay this is duplicate with https://github.com/weaveworks/weave/issues/3974

work around is to use this one instead, https://github.com/weaveworks/weave/releases/download/v2.8.1/weave-daemonset-k8s-1.11.yaml

@benthie thanks for creating issue. we have the same problem with https://github.com/ros2/ros2/commit/1f5bd8ed43beea199dabe48bc8023af3aba9806c `rolling`. i think this is not expected behavior as designed.

@moooeeeep thanks for creating issue. > I recently was in the situation, that two nodes were publishing on the same topic (classroom environment with several turtlebots, two of which with...