3 ms·
I'm excited for this award, it's certainly well deserved. In my heart, I wish the "data community" would show more care for security (and, related, privacy), w
by ecesena 9y ago
I'm excited for this award, it's certainly well deserved.
In my heart, I wish the "data community" would show more care for security (and, related, privacy), with deeper focus on features that simplify access control, and guidelines on how to enforce "reasonable defaults".
I fear that Jupyter in many companies is becoming the next Jenkins, with unconstrained access to all data vs all infra, and this will lead to more and more incidents and leaks.
I very much hope that recognitions like this one will foster not only better tools and support, but also best practice and security considerations.
But, back to the focus of the post, congrats on this success!
- mistrial9 9y agoa CTO said recently .. we think of the base community edition as the place where we enable people to do things, and the corporate enterprise edition as where we prevent people from doing things. All the hardened security goes into the Enterprise Edition, for which they can pay.
- carreau 9y agoThanks for your comment. One of the next focus area, where we are looking for funding and help, is making sure the right restrictions and permissions are in place. We probably will put that in the context of GDPR/HIPPA/FERPA and follow these guidelines to make Jupyter "Ready" for these framework. We can't say that Jupyter it itself compliant, as you need to see in which context it is deployed, but we want to make it as easy as possible for a team of researcher with low budget, or a companies with 1000+ user to make it easy to deploy a secure, auditable and safe Jupyter environement.