Hmmm. I guess Channel is doing more than just websockets, but I've always thought it had good docs... Anyhow...
We'll see how the Async work goes, but a lot of channel will end up being absorbed into Django itself. What, at this point, I guess that will leave is "just" the websocket bit. (Maybe the Channel Layers bit... too but maybe that would/could be separate.) Hopefully this'll make it more focused and easier to follow
But... I think websockets haven't turned out to be the One True Hammer people thought. (They're not that popular actually, it seems...) So I'm not sure we'd include support in core (vs keeping it in the third-party package.)
I guess something to revisit after 3.0.