New package: JuDGE v0.4.6

[JuliaRegistrator]

• Registering package: JuDGE
• Repository: https://github.com/EPOC-NZ/JuDGE.jl
• Created by: @adow031
• Version: v0.4.6
• Commit: 800b8aae8a4cce9ca4669d2d9200411aa99a7e16
• Git reference: master
• Description: An interface for solving a stochastic capacity expansion problem via a Dantzig-Wolfe decomposition algorithm

[github-actions[bot]]

Your new package pull request does not meet the guidelines for auto-merging. Please make sure that you have read the General registry README and the AutoMerge guidelines. The following guidelines were not met:

• Package name starts with "Ju".
• Package name similar to 1 existing package.
  1. Similar to JuDoc. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

After you have fixed the AutoMerge issues, simple retrigger Registrator, which will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number).

If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged.

Since you are registering a new package, please make sure that you have also read the package naming guidelines: https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1

---

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.

[adow031]

I would like this package registered with its current name: JuDGE.

This package has been known as JuDGE since 2018, and has been presented with this name at academic conferences over the last 5 years. JuDGE has been used in this published paper, and has been or is being used by academic researchers in Oceania, Europe, North America and Asia.

JuDGE offers a suite of functionality for multi-stage capacity planning problems, including a modelling framework which builds on JuMP, decomposition algorithms, along with analysis and visualisation tools.

We would like JuDGE to be registered so that it's easier for users to access, and so other packages can set JuDGE as a dependency, if necessary.

Thanks for considering this request, Tony.

Dr Anthony Downward, Engineering Science, University of Auckland, New Zealand.

[cormullion]

[noblock] Fyi: JuDoc isn’t a thing anymore. It was renamed to Franklin.

[odow]

[noblock] @adow031 I've pinged the slack channel.

Per https://pkgdocs.julialang.org/dev/creating-packages/#Package-naming-guidelines-1

Avoid using Julia in your package name or prefixing it with Ju.

• It is usually clear from context and to your users that the package is a Julia package.
• Package names already have a .jl extension, which communicates to users that Package.jl is a Julia package.
• Having Julia in the name can imply that the package is connected to, or endorsed by, contributors to the Julia language itself.

In this case, the use of "Ju" isn't to distinguish it as a Julia package or to claim affiliation; it's just to make a nice acronym.

[goerz]

[noblock] I think the name is great, but do you want to release this from a fork-repo?

[odow]

[noblock]

but do you want to release this from a fork-repo?

Ah. I missed this.

@reganbaucke is okay with the move to @EPOC-NZ, but for simplicity it's probably best to move the repo instead of registering off a fork.

@adow031 you could push your latest changes to Regan's repo, then get him to transfer to EPOC.

If you go to the settings page, then scroll to the bottom, you'll see:

[odow]

[noblock] @StefanKarpinski approves, which I hope is good enough:

So we just need @adow031 to decide the fork issue.

[adow031]

[noblock] @StefanKarpinski approves, which I hope is good enough:

So we just need @adow031 to decide the fork issue.

I've contacted @reganbaucke with the suggestion that I perform a pull request, and once that's accepted I will delete the EPOC-NZ repo. He can then transfer the ownership, and then fork from EPOC-NZ if he wishes.

[odow]

@adow031 I think you can also request that the fork be detached here: https://support.github.com/request/fork

[adow031]

@adow031 I think you can also request that the fork be detached here: https://support.github.com/request/fork

Thanks for that tip. I've detached the repo. Do I need to apply again to be added to the registry?

[odow]

No, this just needs a manual merge now.

[odow]

Thanks @fredrikekre