Add hyveos_bridge and hyveos_msgs to rolling

[Zollerboy1]

Please Add This Package to be indexed in the rosdistro.

Rolling

The source is here:

• https://github.com/p2p-industries/hyveos_ros.git
• https://github.com/p2p-industries/hyveos_ros_msgs.git

Checks

• All packages have a declared license in the package.xml
• This repository has a LICENSE file
• This package is expected to build on the submitted rosdistro, see https://github.com/p2p-industries/hyveos_ros/actions/runs/12740928363 and https://github.com/p2p-industries/hyveos_ros_msgs/actions/runs/12742117089

[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 Discord Server and ask questions in the #infra-help 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 #infra-help channel on our Discord server.

---

For changes related to yamllint:

• ✅ All new lines of YAML pass linter checks

[christophebedard]

hyveoshyveos_bridge:

• At least one of the following must be present
  • Top level license file: https://github.com/p2p-industries/hyveos_ros/blob/main/LICENSE
  • Per package license files:
• License is OSI-approved: MIT
• License correctly listed in package.xmls: https://github.com/p2p-industries/hyveos_ros/blob/main/package.xml
• Public source repo: https://github.com/p2p-industries/hyveos_ros
• Source repository contains ROS packages
• Each package meets REP-144 naming conventions
  • I wonder if the package should be called hyveos_bridge instead of just hyveos, since it's not HyveOS packaged for ROS
  • The package was renamed from hyveos to hyveos_bridge, so all good

hyveos_msgs:

• At least one of the following must be present
  • Top level license file: https://github.com/p2p-industries/hyveos_ros_msgs/blob/main/LICENSE
  • Per package license files:
• License is OSI-approved: MIT
• License correctly listed in package.xmls: https://github.com/p2p-industries/hyveos_ros_msgs/blob/main/package.xml
• Public source repo: https://github.com/p2p-industries/hyveos_ros_msgs
• Source repository contains ROS packages
• Each package meets REP-144 naming conventions
  • TBD depending on the package above, but I think it's probably fine

[tfoote]

I wonder if the package should be called hyveos_bridge instead of just hyveos, since it's not HyveOS packaged for ROS

I think that this mostly comes down to do we ever expect that a ROS package would depend on hyveos or not. If it's possible that it could become a dependency (most likely a rosdep if this is bridging to it) we don't want to have a potential collision in the naming.

TBD depending on the package above, but I think it's probably fine

The messages relate to hyveos presumably so this should be fine. If it goes through a bridge or not is independent.

[github-actions]

For changes related to yamllint:

• ✅ All new lines of YAML pass linter checks

[Zollerboy1]

@christophebedard @tfoote I agree and have already renamed the hyveos package to hyveos_bridge in https://github.com/p2p-industries/hyveos_ros. The hyveos_msgs package name is fine.

[christophebedard]

Thank you both! Looks good to me now.

[Zollerboy1]

Thanks! I'm getting a build error for hyveos_bridge from the ROS2 build farm, because apparently the rosdep key hyveos_msgs isn't available. Did I do anything wrong or will this sort out over time?

[christophebedard]

This is expected. It's trying to find the hyveos_msgs binary, but it doesn't exist yet.

You should first release the hyveos_msgs package/repo. Once that's done and the package is built, then you will be able to release hyveos_bridge and Rpr/Jpr/Rdev/Jdev jobs will work. Looks like the Rdev job (for example) uses the testing apt repository, so hyveos_msgs should only need to be released (bloom + PR here) and then built by the buildfarm. It won't need to be synced to the main apt repository, which can take some time.

If you don't intend to release your packages, then I think you'll have to put hyveos_msgs and hyveos_bridge in the same git repository for the Rdev/etc. jobs to work. In any case, having both packages in the same git repository would probably simplify the release process.