Talk:Robot Operating System

Robotics Start‑class Low‑importance

	This article is within the scope of WikiProject Robotics, a collaborative effort to improve the coverage of Robotics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.RoboticsWikipedia:WikiProject RoboticsTemplate:WikiProject RoboticsRobotics
Start	This article has been rated as Start-class on Wikipedia's content assessment scale.
Low	This article has been rated as Low-importance on the project's importance scale.

Computing: Software Start‑class

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
Start	This article has been rated as Start-class on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by WikiProject Software.

Disambigulation

ROS also refers to ReactOS, according to ROSASM, ROSBE, etc. 68.185.166.207 (talk) 11:40, 30 May 2009 (UTC)[reply]

Not middleware!

Quote lede:

Robot Operating System (ROS) is robotics middleware (i.e. collection of software frameworks for robot software development).

This is not what middleware is! Middleware are systems for distributed objects, such as DCOM, CORBA and late time replacements. Robot Operating System contains middleware, fair enough, but it is an operating system level collection of libraries intended for robotics fast prototyping (as far as I can tell). There is a non-middleware core, a middleware set of libraries (according to the real definition), and some more. Rursus dixit. (^mbork³!) 10:13, 21 July 2018 (UTC)[reply]

Propose Restructuring

This article could use some work. Besides the introduction, which is pretty good, it's essentially just a timeline of development events, with a bit about ROS-Industrial. I'd like to propose restructuring as follows:

Introduction (edit, update, and expand)
History (narrative)
1. Version list
2. ROS2 (new)
3. ROS-Industrial (verify and update)
ROS Concepts and Construction (new)
Standard ROS Tools (new)
ROS Packages (expand)
1. Packages of note (new)
Robots Which Use ROS (expand)
See Also (expand)
Related Projects (expand)

Some of these sections, such as ROS Concepts and Construction and Standard ROS Tools would be entirely new, needing new references, mostly to the official ROS Tutorials. Thoughts? ApprehensiveAndroid (talk) 16:41, 11 April 2019 (UTC)[reply]