New package: MP3IO v1.1.0

[JuliaRegistrator]

• Registering package: MP3IO
• Repository: https://github.com/JuliaLibs/MP3IO.jl
• Created by: @clouds56
• Version: v1.1.0
• Commit: b9512e35593102b4d06304bf864f5cb2688467c9
• Reviewed by: @clouds56
• Reference: https://github.com/JuliaLibs/MP3IO.jl/issues/5#issuecomment-3272101431
• Description: MP3 codec for Julia using JuliaAudio idioms. LAME and mpg123 working under the hood

[github-actions[bot]]

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.
• I was not able to load the package (i.e. import MP3IO failed). See the AutoMerge logs for details.
• Package name similar to 1 existing package.
  1. Similar to MPI. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

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]

My recommendation for the package name would probably be MP3Codec. However, this being a fork, I think it would be preferable to continue developing the project under the original organization (https://github.com/JuliaAudio). Can you contact the owners of the JuliaAudio organization and ask them to add you as a maintainer for the existing https://github.com/JuliaAudio/MP3.jl? Then, you could rename that package and register it.

It would also be important to update the README, and to ensure that it actually works, i.e., that the tests run through in CI.

[goerz]

@ssfrr, @rob-luke

[clouds56]

Thanks for kindly reply, I also think it would be excellent if the original repo continuing to be maintained. Actually the code in MP3.jl which last modified 4 years ago still work today on julia 1.11. I think there's nothing blocking the original repo to be registered, but sadly the issue https://github.com/JuliaAudio/MP3.jl/issues/23 hasn't been updated these years.

I'd like to rename the package to MP3Codec after final decision.

[goerz]

Let's wait a day or two to see if @ssfrr or @rob-luke are around and can manage this. If not, let's see if there's someone on Slack that can help with getting you into the @JuliaAudio organization.

[ssfrr]

Hey there - I'm pretty out-of-practice with registering Julia packages. I'm merging the queue of PRs to update to the latest conventions. Once that's wrapped up I should be able to go through with the registration. Thanks for the poke.

[goerz]

Thanks for the response, @ssfrr!

It might be good to just add @clouds56 as a maintainer to the project. First, they would have to become a member of the JuliaAudio organization. Then, they would have to be added to the list of "Owners" for the MP3 package. That is under the assumption that you're not really planning to maintain the package going forward, and that @clouds56 would like to step in. Of course, you will maintain ownership as well.

@clouds56 Is there anything further you have planned for this package, or is this just to get it registered? Whoever ends up doing the registration, this should still probably be renamed to MP3Codec, just because MP3 is going to get blocked by the bot, and getting a manual merge can be a major pain. And, like I said, make sure the README is up-to-date and the package verifiably still works, based on CI.

[clouds56]

Is there anything further you have planned for this package, or is this just to get it registered?

Currently just get it registered. I believe the functionality in MP3.jl/MP3Codec.jl is quite stable and there's nothing to be done in the near future. Given that @ssfrr would like to periodically review PR, I'm happy with current state as I could contribute when it got broken.

[goerz]

Alright, then I'll just leave it to @ssfrr to rename / register the package. If you (either of you) run into trouble, feel free to reach out here, on Slack or on Discourse

[clouds56]

ping @ssfrr any thoughts on the rename? I've drafted a PR, would you mind review it.

[github-actions[bot]]

This pull request has been inactive for 30 days and will be automatically closed 7 days from now. If this pull request should not be closed, please either (1) fix the AutoMerge issues and re-trigger Registrator, which will automatically update the pull request, or (2) post a comment explaining why you would like this pull request to be manually merged. [noblock]

[clouds56]

not stale

[github-actions[bot]]

This pull request has been inactive for 30 days and will be automatically closed 7 days from now. If this pull request should not be closed, please either (1) fix the AutoMerge issues and re-trigger Registrator, which will automatically update the pull request, or (2) post a comment explaining why you would like this pull request to be manually merged. [noblock]

[clouds56]

ping @ssfrr