New package: Q2 v0.2.0

[JuliaRegistrator]

• Registering package: Q2
• Repository: https://github.com/p-casgrain/Q2.jl
• Created by: @p-casgrain
• Version: v0.2.0
• Commit: ce1b73dd8ca47ff5de69bb2b1934cc6e55626482
• Git reference: HEAD
• Description: Connect Julia and kdb

[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

• There is no compat entry for julia.

• The following dependencies do not have a [compat] entry that is upper-bounded and only includes a finite number of breaking releases: DataFrames, Missings, Revise, Tables, TimesDates

  Extended explanation

  Your package has a Project.toml file which might look something like the following:

  name = "YourPackage"
  uuid = "random id"
  authors = ["Author Names"]
  version = "major.minor"
  
  [deps]
  # Package dependencies
  # ...
  
  [compat]
  # ...

  Every package listed in [deps], along with julia itself, must also be listed under [compat] (if you don't have a [compat] section, make one!). See the Pkg docs for the syntax for compatibility bounds, and this documentation for more on the kinds of compat bounds required for AutoMerge.

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]

The package serves as a replacement to the unmaintained and outdated Q.jl

While by today’s standards, there is probably no way that a package Q could be registered, given that it exists, the name Q2 seems reasonable.

[noblock]

[gdalle]

Maybe we could actually replace Q without a new package, just by making the general registry point to this new repo? The last release of Q was 7 years ago

[goerz]

@p-casgrain Did you at any point try to reach out to @abalkin or anyone else associated with the original Q.jl?

[ericphanson]

I don't think Q.jl is registered; I don't see it here: https://github.com/JuliaRegistries/General/tree/master/Q

Therefore I don't think the name Q.jl is taken in General. However both Q.jl and Q2.jl seem very short and non-descriptive to me. I guess since I didn't know there was a programming language called Q. What about QLang.jl or something like that?

[goerz]

Good catch! Yeah, if Q isn’t currently registered, I would definitely push for a longer name.

[p-casgrain]

@p-casgrain Did you at any point try to reach out to @abalkin or anyone else associated with the original Q.jl?

I haven't, though I can do it if you think it's worth it.

[p-casgrain]

Good catch! Yeah, if Q isn’t currently registered, I would definitely push for a longer name.

Ok, I'll think of something.

What's the procedure if I change the name? I rename the repo and resubmit the request for registration?

[gdalle]

What's the procedure if I change the name? I rename the repo and resubmit the request for registration?

Exactly, and the present PR will be blocked anyway because of our comments (but someone will probably close it manually).

[p-casgrain]

I have two suggestions here in order of preference

• JuliaKdb.jl
• QConnect.jl

Are there any objections to either?

[Azzaare]

Jumping in with my 2-cents ...

I believe that you should avoid having julia in the name, as it is already implied to be a julia thing by the .jl extension. The second name is more likely to fit the current usage.

Side note, what name would be the easier to understand for the users? If there are more related packages, can they share a common subname? (such as QConnect, QLang, QParse, etc.)

[goerz]

Closing in favor of #118193