New package: AxisKeysExtra v0.1.9

[JuliaRegistrator]

• Registering package: AxisKeysExtra
• Repository: https://github.com/JuliaAPlavin/AxisKeysExtra.jl
• Created by: @aplavin
• Version: v0.1.9
• Commit: 0000000065d69673f7f40c0f93f01ba0fbbbda34
• Reviewed by: @aplavin
• Reference: JuliaAPlavin/AxisKeysExtra.jl@0000000#commitcomment-141731774

[github-actions]

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

Since you are registering a new package, please make sure that you have read the package naming guidelines: https://pkgdocs.julialang.org/v1/creating-packages/#Package-naming-guidelines

---

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. You can edit blocking comments, adding [noblock] to them in order to unblock auto-merging.

[goerz]

This is less than ideal. It would be a much better outcome if @mcabbott could transfer AxisKeys.jl to an organization (cf. mcabbott/AxisKeys.jl#110 (comment)) and if @aplavin could act as a co-maintainer and add new features directly. At least unless @mcabbott has a particular reason to want to keep AxisKeys extremely "stable".

I'm just blocking this temporarily for some community discussion. If there's no path forward for contributing to AxisKeys directly, I have no objections to this registration.

I raised the issue in the #pgk-registration channel on Slack

[noblock]

[aplavin]

I'm glad that this registration helped to progress that old AxisKeys PR of mine :) Merged that.

Still, would be nice to register AxisKeysExtra as well, is there anything preventing it? Three days have passed, and the name seems straightforward without any conflicts.

It's totally reasonable to have a stable package providing base well-tested functionality, with an "xxxExtra(s)" package containing more opinionated/experimental/less well-tested/less documented functions. This happens in the Julia ecosystem, see some packages at https://juliahub.com/ui/Search?q=Extra&type=packages.
As AxisKeysExtra is not a fork, it works with the exact same structs defined in AxisKeys and doesn't have any potential to split the ecosystem.

[noblock]

[goerz]

[noblock] Sure! I unblocked my comment

[goerz]

[noblock] (note that you have to unblock your own comment as well)