Adolfo,
Thanks for your interest. I think you are correct that we could only hope to certify every couple of actual ROS revisions. Our customers would probably be
willing to give up the latest and greatest functionality for certification.
Shaun Edwards
Senior Research Engineer
Manufacturing System Department
http://rosindustrial.swri.org/
Southwest Research Institute
210-522-3277
From: ros-users-bounces@code.ros.org [mailto:ros-users-bounces@code.ros.org]
On Behalf Of Adolfo Rodríguez Tsouroukdissian
Sent: Friday, April 13, 2012 12:13 PM
To: User discussions
Subject: Re: [ros-users] Enterprise Version of ROS
On Thu, Apr 12, 2012 at 5:07 AM, Edwards, Shaun M. <sedwards@swri.org> wrote:
All,
We have been using ROS for some time now. Projects that originally started as research are now maturing to the point where they need to be deployed. As we have started moving
ROS from research applications to real world applications it is becoming very clear that stability, safety, and reliability are of chief concerns to our customers. For early adopters, we can alleviate these issues by standing behind the software as a whole,
including ROS. After all, sometimes it is easier to support an open software solution than it is a closed solution, since not all closed source software vendors live up to our customers expectations.
I would like to gauge community interest in creating a group whose purpose is to test, review, and certify robust, stable, and safe Enterprise versions of ROS. This may be a group
of volunteers, but I fully expect that such a group would need significant funding, hopefully by commercial and other large users. It is also possible that a company could be create for or step into this role, much like RedHat.
Is anybody open to this idea? Is this a good idea? Has anybody else seen/expressed this need? Is ROS at the point where this makes sense? What do you think?
We at PAL Robotics would be open to the idea, yes. Probably the first step would be to start discussing what are the expectations of the interested parties, and determine the scope of "test, review, and certify robust, stable, and safe", as well as a sensible
timeline to start making incremental progress. I personally have never participated in the certification of HW/SW, but I have co-workers that have, and from their experience, I can tell that there is a _lot_ to talk about.
How would you see the certification process taking place, as something like a LTS distribution, that comes out every n ROS distributions?. I'm guessing that officially certifying safe, robust and stable software is a costly process that will have slower dynamics
than that of regular ROS releases.
So, yes, there is interest!. I hope there is more out there.
Best,
Adolfo.
Shaun Edwards
Senior Research Engineer
Manufacturing System Department
http://rosindustrial.swri.org/
Southwest Research Institute
_______________________________________________
ros-users mailing list
ros-users@code.ros.org
https://code.ros.org/mailman/listinfo/ros-users
--
Adolfo Rodríguez Tsouroukdissian
Robotics engineer
adolfo.rodriguez@pal-robotics.com
http://www.pal-robotics.com
PAL ROBOTICS S.L
c/ Pujades 77-79, 4º4ª
08005 Barcelona, Spain.
Tel. +34.93.414.53.47
Fax.+34.93.209.11.09
AVISO DE CONFIDENCIALIDAD: Este mensaje y sus documentos adjuntos, pueden contener información privilegiada y/o confidencial que está dirigida exclusivamente a su destinatario. Si usted recibe este mensaje y no es el destinatario indicado, o el empleado encargado
de su entrega a dicha persona, por favor, notifíquelo inmediatamente y remita el mensaje original a la dirección de correo electrónico indicada. Cualquier copia, uso o distribución no autorizados de esta comunicación queda estrictamente prohibida.
CONFIDENTIALITY NOTICE: This e-mail and the accompanying document(s) may contain confidential information which is privileged and intended only for the individual or entity to whom they are addressed. If you are not the intended recipient, you are hereby
notified that any disclosure, copying, distribution or use of this e-mail and/or accompanying document(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender at the above e-mail address.