Some roadmapping

[rgbkrk]

Taking pieces from #6 and #7 to make an initial ROADMAP and messaging outline.

[kafonek]

Looks good to me @rgbkrk. Two places that I think need a touch more detail, although it may only come after we start iterating on code:

• From backend perspective, there should be one central Tauri process -> many Sidecars (which means in-memory Notebook and ZMQ connection management), just like one Jupyter server -> Kernels (only managing ZMQ connections) right? Are you constraining the phase 1 work to the Tauri app spawning Jupyter Kernels (ipykernel, deno, etc) as subprocesses?
• I'm writing kernel-sidecar to run in a tokio runtime, is that compatible with how you're rolling out the initial Tauri app?

[rgbkrk]

I'm writing kernel-sidecar to run in a tokio runtime, is that compatible with how you're rolling out the initial Tauri app?

tokio all the way -- happy to stay in that ecosystem alongside deno

From backend perspective, there should be one central Tauri process -> many Sidecars (which means in-memory Notebook and ZMQ connection management), just like one Jupyter server -> Kernels (only managing ZMQ connections) right? Are you constraining the phase 1 work to the Tauri app spawning Jupyter Kernels (ipykernel, deno, etc) as subprocesses?

Ok great, useful for me to know about. I just assumed based on https://github.com/kafonek/kernel-sidecar-rs/blob/main/src/main.rs that kernel sidecar was launching the subprocess. I can update the doc & diagram.