Hi Michael, I'm supportive of this (just as I've been in the past). We need to have network-uri added to the HP, which I don't think should be a problem as the API doesn't change with this split, assuming that the new maintainer agrees to follow the HP rules (e.g. don't add non-HP packages as dependencies, don't radical change the API without discussion.) I have a slight preference to use 2.6 as the network version number, as I'm saving 3.0 for something more juicy.
1. Create a new package, network-uri, version 2.5.0.0, which exposes no modules and has an upper bound `network < 2.6.
I'm sure there's something clever behind this empty package, but I don't quite understand it. How does this help. Note that depending on network-uri but not network will not let you use Network.URI in your code, as that module will be hidden.
2. Create a second release of network-uri, version 3.0.0.0, which provides the Network.URI module verbatim as provided by the network package today, and has a lower bound `network >= 3.0`.
(And < X+1, as the HP follows the PVP.)