Dead link in most (all?) quality declarations

[shonigmann]

Apologies in advance if this is the wrong place to post this fairly minor point, but I noticed that many (if not all) of the Quality Declaration files for core ROS packages have a dead link to a ROS2 Onboarding Guide.

Full excerpt from Coverage [4.iii]:
Current coverage statistics can be viewed here. A description of how coverage statistics are calculated is summarized in this page "ROS 2 Onboarding Guide".

A few examples:
rcl
rclcpp
rmw

Has this guide moved somewhere else or should the reference to it be removed altogether? Is there a better document that we should direct new users (like myself) to, to learn how coverage statistics are calculated?

Thanks!

[clalancette]

Good catch. We took the relevant parts of that guide and moved it elsewhere. Just looking at the rcl one:

• The link to the "package quality categories" looks to be just wrong, and should have pointed to REP-2004 all along
• "Semver" now exists at https://docs.ros.org/en/rolling/Contributing/Developer-Guide.html#versioning
• "Change control process" now exists at https://docs.ros.org/en/rolling/Contributing/Developer-Guide.html#change-control-process
• "Concepts" now exists at https://docs.ros.org/en/rolling/Concepts.html
• "Client libraries" now exists at https://docs.ros.org/en/rolling/Concepts/About-ROS-2-Client-Libraries.html
• "Code coverage" now exists at https://docs.ros.org/en/rolling/Contributing/Developer-Guide.html#note-on-coverage-runs
• "Performance" now exists at https://docs.ros.org/en/rolling/Contributing/Developer-Guide.html#performance
• "Linters" now exists at https://docs.ros.org/en/rolling/Contributing/Developer-Guide.html#linters-and-static-analysis

So we do indeed need an update to all of those quality declarations.

[shonigmann]

I can write a quick script to look for duplicates of those lines, update the links, and submit pull requests in the 40-odd packages with quality declarations if that would be helpful.

Just confirming that the quality declarations in the master branches should be targeting the Rolling documentation?

[clalancette]

Yeah, for the master branches, it definitely should be the Rolling documentation. Thanks for taking this on!

[shonigmann]

Assuming I can automate this a bit, would it be worth updating the branches for other releases as well? E.g. for the foxy branch, update the links if they exist to the foxy equivalent documentation url?

[clalancette]

Assuming I can automate this a bit, would it be worth updating the branches for other releases as well? E.g. for the foxy branch, update the links if they exist to the foxy equivalent documentation url?

Yep, that would be nice. You'll only have to worry about the master branches and the foxy branches; we didn't have Quality Declarations before Foxy.

[clalancette]

@shonigmann Thank you so much for doing this! It really helps a lot.

[shonigmann]

Happy to help!