Meetings2012-02-02 » History » Version 4

Anonymous, 02/02/2012 04:24 PM
RST type consolidation - stable

1 1 J. Moringen
h1. Meetings 2012-02-02
2 2 J. Moringen
3 2 J. Moringen
h2. RST Release Management
4 2 J. Moringen
5 2 J. Moringen
h3. Type Consolidation
6 2 J. Moringen
7 2 J. Moringen
h3. Component-specific (non-domain) Data Types
8 2 J. Moringen
9 2 J. Moringen
* How can these be retrieved?
10 2 J. Moringen
* Mandatory installation to file system?
11 3 S. Wrede
* Other serialization formats than protobuf?
12 2 J. Moringen
13 2 J. Moringen
h2. Meeting Planning
14 2 J. Moringen
15 2 J. Moringen
# Collect additional topics
16 2 J. Moringen
# Determine topic priorities
17 2 J. Moringen
# Roughly assign to meeting slots (~ short-term, mid-term, long-term)
18 4 Anonymous
19 4 Anonymous
h2. Discussion
20 4 Anonymous
21 4 Anonymous
h3. Type Consolidation
22 4 Anonymous
23 4 Anonymous
h4. stable
24 4 Anonymous
25 4 Anonymous
* @rst/audition/ITD.proto@: filename should be fulle name, not abbreviation
26 4 Anonymous
* Forces/Torques/Wrench still sandbox-ish (do you need wreench split up?)
27 4 Anonymous
* Do coordinate types need (optional) coordinate systems and units?
28 4 Anonymous
* Yes, express units right inside the proto file
29 4 Anonymous
** For first release, check, that units are documented in every proto file
30 4 Anonymous
** For next release, check how to express units (enum?)
31 4 Anonymous
* For geometry/pointcloud tyes, check compliance with PCL