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

#Proposal migration to jupyterlab-contrib organization #11

Open
fcollonval opened this issue Jan 10, 2021 · 6 comments
Open

#Proposal migration to jupyterlab-contrib organization #11

fcollonval opened this issue Jan 10, 2021 · 6 comments

Comments

@fcollonval
Copy link
Contributor

Hey @shreddd

I created a new organization jupyterlab-contrib to gather extensions highly used by the community to increase their visibility and to attract attention on volunteers to help maintain them. Some extensions have already been transferred like jupyter-archive or jupyterlab-kernelspy.

As you were in the past interested to transfer this extension to the community, I wonder if you would be interested in transferring it to that organization?

The new organization is mirroring the jupyter_contrib_nbextensions repository. In particular it is not endorsed officially by the Jupyter board/developpers.

@shreddd
Copy link
Contributor

shreddd commented Jan 28, 2021

Hi @fcollonval

Yes - we would be interested in transferring ownership to the community.

In a past meeting with the JupyterLab core team we had also discussed merging with the core set of Jupyter extensions as well, since this feature (along with https://github.com/NERSC/jupyterlab-favorites) would be of general use to all Jupyter users.

@fcollonval
Copy link
Contributor Author

Thanks for reaching out @shreddd

Indeed there has been discussions on that front. But the latest discussion in jupyterlab/frontends-team-compass#52 points to rather keep the extensions outside of the core. This is the reason I started the jupyterlab-contrib organization especially to help extension authors that do not have the bandwidth to update to JLab 3.

Let me know if you want more information or if you would like to start a broader discussion with some core developers.

@shreddd
Copy link
Contributor

shreddd commented Jan 28, 2021

OK - yes - I think we are supportive of moving this to jupyterlab-contrib. Let us know how we can proceed.

@fcollonval
Copy link
Contributor Author

Hey @shreddd sorry for the late answer.

If you okay, could you please open an issue there?

I need the GitHub and npmjs username of somebody with owner rights on this repo and package.

@krassowski
Copy link

Hi @shreddd I would be interested to contribute to maintenance after moving to jupyterlab-contrib, are you still interested?

@fcollonval
Copy link
Contributor Author

@krassowski FYI I forked the projet to jupyterlab-contrib https://github.com/jupyterlab-contrib/jupyterlab-recents/ and I'm owner on the PyPI and conda packages. Let me know if you want to be added as maintainer on the fork

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