forked from ros-infrastructure/rep
-
Notifications
You must be signed in to change notification settings - Fork 1
/
TODO
31 lines (27 loc) · 885 Bytes
/
TODO
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
REP 1, REP Purpose and Guidelines
REP 2, Scope of REP Process, REP Stacks
REP 3, Target Platforms
REP 4, Versioning and Deprecation Process (Tick-Tock)
REP 5, Recommendations for Code Repository Layout
(REP 6)
REP 7, Style Guide for C++ Code
REP 8, Style Guide for Python Code
REP 9, ABI Compatibility
REP 10, Voting Guidelines
(REP 11)
REP 12, Sample reStructuredText REP Template
Not yet written:
REP 5, Recommendations for Repository Layout
- sandbox
- graveyard
- flat layout
- per-stack layout
- svn externals (support scripts)
REP 6, Versioning and Deprecation Process (Tick-Tock)
REP 7, Style Guide for C++ Code
Would be good to write:
Josh's RFC for Code Reviews as REP
tf 2.0 REP coming soon
Message IDL as REP for more general approach
Message Serialization as REP as way to make it easier for wire compatiability/document format.
Common frames for Mobile Robots