The Robot Operating System: Package reuse and community dynamics
Author
dc.contributor.author
Estefo, Pablo
Author
dc.contributor.author
Simmonds, Jocelyn
Author
dc.contributor.author
Robbes, Romain
Author
dc.contributor.author
Fabry, Johan K.
Admission date
dc.date.accessioned
2019-10-15T12:25:24Z
Available date
dc.date.available
2019-10-15T12:25:24Z
Publication date
dc.date.issued
2019
Cita de ítem
dc.identifier.citation
Journal of Systems and Software, Volumen 151,
Identifier
dc.identifier.issn
01641212
Identifier
dc.identifier.other
10.1016/j.jss.2019.02.024
Identifier
dc.identifier.uri
https://repositorio.uchile.cl/handle/2250/171676
Abstract
dc.description.abstract
ROS, the Robot Operating System, offers a core set of software for operating robots that can be extended by creating or using existing packages, making it possible to write robotic software that can be reused on different hardware platforms. With thousands of packages available per stable distribution, encapsulating algorithms, sensor drivers, etc., it is the de facto middleware for robotics. Like any software ecosystem, ROS must evolve in order to keep meeting the requirements of its users. In practice, packages may end up being abandoned between releases: no one may be available to update a package, or newer packages offer similar functionality. As such, we wanted to identify and understand the evolution challenges faced by the ROS ecosystem. In this article, we report our findings after interviewing 19 ROS developers in depth, followed by a focus group (4 participants) and an online survey of 119 ROS community members. We specifically focused on the issues surro