With the increasing addition of remote engineering resources thanks to the efforts of the TSC, there must be some kind of instantaneous chat going on. @wjwwood mentioned an Open Robotics slack; having an internal slack is not something I'm going to argue against because I agree it is needed. As everyone seems to agree, what is lacking is the equivalent for the whole community that is *actually used*. I gave up trying to maintain my connection to #ROS because was 95% no activity, 4% someone making a random statement along the lines of "Hi there! I'm learning ROS! Yay", and the remaining 1% was interesting discussion. This not-being-used thing is a problem. As @kyrofa said, having to hold your design discussions in a public channel that supports rapid, lightweight response is better all around.
What technical solution to use for instantaneous chat is another thread now, but I am all in favour of trying to transform things a bit in this way.
Plus my collection of Slacks is not nearly big enough yet.
---
[Visit Topic](
https://discourse.ros.org/t/design-process-of-ros-2/7782/10) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)