I don't think I've been strongly pushed in either direction of either adopting a standard or keeping the status quo.
In specific regards to namespace / prefixes for types:
What we've talked about thus far are hypothetical futures, and I believe that it could remain that way, at least for SSWG pitch/proposal packages, is that we're stringent in our feedback and discussion threads to guard against these types of names without them being namespaced such as Redis.foo.
This'll probably be highly important for say, the NIODNS especially as the SwiftNIO team has expressed interest in ingesting it into the base layer of our stacks.
But for something like Postgres and Redis, we've done a well enough job of our types being <Database Name>* or NIO<Database Name>*.
Ultimately, the only inclination I'm having is "we keep a close eye on it, and revisit as needed" - but anything further might be premature optimization.