3 ms·

Jupyter/IPython dev here. 1) We are always supper happy to see commercial offers that integrate Jupyter – I see the HQ of Kyso is in SF, feel free to come see t

Jupyter/IPython dev here. 1) We are always supper happy to see commercial offers that integrate Jupyter – I see the HQ of Kyso is in SF, feel free to come see the Berkeley team. We're also be happy to come by SF to discuss ! 2) RT collaboration is on its way on main Jupyter (via JupyterLab) the beta should be announced in a couple of weeks maybe before end of month. It will be using Google Drive (by default, but plug-able). Not only on notebooks, but all text documents – you can get it now if you install master. 3) I would also look at CoCalc (ex SageMathCloud) that already have real-time collaboration with full history.

williamstein 9y ago
As mentioned, we have had collaborative editing with full history for Jupyter notebooks since 2014 in https://cocalc.com https://cocalc.com, which is open source by the way. We've written and rewritten this functionality 3 times now, culminating most recently with a complete front and backend rewrite of Jupyter from scratch for CoCalc. See http://blog.sagemath.com/jupyter/2017/05/05/jupyter-rewrite-for-smc.html http://blog.sagemath.com/jupyter/2017/05/05/jupyter-rewrite-... for more details. We also still support collaborative editing using Classical Jupyter.
- j_s 9y ago
  Nice! How much of this made it back into Jupyter proper? I'm always interested in the "rubber meets the road" aspects of commercialized open source development. Your project looks perfect for helping people learn how to code.
  - williamstein 9y ago
    I'm in close communication with many Jupyter developers, got a lot of help and feedback from them, and I hope I influence their direction in some cases. We view CoCalc Jupyter as another Jupyter client in the Jupyter ecosystem (much like nteract, Google Collaboratory, etc.); the implementation framework of CoCalc Jupyter is React.js, so the main code sharing is with Nteract, rather than classical Jupyter. Regarding commercialized open source, Nteract is another Jupyter client who development is funded by a company (currently mainly Netflix).

williamstein 9y ago

As mentioned, we have had collaborative editing with full history for Jupyter notebooks since 2014 in https://cocalc.com https://cocalc.com, which is open source by the way. We've written and rewritten this functionality 3 times now, culminating most recently with a complete front and backend rewrite of Jupyter from scratch for CoCalc. See http://blog.sagemath.com/jupyter/2017/05/05/jupyter-rewrite-for-smc.html http://blog.sagemath.com/jupyter/2017/05/05/jupyter-rewrite-... for more details. We also still support collaborative editing using Classical Jupyter.

j_s 9y ago
Nice! How much of this made it back into Jupyter proper? I'm always interested in the "rubber meets the road" aspects of commercialized open source development. Your project looks perfect for helping people learn how to code.
- williamstein 9y ago
  I'm in close communication with many Jupyter developers, got a lot of help and feedback from them, and I hope I influence their direction in some cases. We view CoCalc Jupyter as another Jupyter client in the Jupyter ecosystem (much like nteract, Google Collaboratory, etc.); the implementation framework of CoCalc Jupyter is React.js, so the main code sharing is with Nteract, rather than classical Jupyter. Regarding commercialized open source, Nteract is another Jupyter client who development is funded by a company (currently mainly Netflix).