Reviewing Zeppelin and Jupyter Notebooks

There&#x27;s also Iodide from Mozilla, which is pretty cool: <a href="https:&#x2F;&#x2F;alpha.iodide.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;alpha.iodide.io&#x2F;</a><p>GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;iodide-project&#x2F;iodide" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;iodide-project&#x2F;iodide</a><p>Post explaining what it is: <a href="https:&#x2F;&#x2F;hacks.mozilla.org&#x2F;2019&#x2F;03&#x2F;iodide-an-experimental-tool-for-scientific-communicatiodide-for-scientific-communication-exploration-on-the-web&#x2F;" rel="nofollow">https:&#x2F;&#x2F;hacks.mozilla.org&#x2F;2019&#x2F;03&#x2F;iodide-an-experimental-too...</a><p>It uses this markdown like file format: <a href="https:&#x2F;&#x2F;iodide-project.github.io&#x2F;docs&#x2F;jsmd&#x2F;" rel="nofollow">https:&#x2F;&#x2F;iodide-project.github.io&#x2F;docs&#x2F;jsmd&#x2F;</a>

There is also another tool called `pynb` (by the same author) that can be used to achieve human-readable format. The logic is a bit different there, since it generates a .py script file with markdown cells appearing as Python comments.<p>example diff: <a href="https:&#x2F;&#x2F;github.com&#x2F;minireference&#x2F;noBSLAnotebooks&#x2F;commit&#x2F;9005d37d06d9bdaca53806214b70ca81ea0a2007" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;minireference&#x2F;noBSLAnotebooks&#x2F;commit&#x2F;9005...</a><p>script: <a href="https:&#x2F;&#x2F;github.com&#x2F;minireference&#x2F;noBSLAnotebooks&#x2F;blob&#x2F;master&#x2F;util&#x2F;makepynb.sh" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;minireference&#x2F;noBSLAnotebooks&#x2F;blob&#x2F;master...</a><p>pre-commit hook: <a href="https:&#x2F;&#x2F;github.com&#x2F;minireference&#x2F;noBSLAnotebooks&#x2F;blob&#x2F;master&#x2F;util&#x2F;pre-commit-hook.sh" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;minireference&#x2F;noBSLAnotebooks&#x2F;blob&#x2F;master...</a>

Why wouldn&#x27;t you just use org-mode and ob-ipython which lets you call out to jupyter kernels and have the results appear in your org file?<p>At least then you&#x27;re dealing with diffs of plain text instead of json.

Emacs org mode definitely got this right. Storing everything as json feels like an ok choice, but there is a huge advantage to storing in the repo exactly what you review.

Converting notebooks to markdown is a fine idea (although you have to maintain both versions).<p>I built ReviewNB (<a href="https:&#x2F;&#x2F;www.reviewnb.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.reviewnb.com&#x2F;</a>) specifically to review Jupyter Notebooks on GitHub.

There&#x27;s also jupytext: <a href="https:&#x2F;&#x2F;github.com&#x2F;mwouts&#x2F;jupytext" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;mwouts&#x2F;jupytext</a>

This works on Github: <a href="https:&#x2F;&#x2F;www.reviewnb.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.reviewnb.com&#x2F;</a>

Github formats Jupyter notebooks but not Zepplin, which for me is pretty much a slam dunk for jupyter.