New package: MinCostFlows v0.1.2

[JuliaRegistrator]

• Registering package: MinCostFlows
• Repository: https://github.com/NREL/MinCostFlows.jl
• Created by: @GordStephen
• Version: v0.1.2
• Commit: 3e0168ff93c0d95cae96b5a1a42ca03c7576efc4
• Reviewed by: @GordStephen
• Reference: NREL/MinCostFlows.jl@3e0168f#commitcomment-149855397
• Description: Fast min-cost flow solver for network optimization in PRAS

[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 are all met! ✅

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

3. 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.

[GordStephen]

Regarding the license: there is indeed a license, but it's "modified" MIT Expat . My understanding is that, at least in 2019 when this software was licensed, it was corporate policy to require that "THE UNITED STATES, THE UNITED STATES DEPARTMENT OF ENERGY, OR ANY OF THEIR EMPLOYEES" be explicitly added to the liability waiver language.

Hopefully this isn't a blocker. If it is, I can talk to our tech transfer people about relicensing the software, but if there's any latitude to accept it as-is that would make things a lot easier.

[noblock]

[goerz]

[noblock]

My understanding is that there was a decision that an OSI-approved license is a hard requirement. There is no leeway for any kind of modifications beyond what the automated bot still manages to recognize. I wasn't involved in that discussion, but I think the argument was that the Julia community is not equipped to understand what modifications to a license might legally imply. Even if it's a trivial modification such as this one, I'm not sure if there's any registry maintainer who would want to manually override the check somehow. This is especially true because AFAIK the license check is not just performed on the initial registration, but also on all subsequent updates. So, every update of the package would have to be merged manually.

Your best bet is probably to use a LICENSE file that makes the bot happy. If it's not possible to sneak in the extra text somehow (the bot does swallow some minor modifications, possibly at the beginning and end, not sure), I would include the extra text in some other place. For example, put the current modified license text at the bottom of your README. I'm not a lawyer, but I don't think the unmodified MIT and your modified MIT are in any way incompatible, or that the note would be any more or less binding if it appeared in the README. Quite honestly, my common-sense legal opinion is that the extra note about the U.S. government is completely redundant. In that vein, you could try to clarify whether that extra language is still necessary. Or, probably better, don't make a fuss about it and find a pragmatic workaround. I suspect you're not going to get into any kind of trouble (even if you were to just completely drop the extra language from the LICENSE), but make your own judgement on that.

[GordStephen]

Ok, thanks - that's understandable. I suspect this won't be a big deal to change on our end, but with the holiday here it'll just take a few days to get sorted.

[noblock]