Brainstorming permanent name for the 'QA' universe

[shikokuchuo]

We've become used to describing things in terms of the QA and production universes, whereas it has been pointed out that 'QA' as a moniker is far from obvious.

We've solved this on the technical side by using 'multiverse' as the universe for everything.

Should we just start calling it multiverse and production (repo), or does anyone have a better idea?

[shikokuchuo]

The naming scheme I proposed above might get confusing if ultimately we want the production repo to the default repository for users i.e. potentially link the TLD to 'production'.

I've always called it the 'community' repo and I still like that name (and its connotations). Community and Production?

[wlandau]

In that case, I would prefer to fully spell out "community". I have been using QA / PRD because those are terms used a lot in industry, "CMTY" is less standard and not as obvious an abbreviation. But yes, I agree it will be good to use "community" and "production" going forward.

[shikokuchuo]

How do you feel about 'unrestricted' as a more literal name?

CMTY is a fairly common abbreviation for community so even if we don't use it others will.

[wlandau]

How do you feel about 'unrestricted' as a more literal name?

That's a good one. I would be fine with that, maybe even "restricted" instead of "production" as well.

[shikokuchuo]

Community and Production has a nice balance to it. If 'unrestricted', then I think we'd have to adopt 'restricted'.
From continued use over the past week or so I'm still in favour of Community and Production.

[wlandau]

Community/production sounds good to me.

[llrs]

One repo is for releases that pass R CMD check, the other is for all the additional checks added on top of it. So my suggestion would be for:

• immediate.r-multiverse.org: The QA repo
• tested.r-multiverse.org: The production repo

imho everything and all can be confusing to which is which, while immediate and tested might be a bit confusing regarding that those at QA pass some checks it is not at the level of tested.

[shikokuchuo]

Thanks. We've been through similar suggestions and we're in favour of more 'obvious' names. We're in a sense too familiar with the problem. To a user, if they see the above 2 options, they would have to look up the definition of each one to figure out which it is that they need.

[llrs]

Yes, but that would only be needed once. But if this is not enough you might be interested in the devel and release branch names from Bioconductor it is easy to know which is which. I think this is easy and general enough that do not need more explanations for end users.
Or devel and production to avoid confusing a package release that doesn't end up in the release/production repository.

[shikokuchuo]

Devel would be confusing as R-Multiverse is not a development platform - that repository will still consist of releases made by package maintainers.

[wlandau]

I think we aligned on "community" and "production". The respective names are instantiated.