<div dir="ltr"><div>I guess this whole conversation deserves a proper SIG no ? There seem to be a lot of interest and several things to talk about: standards, policies, reports, software. Actually, just came across an ABI / API breakage site for popular open source projects :<br>
<a href="http://upstream-tracker.org/" target="_blank">http://upstream-tracker.org/</a><br></div>Some of the ones we use in our ecosystem are there:<br><a href="http://upstream-tracker.org/versions/assimp.html">http://upstream-tracker.org/versions/assimp.html</a><br>
<a href="http://upstream-tracker.org/versions/opencv.html" target="_blank">http://upstream-tracker.org/versions/opencv.html</a><br>
<a href="http://upstream-tracker.org/versions/pcl.html" target="_blank">http://upstream-tracker.org/versions/pcl.html</a><br><a href="http://upstream-tracker.org/versions/yaml-cpp.html" target="_blank">http://upstream-tracker.org/versions/yaml-cpp.html</a><br>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Sep 24, 2013 at 6:17 PM, Dejan Pangercic <span dir="ltr"><<a href="mailto:dejan.pangercic@gmail.com" target="_blank">dejan.pangercic@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thibault,<br>
any company if it can it will take open source implementation, at<br>
least as a baseline option. It can of course happen that they will<br>
later contact a developer to get add-on features. However for now they<br>
(Bosch is using ROS for research projects) are wary to use ROS since<br>
there is no connection to standardized code quality indicators at all.<br>
That of course being only one of the reasons.<br>
<br>
I will also say that we haven't started doing these metrics just<br>
because we get bored here. Obviously we talk to other industrial<br>
partners and ROScon participants and to have a way to quickly infer<br>
software quality, possibly against some industrial standard [1] was<br>
identified as one of the biggest needs. I know that ROS is still<br>
predominantly research community that often couldn't care less about<br>
such issues but that is also why we are not forcing them as the<br>
de-facto quality view.<br>
<br>
<br>
[1] - <a href="http://portal.automotive-his.de/images/pdf/SoftwareTest/his-sc-metriken.1.3.1_e.pdf" target="_blank">http://portal.automotive-his.de/images/pdf/SoftwareTest/his-sc-metriken.1.3.1_e.pdf</a><br>
<br>
D.<br>
<div><div>On Tue, Sep 24, 2013 at 1:51 AM, Thibault Kruse <<a href="mailto:kruset@in.tum.de" target="_blank">kruset@in.tum.de</a>> wrote:<br>
><br>
> On <a href="tel:24.09.2013%2002" value="+12409201302" target="_blank">24.09.2013 02</a>:12, Dejan Pangercic wrote:<br>
>>><br>
>>> Selling ROS (even for free) to a company is a marketing problem, it is<br>
>>> about<br>
>>> maintaining a community, a pretty website and advertising, finding<br>
>>> reference<br>
>>> customers speaking up for the product, and so on.<br>
>><br>
>> Thibault this is unfortunately very wrong. Selling ROS is right now<br>
>> rather a technical problem. Say you have<br>
>> $10 available for your micro-controller. And that one has to be<br>
>> certified, has to support some sort of encryption to protect IP, etc.<br>
>> So you end up with the chip like this:<br>
>> <a href="http://www.atmel.com/Images/doc6462.pdf" target="_blank">http://www.atmel.com/Images/doc6462.pdf</a>, note 266MHz. Now you go, put<br>
>> ROS on it and have it run drivers, task-executive, perception,<br>
>> planning and control software.<br>
>> Having metrics like this will not help us with getting ROS to scale to<br>
>> something like this but it will help us convince the industry that<br>
>> coding standards used in ROS are solid and would give us the code that<br>
>> would run on somewhat more powerful processor(s) - which industry<br>
>> would not have hard time to spend more money on.<br>
>><br>
>><br>
>> Also, we do not want to force anyone to use the metrics but it is for<br>
>> now the only way to (quickly) asses the quality of the code,<br>
>> especially if it has been orphaned due to the lack of human resource.<br>
><br>
> Hi Dejan,<br>
><br>
> given that you work at Robert Bosch LLC, you kind-of represent "the<br>
> industry", don't you (as opposed to academia)?<br>
> And if Bosch as a company would like a vendor to provide some code, maybe<br>
> Bosch can negotiate that directly?<br>
><br>
> cheers,<br>
> Thibault<br>
><br>
> _______________________________________________<br>
> ros-users mailing list<br>
> <a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
> <a href="http://lists.ros.org/mailman/listinfo/ros-users" target="_blank">http://lists.ros.org/mailman/listinfo/ros-users</a><br>
<br>
<br>
<br>
</div></div><span><font color="#888888">--<br>
Dejan Pangercic<br>
Autonomous Technologies Group<br>
Robert Bosch LLC<br>
Office: <a href="tel:%2B16505657403" value="+16505657403" target="_blank">+16505657403</a><br>
Cell: <a href="tel:%2B16508610951" value="+16508610951" target="_blank">+16508610951</a><br>
E-Mail: <a href="mailto:dejan.pangercic@gmail.com" target="_blank">dejan.pangercic@gmail.com</a><br>
WWW: <a href="http://ias.cs.tum.edu/people/pangercic" target="_blank">http://ias.cs.tum.edu/people/pangercic</a><br>
</font></span><div><div>_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
<a href="http://lists.ros.org/mailman/listinfo/ros-users" target="_blank">http://lists.ros.org/mailman/listinfo/ros-users</a><br>
</div></div></blockquote></div><br></div></div>