Roadmap

---

THIS PAGE IS CURRENTLY UNMAINTAINED

---

To all collaborators, 🎉 welcome to the nteract party! 🎉 @willwhitney has transferred ownership of hydrogen to the collective code constructors of nteract.

We've got a lot of packages within the nteract org that are being used to build a new version of the notebook. These same packages can and should be used by Hydrogen. In order to get there, we're going to want to make some targeted refactorings, namely:

• write tests and aim for stability
• switching to async by default where possible - [ ] use promises - [ ] use observables - [ ] use enchannel-zmq-backend for the kernel messaging
• pure javascript, no reliance on jupyter tooling - [ ] only protocols, formats, and paths - we want it to work by installing straight from Atom - [ ] rely on other npm packages within nteract (or elsewhere) to reduce code duplication and keep things as simple as possible - [x] use jmp for the kernel messaging - [x] use transformime - [ ] use kernelspecs

Please, update this wiki page if you intend to work on any of the above items.

Some Ideas

• Add a console to make execution request to the running kernel.
• Add the ability to define code cells similar to the jupyter notebook.

Will's branches

There are three branches with Will's work to add some features to Hydrogen:

• jmp (already implemented)
• rich-completions (See also https://github.com/jupyter/jupyter_client/issues/51 )
• plugin-api