Add nav2_config for humble and jazzy

[sutharsan-311]

Description

Adds nav2_config to the ROS2 humble and jazzy distributions.

nav2_config is a real-time visual parameter tuning GUI for Nav2. It connects to a live Nav2 stack and lets you tune navigation parameters without killing and relaunching nodes — no more edit–kill–relaunch–wait–test cycles.

• GitHub: https://github.com/sutharsan-311/nav2_config
• Release repo: https://github.com/sutharsan-311/nav2_config-release
• License: Apache-2.0
• 59+ GitHub stars, community-verified on Turtlebot4 + Raspberry Pi 5 (Jazzy) and production AMR deployments (Humble)

Distros: humble, jazzy
Version: 0.1.0-1
Status: developed

CI passing on both humble (Ubuntu 22.04) and jazzy (Ubuntu 24.04):
https://github.com/sutharsan-311/nav2_config/actions

[github-actions]

Thanks for sending a pull request to ROS distro!

This is an automated tool that helps check your pull request for correctness.
This tool checks a number of attributes associated with your ROS package and generates a report that helps our reviewers merge your pull request in a timely fashion. Here are a few things to consider when sending adding or updating a package to ROS Distro.
ROS Distro includes a very helpful CONTRIBUTING.md file that we recommend reading if it is your first time submitting a package.
Please also read the ROS Distro review guidelines which summarizes this release process.

ROS Distro Considerations

• ROS Distributions are created using REP-134 Standards Track as a guide.
• Your package name should comply to REP-144 ROS Package Naming
• Your package must build for all platforms and architectures on the ROS buildfarm. See REP-2000 ROS Releases and Supported Platforms for all supported platforms for your ROS Distro.
• Your package must contain an OSI approved license. Your package.xml file must also include that license in a machine readable format. See REP-149 Package Manifest Format Three Specification for additional details.
• A publicly available, open source, repository for your ROS package.
• While not required, we recommend that you create an account for ROS Discourse and subscribe to the appropriate release topic.
• If you would like, you may join our Zulip Server and ask questions in the Infrastructure General channel.

Package Considerations

Having your package included in a ROS Distro is a badge of quality, and we recommend that package developers strive to create packages of the highest quality. We recommend package developers review the following resources before submitting their package.

• REP-2004 Package Quality Declaration-- The ROS 2 TSC has created a quality rating system for ROS packages. These ratings should serve as a guide for package developers. We recommend package developers achieve a quality level of three or higher.
• Documentation -- it is recommended that ROS packages include an extensive README.md file, and API level documentation using the Sphinx documentation system.
• Maintainer Responsibilities -- the ROS 2 documentation includes a guide to ROS package maintainer responsibilities that summarizes your responsibilities as an open source maintainer. While we do not enforce these requirements on package maintainers they should be considered best practices.
• We recommend that your package should strive to conform to the ROS 2 Developer Guide and the ROS 2 Style Guide.

Need Help?

Please post your questions to Robotics Stack Exchange or refer to the Infrastructure General channel on our Zulip server.

---

For changes related to rosdistro:

• ✅ New repositories are named appropriately
• ✅ New packages are named appropriately
• ❌ Changes to release stanzas across multiple distributions are not permitted

For changes related to yamllint:

• ❌ One or more linter violations were added to YAML files

[github-actions]

Changes to release stanzas across multiple distributions are not permitted

[github-actions]

Changes to release stanzas across multiple distributions are not permitted

[github-actions]

This line does not pass YAML linter checks: wrong ordering of key "nav2_config" in mapping

[github-actions]

For changes related to rosdistro:

• ✅ New repositories are named appropriately

For changes related to yamllint:

• ✅ All new lines of YAML pass linter checks

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[mjcarroll]

• At least one of the following must be present
  • Top level license file: LICENSE (Apache-2.0)
  • Per package license files:
• License is OSI-approved: Apache-2.0
• License correctly listed in package.xmls
• Public source repo: https://github.com/sutharsan-311/nav2_config
• Source repository contains ROS packages
• Each package meets REP-144 naming conventions

Package name details

$ find . -name "package.xml" -exec grep --color=auto -e "<name>" "{}" ";"
<name>nav2_config</name>

License details

$ find . -name "package.xml" -exec grep --color=auto -e "<license>" "{}" "+"
<license>Apache-2.0</license>

[sutharsan-311]

Thanks @mjcarroll! On the release repo — I'll generate it properly with bloom-release rather than the hand-rolled entry, but I'm holding off on that until the name is settled.

On the name: rather than assume, I opened ros-navigation/navigation2#6230 to ask the Nav2 maintainers directly whether they're comfortable with nav2_config in their namespace or would prefer I move it out (and whether they'd want to upstream it). Once they weigh in I'll either keep the name or rename, then run bloom-release and update this PR accordingly. Will report back here.