transfer classic jupyter/notebook to the jupyterlab organization

[tonyfast]

as we manage the transition to notebook 7, we'll need to move issues between the repos. projects need to be in the same organization to transfer issues between projects. would it be possible to move classic to jupyterlab organization to prepare for notebook 7.0? are there any major downfalls of this choice?

there are some drafts issues on the sunrise project board that will be hampered by the separate organizations, and recently this became a concern when merging retrolab issues in notebook classic jupyter/notebook#6225 (comment) .

cc: @Zsailer @jtpio

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[jtpio]

Should this be closed now that the general consensus seems to be moving the retrolab code base to the existing jupyter/notebook repo? #133 (comment)

[vidartf]

Closing proactively (aka please have a low threshold for reopening if this is still needed/useful). 😃