Skip to content
This repository has been archived by the owner on Feb 21, 2024. It is now read-only.

Move issues from the RetroLab repo to the Notebook repo #9

Closed
jtpio opened this issue Mar 10, 2022 · 3 comments
Closed

Move issues from the RetroLab repo to the Notebook repo #9

jtpio opened this issue Mar 10, 2022 · 3 comments

Comments

@jtpio
Copy link
Member

jtpio commented Mar 10, 2022

Opening the issue here to discuss the strategy we would like to follow to move the issues from https://github.com/jupyterlab/retrolab to https://github.com/jupyter/notebook, now that the main branch is targeting Notebook v7.

At the Jupyter triage meeting today @krassowski suggested we could temporarily move the retrolab repo to the jupyter organization on GitHub for maybe 30 minutes. Since the two repos would be under the same org we could use the "Tranfer Issue" feature from the GitHub UI directly.

When issues have been moved, we move the retrolab repo back to the jupyterlab organization.

This would avoid having lots of issues open by Meeseeks, and we keep the original authors.

What do you think?

@damianavila
Copy link
Member

+1 on the simplest approach and what you describe (temporary migration) seems totally reasonable to me if we can avoid the non-useful noise.

@jtpio
Copy link
Member Author

jtpio commented Apr 27, 2022

Starting the transfer now.

Will move the repo back to the jupyterlab organization once finished.

@jtpio
Copy link
Member Author

jtpio commented Apr 27, 2022

Closing as all the relevant issues have now been transferred and added to the 7.0 milestone: https://github.com/jupyter/notebook/milestone/45

The RetroLab repo has been transferred back to the jupyterlab organization: https://github.com/jupyterlab/retrolab

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

No branches or pull requests

2 participants