design

design copied to clipboard

This was brought up in the component life cycle discussion in #34 but deferred [here](https://github.com/ros2/design/pull/34#issuecomment-141509421)

tfoote

This was cut from the component life cycle discussion in #34 Ticketing separately re: [this comment](https://github.com/ros2/design/pull/34#issuecomment-141509421)

tfoote

Partitions, topics, and ROS namespacing

10

I've been reading up on the topic and service mapping article, having seen that the partition PR landed back in March: https://github.com/ros2/design/blob/gh-pages/articles/140_topic_and_service_name_mapping.md I wanted to feel out how "locked in"...

spiderkeys

Fix #96 Add EBNF grammar for ROS2 names in self-testing python script

4

Prototype for #96. Since last time I extended a bit. Because of the fully-qualified vs. non-fully-qualified, the grammar has grown a bit. The grammar still does not prevent double underscores,...

tkruse

finish EBNF for topic and service names

3

See: https://github.com/ros2/design/pull/90#issuecomment-247329344

wjwwood

See: https://github.com/ros2/design/pull/97#issuecomment-257142994

wjwwood

Based on feedback, changes todo: - [x] Use the term `communication graph` rather than `data layer graph` or `data layer`. - [ ] Write abstract - [ ] Rewrite problem...

wjwwood

design how to support component node migration between containers

2

This was mentioned in #34 but needs it's own discussion. deferred [here](https://github.com/ros2/design/pull/34#issuecomment-141509421)

tfoote

Write documentation design document

1

AC: - [x] Whitepaper describing the documentation process - [ ] Examples for how to write documentation with the different tools Follow up ticket: implementing the toolchain.

dirk-thomas

Extend @key annotation documentation

1

This PR extends the `@key` annotation documentation.

Mario-DL