Matthias and Team: On Tuesday, June 6, 2017 at 5:04:29 PM UTC-7, Matthias Bussonnier wrote: > > On Tue, Jun 6, 2017 at 4:12 PM, Jean Bigboute <[email protected] > <javascript:>> wrote: > > Thank you for posting this and I hope you are successful. As an > occasional Jupyter user, I have struggled to understand its use for > collaborative work when so much depends on future developments and > additional infrastructure. In my work environment we can't deploy IT > services such as servers, containers etc. on our own. We don't always have > access to help sites either. It is hard to know when to push and when to > punt. I don't feel so alone any more. > > The usage for collaborative work should become easier soon. We had our > dev meeting last week, and a version that allow some[1] syncing via > google drive is almost ready (Ian did and does a fantastic job). You > will probably see that in JupyterLab in one of the next releases (at > least as an extension). ... >
Thanks for your prompt response. With due respect, I would like to point out that Google Drive doesn't solve the problem. In corporate environments where proprietary data and algorithms are at stake, it is highly unlikely that users will be allowed access to Google Drive, Github, NBViewer, StackOverflow, etc. That is certainly true with my employer so I can only post completely generic questions and then again from my own account. In the present IT security environment (which is only going to get more restrictive) any type of added service requires multiple levels of scrutiny and review all tied into business cases. Bypassing the system or attempting to do so will be detected quickly and the people responsible will get fired. Unless the product or service is incredibly compelling (see below) no one will go through the effort to get a product approved because the odds of success are practically zero. Additionally, I looked up JupyterLab just now and read that "JupyterLab computational environment. This is a very early preview, and is not suitable for general usage yet. " This has been the case for quite some time. > Finding the right balance between consumers of Jupyter that want to > deploy that on large number of nodes with hundreds of users – ... > [deletia] > > The documentation can definitively get improvement – and as you might > have seen in an earlier mail Jessica is starting to work with us on > that and we are thrilled – but we can't cover all the ground. We also > tend to assume more and more that people have internet to get help if > you have an interest if having our docs offline and we don't provide a > link please open an issue and we'll try to find time to make that > happen. If you have experience in deploying in a difficult environment > and have manage to go around some pain point, please let us know – or > even better make a PR against our documentation. We'd love to have a > clearer way of expressing the advantages drawback of each deployment > but so far didn't had the time to sit down and write these as things > are moving really fast even for us. > And this is the key point. I have been following IPython then Jupyter now Jupyter +Lab and +Hub since about 2014. The pace of developments is incredibly fast and I admire the team for doing so much. But, I think the mindset is very much from academia. I love academia, its ethos, and the exuberance but Jupyter is now fully promoting into other areas which have very different cultures and needs. Documentation, user testing, stability, self-containment,... these are all important and I don't think are being given sufficient consideration. There's a fascinating blogpost on making Jupyter Notebooks more reproducible: https://jakevdp.github.io/blog/2017/03/03/reproducible-data-analysis-in-jupyter/ The author uses Github as a repository and a standalone text editor among other tools to accomplish this. In one of the comments, he remarks "I agree that collaborating on notebooks is tough. I mostly avoid it, and instead collaborate on plain-text documents like markdown and code files." Then, he recommends the nbdime project as another workaround. I bring him into this discussion because I think he is incredibly smart, an advocate for the project, highly experienced with the tool, and yet still has to find ways to do things which, on the surface, are asserted as built in. Please excuse the frustration that is coming though. I think I am a well-wisher to the project but after nearly three years of observation, I suggest, again respectfully, that you won't always be reaching the elite. If Jupyter is to succeed, it will have to be used by rank-and-file slobs like myself in environments where we have pressures to produce. We aren't dumb but neither can we 't be diving into the gizzards of servers, source code, and containers. We need stuff to work so we can get on with our jobs. 'Real Soon Now' only goes so far. -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/ebc062a3-4ae1-4635-960a-4d9ce62ea605%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
