Reviewer: kwc

Instructions for doing a doc review

See DocReviewProcess for more instructions

  1. Does the documentation define the Users of the Stack, i.e. for the expected usages of the Stack, which APIs will users engage with?
  2. Are all of these APIs documented?
  3. Do relevant usages have associated tutorials?
  4. Have all Packages in the Stack been API reviewed?

  5. Does the Stack conform to the StackDocumentation guidelines?

  6. Are there Packages in the Stack that don't belong

Concerns / issues

Fairly straightforward. Minor fixes that were easy to do:

  • Minor updates to package manifests for clarity and readability
  • Added link to visualization_common
  • Updated stack manifest description to indicate new inclusion of rxbag plugins and added links.


Doc reviewed, pending viewing of manifest changes via rosdoc generation

Wiki: visualization/Reviews/2010-01-07_Doc_Review (last edited 2010-01-09 00:55:40 by KenConley)