[ros-users] [Discourse.ros.org] [Next Generation ROS] Design process of ROS 2

Matt Hansen via Discourse.ros.org ros.discourse at gmail.com
Thu Feb 14 17:18:28 UTC 2019

I'm not sure I agree that adding slack or IRC is going to resolve this any better than Github and Discourse has. I think its just going to add more confusion, not less, IMO. I already get 10-30 github notifications, dozens of emails, and 5-10 Discourse notifications each day. Adding IRC/Slack will only make things less focused, not more. I think something more like the model that Google Cartographer is using for their [Open House](https://github.com/googlecartographer/cartographer#open-house) is a better way to discuss the key design issues in real-time. 

I would also like to add that I do understand the iterative approach, but without knowing what the long-term design goal is, often the first iteration becomes the only implementation (as noted above by @gbiggs). At least if the goal is stated clearly in a design document (or an Epic as he suggested), then it can be made clear that there will be changes upcoming to reach that final design. I don't think we have that clarity right now. It might be clear to the implementers that it was only meant to be a first implementation, not the final one, but to the community, it's not clear. See the thread on [Actions](https://github.com/ros2/ros2/issues/583) that was mentioned above for a good example of this.

[Visit Topic](https://discourse.ros.org/t/design-process-of-ros-2/7782/12) or reply to this email to respond.

More information about the ros-users mailing list