dc.creatorEstefo, Pablo
dc.creatorSimmonds, Jocelyn
dc.creatorRobbes, Romain
dc.creatorFabry, Johan K.
dc.date.accessioned2019-10-15T12:25:24Z
dc.date.available2019-10-15T12:25:24Z
dc.date.created2019-10-15T12:25:24Z
dc.date.issued2019
dc.identifierJournal of Systems and Software, Volumen 151,
dc.identifier01641212
dc.identifier10.1016/j.jss.2019.02.024
dc.identifierhttps://repositorio.uchile.cl/handle/2250/171676
dc.description.abstractROS, 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
dc.languageen
dc.publisherElsevier Inc.
dc.rightshttp://creativecommons.org/licenses/by-nc-nd/3.0/cl/
dc.rightsAttribution-NonCommercial-NoDerivs 3.0 Chile
dc.sourceJournal of Systems and Software
dc.subjectPackage management
dc.subjectRobot Operating System
dc.subjectSoftware ecosystems
dc.titleThe Robot Operating System: Package reuse and community dynamics
dc.typeArtículo de revista


Este ítem pertenece a la siguiente institución