Case for a "Notebook Subproject" Github organization

[Zsailer]

I'd like to make a case for a separate "Notebook" Github org.

I know we discussed that we'd rather aim to consolidate things (in today's notebook meeting), but because there is a unique governing body that will manage this subproject and a specific set of projects under these team's management (see the list below), I believe there is a decent case for a separate org.

Further, I don't think it's the responsibility of the JupyterLab team to maintain nbclassic and the (new) notebook_shim package; rather it's the responsibility of the notebook team.

Here is a list of repos we would immediately move to this new org:

• jupyterlab/nbclassic
• jupyterlab/notebook_shim
• jupyter/notebook
• jupyter/notebook-team-compass

Pinging @tonyfast @afshin @jtpio.

[damianavila]

I would be supportive of the creation of that organization.

[jtpio]

While it would make sense in theory, one of the main "requirements" for the Notebook v7 transition is to keep the jupyter/notebook name for the repo, just because it's been the home for Notebook for so many years.

Maybe we should consider moving to a separate organization after Notebook v7 has landed, maybe for Notebook v8?

[afshin]

I think it is very important to keep jupyter/notebook as the home of the codebase a user is installing when they run pip install notebook. This does not prevent us, however, from having that repo redirect to a new one. I would propose waiting until after the the dust settles from the Jupyter Notebook v7 launch and the activity that will undoubtedly generate.

[jtpio]

Closing as the JupyterLab and Notebook subprojects have now been merged into a single subproject: jupyter/governance#200

jupyterlab/frontends-team-compass#230 is currently still opened to handle the follow-up items such as merge the list of council members and eventually archiving this repo.

Thanks!