Skip to content

New packages: PRASCore, PRASFiles, PRASCapacityCredits, PRAS v0.7.0#120786

Closed
GordStephen wants to merge 4 commits intoJuliaRegistries:masterfrom
GordStephen:master
Closed

New packages: PRASCore, PRASFiles, PRASCapacityCredits, PRAS v0.7.0#120786
GordStephen wants to merge 4 commits intoJuliaRegistries:masterfrom
GordStephen:master

Conversation

@GordStephen
Copy link

This is a manual pull request, prepared with LocalRegistry.jl, to simultaneously register v0.7.0 of four packages from NREL's Probabilistic Resource Adequacy Suite (PRAS). The four packages are PRASCore.jl, PRASFiles.jl, PRASCapacityCredits.jl, and PRAS.jl, a convenience metapackage that loads all the others. All four packages reside in https://github.com/NREL/PRAS

For convenience I'll try to proactively talk through some of the automerge checks:

  • About the package name - yes, we realize this probably isn't going to be looked on too favorably, particularly PRAS.jl which fails multiple automerge rules. PRAS as a brand exists outside of the Julia ecosystem (e.g. https://www.nrel.gov/analysis/pras.html) and we're hoping we can get an exception on this. We received feedback from @goerz and @gdalle in New package: SiennaPRASInterface v0.1.0 #120172 that this may be possible, and are hoping folks here agree?

  • About the repository name - while today PRAS is exclusively a Julia project, we're actually in the middle of a rewrite and our monorepo will be hosting Rust, Julia, and Python code in the near future. So we don't think having a repo name that ends in .jl would be appropriate.

  • About the version number - while 0.7.0 is the first version of PRAS submitted to General, it is not the first version of PRAS. v0.6 and earlier were registered in NREL's public registry (https://github.com/NREL/JuliaRegistry).

  • All four packages are MIT licensed and a copy of the license is included in each of the respective subdirectories of the monorepo.

Happy to answer any further questions or take feedback if there are things here we should be doing differently!

UUID: c5c32b99-e7c3-4530-a685-6f76e19f7fe2
Repo: git@github.com:NREL/PRAS.git
Tree: 7f876920fc9727874f5601a967a3a387c80b9903
UUID: 2e1a2ed5-e89d-4cd3-bc86-c0e88a73d3a3
Repo: git@github.com:NREL/PRAS.git
Tree: 014e55f5662b8685a644108ce7fac68707ce1221
UUID: a2806276-6d43-4ef5-91c0-491704cd7cf1
Repo: git@github.com:NREL/PRAS.git
Tree: cee023d07cb0550360809a56273ea2960e7e4b82
UUID: 05348d2-1c52-11e9-35e3-9d51842d34b9
Repo: git@github.com:NREL/PRAS.git
Tree: 21a22aff68a92d6b30a0e8bfcdee6613951f08eb
@goerz
Copy link
Member

goerz commented Dec 6, 2024

Given the maturity of the project, I don’t see any problem with the name PRAS and would be happy to see this merged.

You will probably have to go on Slack and post a message in the #pgk-registration channel to find someone with merge permissions.

@GordStephen
Copy link
Author

Per guidance on Slack, we're submitting these individually via Registrator with the understanding that this PR will count as the three days waiting period.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants