Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we make nbresuse an official jupyter project? #62

Closed
lresende opened this issue Aug 1, 2020 · 3 comments
Closed

Should we make nbresuse an official jupyter project? #62

lresende opened this issue Aug 1, 2020 · 3 comments

Comments

@lresende
Copy link
Member

lresende commented Aug 1, 2020

We are seeing good adoption of nbresuse, should we move this to Jupyter org?

@jtpio
Copy link
Member

jtpio commented Aug 31, 2020

Thanks @lresende for opening this.

This sounds like a good idea and is also what the discussion in #58 is heading towards.

We could then group all the frontend extensions in one place to make it easier for users to discover and install.

@jtpio
Copy link
Member

jtpio commented Nov 19, 2020

We discussed this during the Jupyter Server meeting today: jupyter-server/team-compass#1 (comment)

The consensus was that the jupyter-server would be a good home for this project. Moving it there would also help with the long-term goal of baking metrics in the server and “closer” to kernels.

@yuvipanda is it ok for you to move the repo to the jupyter-server GitHub organization?

cc @ajbozarth @Zsailer @kevin-bates @mlucool

@yuvipanda
Copy link
Collaborator

yuvipanda commented Nov 24, 2020

YESSS!

Let's continue this conversation in jupyter-server/team-compass#3

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

No branches or pull requests

3 participants