New package: HemiPlots v0.1.0

[JuliaRegistrator]

• Registering package: HemiPlots
• Repository: https://github.com/RUzcategui/HemiPlots.jl
• Created by: @RUzcategui
• Version: v0.1.0
• Commit: f96de5fbdea8a75d22d2db14527506780a3f7e5b
• Reviewed by: @RUzcategui
• Reference: https://github.com/RUzcategui/HemiPlots.jl/commit/f96de5fbdea8a75d22d2db14527506780a3f7e5b#commitcomment-176092277
• Description: Hemispherical projection tools for structural geology and crystallography in 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 are all met! ✅

Your new package registration met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed.

3. 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]

Thank you for submitting your package! The name similarity is a false positive, so I've applied the override for that. However: could you add a little bit of documentation before registering? At the very least, that would be a description of the package's purpose and a small usage example in the README. An important part of packages in General is that any potential user can figure out what the package is about and how to get started with using it. That is really difficult when there is no documentation.

In the longer term, I definitely recommend setting up a Documenter-based documentation. Before a v1.0 release, or for smaller packages that can be effectively described entirely with their README, that's not a requirement, though.

Since this is a package for visualization, I would recommend showing an exemplary output in the README.