New package: GhpGhx v0.1.0

[JuliaRegistrator]

• Registering package: GhpGhx
• Repository: https://github.com/NREL/GhpGhx.jl
• Created by: @Bill-Becker
• Version: v0.1.0
• Commit: 987dc6645abe34af7e10c49f78c093f0b86bef8a
• Reviewed by: @Bill-Becker
• Reference: NREL/GhpGhx.jl@987dc66#commitcomment-78239321
• Description: This package is used for sizing a ground heat exchanger to serve the specified heating and cooling loads. This package is called by REopt.jl when GHP is considered in a REopt evaluation.

[github-actions]

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:

• No licenses detected in the package's top-level folder. An OSI-approved license is required.

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.

[Bill-Becker]

This package is a dependency of an open source energy modeling tool REopt.jl, but this requires a slightly more restricted license that is defined by its LICENSE.md. Can we please get an exception to the OSI-approved license since this supports the open source REopt.jl?

[ericphanson]

Sorry, we can’t make exceptions. Quoting from @giordano

this registry is maintained by volunteers, we don't have a legal team that can thoroughly review any added clause, as simple as it may seem to you. Restriction of use (like no commercialisation), however, often goes against some definitions of open source software (it certainly violates one of the freedoms in the definition of free software). Simply using OSI-approved licenses with no added custom clauses is the best way for us to ensure we have packages legally sounding license.

#31549 (comment)

The following comment also looks relevant here as well:

I will add here that any "no commercialization" clause is almost certain to conflict with the GPL: the GPL requires that the derived work be available under terms compatible with the GPL, which guarantees a wide range of freedoms, regardless of the nature of the application. Since Julia by default ships with GPL libraries, it is very likely that any work derived from a package with this license would be illegal. While it's probably ok to have the end user load the package themselves, it is likely that any application that includes the package would not be legal. It would be necessary to compile a no-GPL version of Julia from source in order to legally create a work derived from the package.

#31549 (comment)

[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. [noblock]

[Bill-Becker]

@ericphanson Thank you for the feedback; we've found a workaround with Requires.jl that allows this unregistered package to be a conditional dependency of the registered package. This requires users of the registered package to "add [GhpGhx.jl]" to their project environment in order to use those certain capabilities in the registered package. I will close this PR.