Instructions for doing a doc review
See DocReviewProcess for more instructions
- Does the documentation define the Users of the Stack, i.e. for the expected usages of the Stack, which APIs will users engage with?
- Are all of these APIs documented?
- Do relevant usages have associated tutorials?
Have all Packages in the Stack been API reviewed?
Does the Stack conform to the StackDocumentation guidelines?
- Are there Packages in the Stack that don't belong
The one sentence "To make other transports available, you must explicitly build their packages." on the image_transport wiki page is really important. Please highlight it on the image_transport page, and also put it on the image_transport_plugins page.
What kind of images can compressed_image_transport deal with? 8-bit only? Alpha? Indexed?
Everything else looks good.