can i ask why we should found yet another independent package repository, especially when the proposed API doesn‘t introduce any build dependencies?
“package-level” API is not really something that is meaningful in swift today, and concerns about module-level bloat are better addressed by spinning off the additional API into separate modules and library products.
the most commonly-used documentation tool today, DocC, has no support whatsoever for multi-target documentation, much less multi-package documentation. today we are able to navigate laterally across DocC modules in the same package on the swift package index thanks to the heroics of @daveverwer and @finestructure , but these bridges do not cross package boundaries, and i feel like fragmenting the server libraries further will make an already hard-to-navigate constellation of libraries even more difficult to use.