-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New REP 135 for Driver Namespaces #22
Conversation
Proposed informational REP on driver namespaces.
It's mature enough to get a number. Please use 135. |
Posted to ROS Users on 2/20/2013. Will call a vote on 2/27/2013. |
@chadrockey: Please add a reference to the REP pointing to the discussion. |
@dirk-thomas I don't see where other REPs provide a reference to their own discussion. If this is expected, where should I place that reference? Is there a new header field? |
Just add it to a reference chapter at the end of the rep. |
@dirk-thomas References added. |
@tfoote This should be ready to merge. |
New REP 135 for Driver Namespaces Merging as Active
Proposed informational REP on driver namespaces. Not sure if I should assign a number, so I did not do so to avoid conflicts.
As of 2/11/2013, this is under review in ros-sig-drivers@googlegroups.com