New package: GIFTI v0.1.0

[JuliaRegistrator]

• Registering package: GIFTI
• Repository: https://github.com/myersm0/GIFTI.jl
• Created by: @myersm0
• Version: v0.1.0
• Commit: 509e72de9c4dd93ac561f0f5666baa8b8f3bbb7f
• Reviewed by: @myersm0
• Reference: https://github.com/myersm0/GIFTI.jl/issues/2
• Description: A Julia package for reading gifti (.gii) neuroimaging surface files

[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.
• Package name similar to 2 existing packages.
  1. Similar to CIFTI. 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 0.65 is at or below cutoff of 2.50.
  2. Similar to NIfTI. Damerau-Levenshtein distance 2 is at or below cutoff of 2. 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.

[myersm0]

Hi, I know there will be some objection to the name of this package, as we had a chat about it on Julia Slack a few months ago. I've re-triggered registration because I just feel compelled to go back and do the right thing here. This is good work: a useful package that fills a need in an important scientific field. It makes Julia language a viable choice (the best choice in my opinion) for researchers in this field. The package name was chosen for purposes of discoverability and harmony with the established Julia ecosystem.

I understand this will get overruled. [noblock]

[odow]

[noblock]

Is there a reason to have it in your personal account rather than JuliaNeuroscience? If it was in the org, I'm in favour. There's precedent, and if all packages are owned by the same org, typo-squatting/name clashes is not a justification.

Here's easy links for reference:

• https://github.com/myersm0/GIFTI.jl
• https://github.com/JuliaNeuroscience/CIFTI.jl
• https://github.com/JuliaNeuroscience/NIfTI.jl

Agree that GIFTIFiles, CIFTIFiles, and NIfTIFiles could have been preferable but that's not where we currently stand, so staying consistent with related packages that were previously accepted seems preferable. (Aside you don't really need to answer: why the lowercase f in NIfTI?)

[myersm0]

I'd be happy to have it in the JuliaNeuroscience org but the catch is that there's already an unregistered GIFTI.jl there. This current package originated from an issue I posted at that older repo. In the end it made sense to develop this as a separate package because it was so different in scope, and shared little code with the original repo. It was suggested a couple times that we replace the original repo or make a PR to it with the new contents, but I think the original author(s) were not receptive to that. [noblock]

[myersm0]

"why the lowercase f in NIfTI?" That's a quirk of the way the three things are spelled in their official specifications. Maybe NIfTI was the first and then they later decided it looked weird and didn't want to continue that tradition. [noblock]

[odow]

[noblock]

I agree with @goerz: https://github.com/JuliaNeuroscience/GIFTI.jl/issues/4#issuecomment-3288449713

Either:

1. Create a single NeuroImagingFiles.jl with these packages as submodules
2. Move GIFTI.jl to the org and then we'll register it

[myersm0]

Option 2 doesn't seem very democratic. I've written a good package that people should be able to use. The old unregistered GIFTI.jl at JuliaNeuroscience is essentially name-squatting.

But, regardless, I respect your decision and will be working on option 1.