Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BYOC2J: Bring Your Own Code (to Jupyter) #7

Open
bollwyvl opened this issue Jul 25, 2016 · 1 comment
Open

BYOC2J: Bring Your Own Code (to Jupyter) #7

bollwyvl opened this issue Jul 25, 2016 · 1 comment

Comments

@bollwyvl
Copy link
Member

Based on feedback from a number of folks, it looks like there is desire for workshop track dedicated to developers who want to bring their ideas to life as Jupyter extensions.


Me

Nick Bollweg


Abstract

The Jupyter stack is built from the ground up to be extensible and hackable, but Jupyter is a big planet with many moons. Let's learn about and build tools and approaches for getting started, testing, and distribution of Jupyter extensions. After a run-down of the extension points (sanctioned and otherwise) within the existing architecture, we'll want to hear about existing extensions to the notebook server, the current notebook JS application, nbviewer, and JupyterHub... and start looking at next-generation tools like JupyterLab.


Affiliation

Project Jupyter

About Me

Nick Bollweg is a Software Developer at Continuum Analytics, working on open source tools and products in Python and Javascript for making Jupyter more adoptable by end users and organizations. Based out of Atlanta, he pitches in on PyData Atlanta

@tonyfast
Copy link
Member

tonyfast commented Aug 3, 2016

Ok, @bollwyvl you're on the hook for co-running this with @blink1073 to make this thing good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants