New package: SciMLPublic v1.0.0

[JuliaRegistrator]

• Registering package: SciMLPublic
• Repository: https://github.com/SciML/SciMLPublic.jl
• Created by: @AayushSabharwal
• Version: v1.0.0
• Commit: 9bbc1dcdf6f2df8a8441b1ca1fdf0a24e071bb4d
• Reviewed by: @AayushSabharwal
• Reference: Register SciML/SciMLPublic.jl#2 (comment)

[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]

[noblock] Although it is probably obvious to people intimately familiar with the public keyword that was added in Julia 1.11, I would very much recommend adding a few paragraphs to the README of this package to give context. Explain what problem this package tries to solve, what the alternative solutions and tradeoffs are, and what the policies for using SciMLPublic.jl within the SciML organization are. You might want to link to the Discourse discussion on "Is Compat.jl worth it for the public keyword?" (and, maybe also add a post to the thread to "announce" this new package). Maybe mention https://github.com/JuliaLang/Public.jl and explain why, even though there was pushback against registering that package, it was deemed sufficiently useful in the context of SciML to register it now.

[AayushSabharwal]

[noblock] Thanks for the input. I'll make the suggested changes soon.