Skip to content

Conversation

@JuliaRegistrator
Copy link
Contributor

UUID: d122d8d1-e425-46db-8770-26312790ade9
Repo: https://github.com/BGN-for-ASNA/BayesianInference.jl.git
Tree: 827e8bcdb5913d601bb93cb8e397c02d0df9048c

Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
@gdalle
Copy link
Contributor

gdalle commented Dec 12, 2025

Hi, congrats on the package! I would strongly recommend a less generic name, especially for a package that looks rather modest in scale (which means it cannot claim to represent all of Bayesian inference)

@gdalle
Copy link
Contributor

gdalle commented Dec 12, 2025

Also, if I'm not mistaken there is a lot of type piracy

@github-actions
Copy link
Contributor

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.

@JuliaTagBot JuliaTagBot added the AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. label Dec 12, 2025
@SebastianSosa
Copy link

Hi, congrats on the package! I would strongly recommend a less generic name, especially for a package that looks rather modest in scale (which means it cannot claim to represent all of Bayesian inference)

Unfortunately, the name cannot be changed. It must remain consistent across the Python and R versions, and it is also the name used in the submitted paper.

@SebastianSosa
Copy link

Also, if I'm not mistaken there is a lot of type piracy

Indeed there is. The sole purpose of this is to enable basic, direct mathematical operations on JAX arrays, thereby preventing Julia users from having to convert those arrays manually.

@SebastianSosa
Copy link

Hi, congrats on the package! I would strongly recommend a less generic name, especially for a package that looks rather modest in scale (which means it cannot claim to represent all of Bayesian inference)

What about changing the package name to BIJ? Would that be acceptable, or is the name too uninformative?

@goerz
Copy link
Member

goerz commented Dec 13, 2025

it is also the name used in the submitted paper.

As a general rule, that is not something we can take into account for registrations, unfortunately. Always register a package before publishing about it. I have no opinion on whether the current name is appropriate or not.

What about changing the package name to BIJ

Three-letter package names are no longer accepted for new packages, so that is not an option.

Also, if I'm not mistaken there is a lot of type piracy

Indeed there is.

I would be extremely skeptical of registering any package that commits type piracy. There may be exceptional circumstances where this could be okay, but IMO it would have to have substantial community consensus that that is indeed the best / only way to solve a particular problem, and that the potential issues associated with type piracy (invalidations, correctness issues) have been mitigated

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

Labels

AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. new package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants