Adding aruco_markers to index for distro

[david-wb]

Note: It's my first time trying to release a ros2 package. Apologies in advance for any mistakes on my part. I am following these instructions.

Please Add This Package to be indexed in the rosdistro.

humble
jazzy
rolling

The source is here:

https://github.com/namo-robotics/aruco_markers

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

[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

[mjcarroll]

Holding for Rolling sync

[marcoag]

@david-wb can you point out differences (if any) between aruco_ros, aruco_opencv and the one proposed here?

[david-wb]

@marcoag aruco_ros is out-of-date and unmaintained, and was not working with the gazebo camera sensor, so I created this new version which has the following properties:

• Clear and simple API with full examples in the README
• Supports selecting the arcuco dictionary to use
• Works with gazebo camera sensor

I'm not familiar with aruco_opencv but it seems to have similar limitations as aruco_ros, at least for my use case.

[sloretz]

Holding for Rolling sync

[github-actions]

This PR hasn't been activity in 14 days. If you are still are interested in getting it merged please provide an update. Otherwise it will likely be closed by a rosdistro maintainer following our contributing policy. It's been labeled "stale" for visibility to the maintainers. If this label isn't appropriate, you can ask a maintainer to remove the label and add the 'persistent' label.

[christophebedard]

New package checklist:

• At least one of the following must be present
  • Top level license file: https://github.com/namo-robotics/aruco_markers/blob/humble/LICENSE
  • Per package license files:
• License is OSI-approved: MIT
• License correctly listed in package.xmls
• Public source repo: https://github.com/namo-robotics/aruco_markers
• Source repository contains ROS packages
• Each package meets REP-144 naming conventions

@marcoag are you satisfied with the explanation above? #44321 (comment)

[github-actions]

For changes related to yamllint:

• ✅ All new lines of YAML pass linter checks

[github-actions]

For changes related to yamllint:

• ✅ All new lines of YAML pass linter checks

[david-wb]

@christophebedard I haved renamed the project from aruco_ros2 to aruco_markers. Does this help complete the new package checklist above?

[christophebedard]

Yeah, I think that's fine.

Could you re-order your entries alphabetically? See the failing CI job.

[github-actions]

For changes related to yamllint:

• ✅ All new lines of YAML pass linter checks