New package: ROJ v0.1.0

[JuliaRegistrator]

• Registering package: ROJ
• Repository: https://github.com/Michi-Tsubaki/ROJ.jl
• Created by: @Michi-Tsubaki
• Version: v0.1.0
• Commit: 84fb13f92f4a312d654cce85abdb991424c0b7d5
• Reviewed by: @Michi-Tsubaki
• Reference: julia official pkg Michi-Tsubaki/ROS2.jl#6 (comment)
• Description: Robot Operating tool using Julia

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines which are not met ❌

• Name does not meet all of the following: starts with an upper-case letter, ASCII alphanumerics only, not all letters are upper-case.
• Name is not at least 5 characters long
• I was not able to load the package (i.e. import ROJ failed). See the AutoMerge logs for details.
• Package name similar to 8 existing packages.
  1. Similar to ROS. Damerau-Levenshtein distance 1 is at or below cutoff of 2. Damerau-Levenshtein distance 1 between lowercased names is at or below cutoff of 1. Normalized visual distance 1.84 is at or below cutoff of 2.50.
  2. Similar to MLJ. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  3. Similar to RAI. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  4. Similar to QOI. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  5. Similar to Run. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  6. Similar to ROOT. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  7. Similar to SOM. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  8. Similar to Proj. Damerau-Levenshtein distance 1 between lowercased names is at or below cutoff of 1.

3. Needs action: here's what to do next

1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

4. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

[goerz]

While acronyms like ROJ are very frowned upon in the Julia community, there are generally exceptions for wrapper packages, which usually can use the name of the wrapped package. That tends to be the least confusing for the user, and is often preferable to coming up with a "Julian" name. In fact, a package with a non-Julian name can serve as a signal that the package wraps something from another language.

I'm not really familiar with ROS, but it does seem like "ROS 1" and "ROS 2" are official names. For ROS 1, my understanding is that we have https://github.com/gstavrinos/ROS.jl by @gstavrinos (unmaintained?), and this package would target "ROS 2". As such, I think ROS2 might actually be the most appropriate name for this package. Of course, that absolutely does not pass the automatic rules, and would have to be merged manually by a registry maintainer. I would recommend checking in the #pkg-registration channel on Slack for some more community feedback on this.

[goerz]

Closing in favor of #124282