That approval was by the previous modularity working group.
A new approval seems to be required by FESCo https://pagure.io/fesco/issue/2761.

How do I understand "or bundled appropriately"?

It means the package's files (programs, libraries, manuals) are not in standard lookup paths, so they cannot be used accidentally by a third-party.

Flatpacks or software collections is an example of bundling. They install "bundled" files into a private directory.

Thanks for the explnation. It isn't obvious from the policy itself, but I cannot think of better wording.

:thumbsup:

Perhaps instead of "bundled appropriately" what we really mean is "not visible to the package manager as an installable package"?

I think the policy should make it clear that if the default stream offers a package, it's part of the API. If they want to avoid that, they must not ship that package (through whatever appropriate means).

In that case the "or bundled appropriately" clause is completely irrelevant and I'd rather remove it.

Another point which baffles me is the SHOULD modal verb. It sounds like you would expect a common class of exceptions. If this should be strict rule, then we should use MUST.

This pull request was approved https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/LI2SXFF2UQVCR2YOLFXF46QOCKZKAPZB/. I will merge it. We can tune the wording later.