<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Wonderful! It’s nice to see more formal standards for naming conventions.<div><br></div><div>Two comments:</div><div> </div><div>It would be nice to give a few examples for the prefix rules.</div><div><br></div><div>Are there any rules for robot-specific configurations for other packages; for example navigation and moveit?</div><div><br></div><div>-Austin</div><div><br><div><div>On Mar 1, 2015, at 1:10 PM, Vincent Rabaud <<a href="mailto:vincent.rabaud@gmail.com">vincent.rabaud@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div>Hi all,<br><br>after not knowing how to properly name packages for NAO, I wrote a REP for how to name ROS packages:<br><a href="https://github.com/ros-infrastructure/rep/blob/master/rep-0144.rst">https://github.com/ros-infrastructure/rep/blob/master/rep-0144.rst</a><br>The original discussion with awesome reviewers happened at:<br><a href="https://github.com/ros-infrastructure/rep/pull/94">https://github.com/ros-infrastructure/rep/pull/94</a><br><br>The draft is now in the process of becoming official (or rejected) so if you have any feedback, please continue the discussion here:<br><a href="https://github.com/ros-infrastructure/rep/pull/96">https://github.com/ros-infrastructure/rep/pull/96</a><br><br></div>Thx,<br></div>Vincent<br></div>
_______________________________________________<br>ros-users mailing list<br><a href="mailto:ros-users@lists.ros.org">ros-users@lists.ros.org</a><br>http://lists.ros.org/mailman/listinfo/ros-users<br></blockquote></div><br></div></body></html>