Split docs to kernel-mgmt

[kevin-bates]

This pull request moves the kernel provider-specific material to jupyter-kernel-mgmt.

[codecov-io]

Codecov Report

Merging #4 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #4   +/-   ##
=======================================
  Coverage   72.27%   72.27%           
=======================================
  Files          17       17           
  Lines        1277     1277           
=======================================
  Hits          923      923           
  Misses        354      354

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5881efb...6987932. Read the comment docs.

[kevin-bates]

This PR should be considered preliminary since it establishes the initial presence on readthedocs.io. It also cross-references with jupyter_kernel_mgmt and takluyver/jupyter_kernel_mgmt#26.

[takluyver]

I'm somewhat uncomfortable about splitting docs up still more - I think it's quite hostile to people trying to get to grips with Jupyter that documentation is in so many little separate pieces. But both JKM and jupyter_protocol are meant to be public API packages which should be documented, and that's easiest to do with the docs in their respective repos. And if jupyter_protocol becomes the main Python implementation of the message spec, it probably makes sense for the protocol description to live along with it.

So I think merging this and the corresponding JKM pull request is the way forwards. But I want to mention this reservation first, in case anyone can see a better way we could try to organise documentation.

[kevin-bates]

I agree with your concern. We will also have two "authoritative description[s] of the Jupyter messaging protocol". 😞 So, like many things between the notebook and juptyer_server repos, we'll need to keep things in-sync between juptyer_client and jupyter_protocol/jupyter_kernel_mgmt. jupyter/jupyter_client#486 is a great example, for instance.

[takluyver]

Thanks. We don't seem to have had any brainwaves for great alternatives, though. So let's move forwards with this.