New package: AIFF v0.1.0

[JuliaRegistrator]

• Registering package: AIFF
• Repository: https://github.com/amemya/AIFF.jl
• Created by: @amemya
• Version: v0.1.0
• Commit: 9bd65d227941c14f6f1cae8f21344b12877ff588
• Git reference: HEAD

[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
• Package name similar to 4 existing packages.
  1. Similar to ASDF. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  2. Similar to RAFF. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  3. Similar to ALFA. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  4. Similar to Adiff. 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]

I would probably suggest AudioInterchangeFiles as a package name

[amemya]

Thank you for the suggestion.
However, I'd prefer to keep the name AIFF to stay consistent with audio format packages in the Julia (e.g., WAV.jl, FLAC.jl, MIDI.jl)
Users searching for AIFF support will naturally look for AIFF.jl.

Would it be possible to proceed with manual merge?

[goerz]

Given recent conversations about package naming between registry maintainers, it seems to me extremely unlikely that you will find a full registry maintainer willing to merge AIFF. Realistically, if you want to keep the acronym in the package name for recognizability / searchability (which I agree is a valid concern), you will have to combine it with an explanatory prefix or suffix. For file format packages, the suffix Files or Format is the usual recommendation. That’s a little less than ideal with the tripple F that would result, so maybe you can come up with a better idea, or a suitable prefix. AudioInterchangeAIFF or AudioAIFF might work, or maybe ReadWriteAIFF.

Of course, you can try finding a registry maintainer on Slack willing to make an exception for AIFF, but I think you will get a lot of pushback.

[IanButterworth]

If this were to be moved to the JuliaIO org, then I think there's reasonable precedent there for similar names. FLAC.jl etc. https://github.com/orgs/JuliaIO/repositories

Not saying that it has to be moved, but that AIFF.jl becomes a bit more reasonable if it were.

Note, I say this as someone who generally doesn't help figure out acceptable names though.. so take that with a pinch of salt.

[goerz]

I’m always strongly in favor of putting packages into an organization, but I’d be surprised if that had much of an impact on the name being merged. “Precedent” officially isn’t something that carries much weight. Most of these packages were registered before there was any enforcement of guidelines, and also the guidelines and their application has evolved in the last couple of years. From anyone with merge permissions who has voiced any opinion on this recently, there seems to be no appetite at all for short acronyms as package names going forward. Three-letter names are out completely; four-letter names may not be as clear-cut, but will probably face quite an uphill battle. Package naming seems to be very strongly moving towards clarity/descriptiveness, hence the recommendation to always combine an acronym with an explanatory suffix or prefix. But I suppose it’s worth a try. Personally, I probably would merge AIFF especially as part of a suitable org, but this particular rule is something only a full registry maintainer can override.

[noblock]

[amemya]

Thank you both for the detailed explanation and context regarding the current naming guidelines. I understand that short acronyms now face much stricter scrutiny than before.

Since I am a maintainer of the JuliaAudio organization, I can transfer this repository there.

If the package is maintained under JuliaAudio, would that be sufficient grounds to allow the name AIFF.jl? I would prefer to keep this name for consistency with other audio formats.

I strongly believe that AIFF.jl offers the best discoverability and consistency for users (alongside existing ecosystem packages), so I would really like to pursue this path if there is a possibility.

[goerz]

Since I am a maintainer of the JuliaAudio organization, I can transfer this repository there.

That sounds great!

If the package is maintained under JuliaAudio, would that be sufficient grounds to allow the name AIFF.jl?

Maybe, but I wouldn't make any guarantees. You can try pinging the Slack #pkg-registration channel periodically every few days until you get a response

[github-actions]

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. It would also be helpful if you could post a message in the #pkg-registration channel of the JuliaLang Slack (https://julialang.org/slack/), to increase visibility. [noblock]

[adienes]

random opinion from the peanut gallery: I agree both with

four-letter names will face an uphill battle

and that this appears to be a suitable exception given the existence of WAV.jl, FLAC.jl, MIDI.jl, as well as MP3.jl, FFMPEG.jl, Zarr.jl, Tar.jl, CSV.jl etc. as long as it's in JuliaAudio or JuliaIO

[goerz]

I would merge this if (and only if) this package was part of the JuliaAudio org. And unlike when this was originally submitted, I would now have the ability to do so.

[amemya]

Thank you so much!
Sorry for the delay in getting back to you—I took a bit of a break from development recently.

I have just transferred the repository to the JuliaAudio organization (https://github.com/JuliaAudio/AIFF.jl).
Could you please proceed with the merge when you have a moment?

[goerz]

You have to retrigger the registration. Since the URL changed, that’ll create a new PR, which I can merge at the end of its own 3-day review period

[amemya]

Got it, thank you for the instruction!

I have retriggered the registration from the new repository URL. Here is the new PR:
#150925

I really appreciate your help and your willingness to merge it. I'll wait for the 3-day review period to finish!

[goerz]

Closing in favor of #150925