Peter Parente (@parente), Developer in IBM Cloud Emerging Technology
Peter Parente (@parente), Developer in IBM Cloud Emerging Technology
There are two ways that new Subprojects are created:
- Direct Subproject creation.
- Incorporation of an existing external Subproject.
Every new Jupyter Subproject does not have to go through the incubator!
- 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.
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.
You are not required to incubate in github.com/jupyter-incubator!
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
And, of course, there are many other awesome new projects outside jupyter-incubator (e.g., binder, bqplot)
Today or virtually on GitHub / gitter (@jtyberg, @lbustelo, @parente, @vinomaster)