design icon indicating copy to clipboard operation
design copied to clipboard

Design documentation for ROS 2.0 effort

Results 53 design issues
Sort by recently updated
recently updated
newest added

Start of the design page for the ROS 2 Embedded effort. Includes contributions by all of the OFERA consortium partners.

in progress

Follow-up of https://github.com/ros2/rcl/pull/235 This could either be done once the parser is fully implemented or done anytime before to reflect the current state and extend the design document when the...

enhancement

The [remapping design doc](http://design.ros2.org/articles/static_remapping.html) states that `/namespace/` is only prefixed to the match side of a rule if it does not begin with `*`, `**`, or `/`. This means the...

enhancement

The [remapping design doc](http://design.ros2.org/articles/static_remapping.html) does not state whether `**` is greedy or lazy. This can change the outcome of some remap rules. ### Example: * rule `/**/foo/**:=/\1/\2` * name `/foo/bar/foo/bar`...

question

Originally from @andreasBihlmaier in https://github.com/ros2/design/pull/70: Please add a short paragraph about "Binary compatibility of message revisions" in the current DDS implementation. For me the most relevant question is whether it...

enhancement
question

This issue serves to track ideas for specifying the policy format to be used for access control in SROS2. Ideally this specification should be extensible enough to convey all necessary...

enhancement

The [_Examples and Ideas for Communicating with Non-ROS Topics_](http://design.ros2.org/articles/topic_and_service_names.html#examples-and-ideas-for-communicating-with-non-ros-topics) section in [_Topic and Service name mapping to DDS_](http://design.ros2.org/articles/topic_and_service_names.html) article presents an example where a DDS topic name containing a forward...

help wanted

The previous version of the document only gave an ambiguous description of the external interface used to manage a node's life cycle. This pull request describes the interface in detail,...

requires-changes

This issue serves to track ideas for specifying the security event logging to be used in SROS2. Ideally this specification should be extensive enough to enable security monitoring and auditing...

enhancement

Now that C and C++ interface [types diverged](https://github.com/ros2/rosidl/pull/211) we should create a design doc defining how each IDL (msg) type is mapped to C. It should also be added to...

help wanted