Jupyter Day NYC 2015

Jupyter Incubator: What's Cooking?

Peter Parente (@parente), Developer in IBM Cloud Emerging Technology

Greetings!

I'm a member of the IBM Cloud Emerging Technology team
We innovate, incubate, and integrate disruptive tech
We've been IPythonites / Jovyans for ~3 years
We've recently become more active in the community

Rundown

Jupyter Subprojects
Some projects in incubation
Collaboration opportunities

First off, a clarification

There are two ways that new Subprojects are created:

Direct Subproject creation.

Incorporation of an existing external Subproject.

New Subproject Process, Jupyter Governance

Every new Jupyter Subproject does not have to go through the incubator!

When to incubate

Significant unanswered technical questions or uncertainties that require exploration.

Entirely new directions, scopes or ideas that haven't been vetted with the community.

Significant, already existing code bases where it is not clear how the Subproject will integrate with the rest of Jupyter.

Incubation of Subprojects, Jupyter Governance

Another clarification

If a Subproject team knows from the start that it would eventually like its Subproject to be part of the official Jupyter organization, it can be incubated in the jupyter-incubator organization.

Incubation in the jupyter-incubator organization, Jupyter Governance

You are not required to incubate in github.com/jupyter-incubator!

tl;dr

Project in scope + proposer on Council + Council agrees
→ create new github.com/jupyter repo

Project mature in open source + want to move to github.com/jupyter
→ proposal for incorporation

Project is immature + want association with Jupyter
→ proposal for incubation under github.com/jupyter-incubator

Project under incubation matures
→ proposal for incorporation

Enough! What's cooking?

Dashboards

Goal: ease transition from notebook to just-good-enough apps
Features: arrange output areas, capture layout, deploy apps
Recent focus: tutorials, demos, defects since open sourcing
Long term: maturation of deployment (jupyter-js-services, kernel gateway, tmpnb / binder)

Declarative Widgets

Goal: ease creation of interactive areas by exploiting web components ecosystem
Features: use declarative syntax, write simple templates / bindings, install 3rd party widgets
Recent focus: set / watch data from kernel, import progress, error logging
Long term: more languages, better dev experience, identification of core modules

Kernel Gateway

Goal: Headless HTTP/Websocket access to kernels
Features: /api/kernels, /api/kernelspecs, token auth
Recent focus: Python reference implementation, hack notebook to launch remote kernels
Long term: use by dashboards, Thebe, Notebook, new kernel consumers, cloud kernel providers

Kernel Gateway

Anything strike your fancy?

Collaboration topics

Dashboard, widget, kernel use cases
Secure, scalable dashboard deployment
Higher-order widgets (wizards?)
Declarative widget underpinnings for other langs (Julia, R?)
Alternative kernel gateway implementations (Go)
"Deeper" kernel gateway APIs (notebook functions as REST?)
"Very remote" kernel support from Notebooks
Porting of incubation concepts to PhosphorJS

Let's chat!

Today or virtually on GitHub / gitter (@jtyberg, @lbustelo, @parente, @vinomaster)

Jupyter Incubator: What's Cooking?

Greetings!

Rundown

First off, a clarification

When to incubate

Another clarification

tl;dr

Enough! What's cooking?

Menu

Dashboards

Declarative Widgets

Kernel Gateway

Kernel Gateway

Anything strike your fancy?

Collaboration topics

Let's chat!