Meetings2012-02-02 » History » Version 4

Version 3 (S. Wrede, 02/02/2012 04:06 PM) → Version 4/7 (Anonymous, 02/02/2012 04:24 PM)

h1. Meetings 2012-02-02

h2. RST Release Management

h3. Type Consolidation

h3. Component-specific (non-domain) Data Types

* How can these be retrieved?
* Mandatory installation to file system?
* Other serialization formats than protobuf?

h2. Meeting Planning

# Collect additional topics
# Determine topic priorities
# Roughly assign to meeting slots (~ short-term, mid-term, long-term)

h2. Discussion

h3. Type Consolidation

h4. stable

* @rst/audition/ITD.proto@: filename should be fulle name, not abbreviation

* Forces/Torques/Wrench still sandbox-ish (do you need wreench split up?)
* Do coordinate types need (optional) coordinate systems and units?
* Yes, express units right inside the proto file
** For first release, check, that units are documented in every proto file
** For next release, check how to express units (enum?)
* For geometry/pointcloud tyes, check compliance with PCL