New package: QED v0.1.0

[JuliaRegistrator]

• Registering package: QED
• Repository: https://github.com/QEDjl-project/QED.jl
• Created by: @AntonReinhard
• Version: v0.1.0
• Commit: c43e326e7c2fbe4829b22560dc06320500cdeb3a
• Reviewed by: @AntonReinhard
• Reference: Release QEDjl-project/QuantumElectrodynamics.jl#50 (comment)
• Description: [WIP] QED.jl: A strong-field particle physics framework

[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 which are not met ❌

• Name does not meet all of the following: starts with an upper-case letter, ASCII alphanumerics only, not all letters are upper-case.
• Name is not at least 5 characters long

3. Needs action: here's what to do next

1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

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

[goerz]

[noblock] The documentation is not yet sufficiently complete for registration, and the name QED will probably receive a lot of push-back. Personally, I might be open to the name, but I don’t have high enough permissions in General to make that decision.

[AntonReinhard]

[noblock] Oh, it seems the last documentation update wasn't properly pushed to gh-pages. I'll try to fix this. As for the name, we're aware this doesn't fit the normal requirements, but since the individual packages are all called QEDsomething.jl it would be nice to have the overall package be just QED.jl.

[goerz]

Since the individual packages are all called QEDsomething.jl it would be nice to have the overall package be just QED.jl

I'd consider that a pretty strong argument. With "QED" being pretty widely understood at least by physicists, names like QEDprocesses and QEDfields.jl are great package names (although I would have recommended the more standard CamelCase QEDProcesses and QEDfields – alas, they're already registered). Thus, I would support QED to tie these packages together as a framework. There's a pretty strong bias against acronyms for Julia packages, and especially three-letter-acronyms. However, I wouldn't consider QED to be an acronym in the same sense, given that it is a well-known physics concept, and a nice pun (I think, at least, I never actually looked up who coined the term).

With package names like QED, it also works in favor of the registration if the package is already reasonably polished and is well-maintained. Multiple contributores, and maintainers with a permanent position or backing by a tenured PI or a company go a long way here. From the contribution summary, that seems to be the case here.

In any case, you'll have to ask for a manual merge on Slack after the three-day waiting period.

[noblock]

[goerz]

Followup in #115082