Ask Your Question

where to raise documentation issues?

asked 2015-12-08 00:59:43 -0500

Joseph Landau gravatar image

updated 2015-12-08 02:17:03 -0500

Akif gravatar image

When a problem such as a broken link is found in the ROS documentation (for instance, the link for "move_base_msgs/MoveBaseActionGoal" on the page , where should it be reported?

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2015-12-08 02:15:21 -0500

Akif gravatar image

It will be better if you can register from here, and Edit (see figure below) the necessary page using right menu for the corrections.

image description

edit flag offensive delete link more

answered 2015-12-08 02:33:22 -0500

gvdhoorn gravatar image

If you can't fix it yourself (fi because you don't know what would be the proper fix), then it probably makes sense to report it to the issue tracker of the corresponding package (in this case ros-planning/navigation/issues).

As almost all pages are in some way related to packages, that would cover most of them.

As to your specific problem, this has been reported before (see Bad links on The requested URL /api/move_base_msgs/html/msg/MoveBaseActionGoal.html was not found on this server), but didn't get answered. The Groovy version of the links do work (see move_base_msgs Msg/Srv Documentation).

I think the issue is currently actually tracked at ros-infrastructure/roswiki#137 ("MsgSrvDoc macro limited to last ROS version"), as it's not so much a documentation issue (ie: written by humans), as it is an issue with the infrastructure auto-generating those links.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2015-12-08 00:59:43 -0500

Seen: 95 times

Last updated: Dec 08 '15