IMO rabbitmq_osiris would've been a better name, and you can use module(..., repo_name="com_github_rabbitmq_osiris") if you need to keep the old name around. We generally don't do the reverse domain name thing in BCR.

IMO rabbitmq_osiris would've been a better name

That's good to know. Since the BCR is flat, we wanted to be respectful and not just grab "osiris" as a top level name. Osiris is from the rabbitmq github org, but is meant for use outside of rabbitmq/rabbitmq as well. I'm about to add another project of ours called ra. Maybe an appropriate name would be "ra-erlang"?

@Wyverald I used rabbitmq_ra for https://github.com/rabbitmq/ra in #846

Should we consider renaming this module to rabbitmq_osiris? Or leave it as it is?

Osiris is from the rabbitmq github org, but is meant for use outside of rabbitmq/rabbitmq as well. I'm about to add another project of ours called ra. Maybe an appropriate name would be "ra-erlang"?

I think calling it rabbitmq_ra (like you did) is perfectly reasonable; it doesn't mean it needs to be used by rabbitmq only, just that it's under the rabbitmq org (similar to google_benchmark not being used for google only, for example).

Regarding renaming, I think we could actually get away with renaming it since it was submitted 2 days ago and unlikely to have seen a lot of usage yet. Happy to force-approve the PR if you send it, but ultimately I'll leave it up to you, since you're likely the only user of that module right now :)

Yes, probably we are the only user, I will first open a PR with the new name, then a second PR to remove the old entry once our references have been updated