jupyterlab-contrib/jupyterlab-contrib.github.io

Management and website of JupyterLab Unofficial Extensions and Tools

jupyterlab-contrib.github.io's Issues

Transfert jupyter-chat

Target

• The code repository: https://github.com/QuantStack/jupyter-chat
• The npm package on npmjs.com (if available): none at the moment
• The python package on pypi.org (if available): none moment
• The conda-forge recipe on https://github.com/conda-forge (if available): none at the moment
• The documentation website (if available): none at the moment

Reason

This project provides:

• a front end package that can be used in a Jupyter extension to include a chat
• a Jupyterlab extension that provides a chat panel

The first idea of this project was to extract the chat part of https://github.com/jupyterlab/jupyter-ai, to make it usable in other extensions.
See jupyterlab/jupyter-ai#205 for more context.

Part of the code come from the jupyter-ai code base (already in Jupyterlab org), and jupyter-ai could make use of the front end package in a next future.

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested (partially)
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

Transfer jupyterlab-gitlab to jupyterlab-contrib organization

Target

A JupyterLab extension for browsing GitLab repositories (in read-only mode).

This extension is based on jupyterlab-github. All credit to the JupyterLab team, and especially Ian Rose, for the github extension!

• The code repository: https://gitlab.com/beenje/jupyterlab-gitlab
• The npm package on npmjs.com (if available): https://www.npmjs.com/package/jupyterlab-gitlab (not used anymore since 3.0.0)
• The python package on pypi.org (if available): https://pypi.org/project/jupyterlab-gitlab
• The conda-forge recipe on https://github.com/conda-forge (if available): not available
• The documentation website (if available): not available

Reason

I don't have much time to maintain this extension.
@krassowski mentioned I could transfer it here. I think it can give the extension more visibility and make it easier to find people wanting to help.
@mahendrapaipuri already proposed to help.

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

Transfer jupyterlab_spellchecker

Target

Transfer jupyterlab_spellchecker.

• The code repository: https://github.com/ijmbarr/jupyterlab_spellchecker
• The npm package on npmjs.com: https://www.npmjs.com/package/@ijmbarr/jupyterlab_spellchecker

Reason

I no longer have time to contribute to developement of this extension. See discussion in jupyterlab-contrib/spellchecker#42

Checklist

• [ x] You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

Transfer jupyterlab-night theme

Target

A JupyterLab dark theme that uses the same color palette as the Github dark theme

• The code repository: https://github.com/martinRenou/jupyterlab-night
• The npm package on npmjs.com (if available):https://www.npmjs.com/package/jupyterlab-night
• The python package on pypi.org (if available): https://pypi.org/project/jupyterlab-night
• The conda-forge recipe on https://github.com/conda-forge (if available): https://github.com/conda-forge/jupyterlab-night-feedstock
• The documentation website (if available): None

Reason

I'd like it to be community driven

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

Move `jupyterlab-topbar`

Target

• The code repository: https://github.com/jtpio/jupyterlab-topbar
• The npm package on npmjs.com (if available): https://www.npmjs.com/package/jupyterlab-topbar
• The python package on pypi.org (if available): https://pypi.org/project/jupyterlab-topbar/
• The conda-forge recipe on https://github.com/conda-forge (if available): https://github.com/conda-forge/jupyterlab-topbar-feedstock
• The documentation website (if available):

Reason

• Better visibility
• jupyterlab-logout depends on it: #13

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

Transfer jupyterlab-link-share

Target

• The code repository: https://github.com/jtpio/jupyterlab-link-share
• The npm package on npmjs.com (if available): N/A - Since it's a simple extension for JupyterLab 3.0 and there isn't much too extend, it hasn't been published to npm. But it technically could be if needed.
• The python package on pypi.org (if available): https://pypi.org/project/jupyterlab-link-share/
• The conda-forge recipe on https://github.com/conda-forge (if available): https://github.com/conda-forge/jupyterlab-link-share-feedstock
• The documentation website (if available): https://github.com/jtpio/jupyterlab-link-share#jupyterlab-link-share

Reason

jupyterlab-link-share is a simple extension to quickly share the link to a running Jupyter Server instance.

The main reason to move it would be to increase its visibility, as some people might be interested in adding it by default to their Binder config, so multiple people could easily collaborate on the same instance.

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

Set up `jupyterlab-contrib-bot` for releases

Looks like this org already has a bot account: https://github.com/jupyterlab-contrib-bot

Maybe we could use it to make releases using the Jupyter Releaser v2 workflows?

This would help make releases for the projects under the jupyterlab-contrib GitHub organization.

Things to check:

• Push access on PyPI
• npm
• Admin access on the repos

cc @fcollonval who probably created this account

Create a GitHub App for releasing with the Jupyter Releaser

We should look into following this change in Jupyter Releaser to avoid using the ADMIN_GITHUB_TOKEN: jupyter-server/jupyter_releaser#557

This would mean creating an org wide GitHub app, and updating the releaser workflow and each repo to use the app.

Transfer `jupyterlab-spreadsheet-editor`

Target

jupyterlab-spreadsheet-editor enables editing CSV/TSV files using third-party Jspreadsheet editor; in future should also allow to edit MS spreadsheet etc; different from jupytercalpoly/jupyterlab-tabular-data-editor which tries to implement the spreedsheet editor itself using lumino grid; I did not have time to re-implement it from scratch so I went for well tested third-party solution (which is easier in maintenance IMO, but provides less integration with JupyterLab, e.g. the context menus are styled slightly differently).

• The code repository: https://github.com/krassowski/jupyterlab-spreadsheet-editor
• The npm package on npmjs.com (if available): https://www.npmjs.com/package/spreadsheet-editor
• The python package on pypi.org (if available): https://pypi.org/project/jupyterlab-spreadsheet-editor/
• The conda-forge recipe on https://github.com/conda-forge (if available): TBD
• The documentation website (if available): None

Reason

I want to encourage others to contribute to jupyterlab-spreadsheet-editor and make it possible for others in jupyterlab-contrib to make patch releases in case if I am away on holiday or something. I will continue developing the extension when I get chance to (i.e. the other kind of holidays).

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

jupyterlab-unfold

Target

• The code repository: https://github.com/martinRenou/jupyterlab-unfold
• The npm package on npmjs.com (if available): NA
• The python package on pypi.org (if available): https://pypi.org/project/jupyterlab-unfold/
• The conda-forge recipe on https://github.com/conda-forge (if available): NA
• The documentation website (if available): NA

Reason

https://github.com/martinRenou/jupyterlab-unfold/issues/21

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

Transfer of repo `oscar6echo/react-auth-google-example`

Target

Repo: https://github.com/oscar6echo/react-auth-google-example

This repo enables a JupyterLab user to authenticate with Google Identity services, and gives an example how to use it.
It is constructed by the jupyterlab/extension-examples react-widget.
Cf. its README.

Context

Described in this issue: jupyterlab/extension-examples#242

Help with maintenance of jupyterlab_spellchecker

• Which repository do you want to maintain:
  • All
  • https://github.com/jupyterlab-contrib/jupyterlab_spellchecker
• What do you want to do (multiple choices accepted):
  • Address reported issues and feature requests
  • Update a Archived repository to make it work on the latest JupyterLab version
  • Improve an extension (if so please describe, what you want to achieve)
    - fix BUGs
    - support more languages
    - integration with the language packages inside jupyterlab>3
• Which level of help, would you need (choose one of):
  • Total beginner but enthusiast (you are more than welcome and we will help in your learning of the Jupyter ecosystem)
  • Good reviews with tips would be appreciated
  • I am a experienced developer with Jupyter ecosystem

Transfer `jupyterlab-filesystem-access`

Target

jupyterlab-filesystem-access lets JupyterLab users browse local files using the (non-standard) Web Browser File System Access API: https://developer.mozilla.org/en-US/docs/Web/API/File_System_Access_API

• The code repository: https://github.com/jtpio/jupyterlab-filesystem-access/
• The npm package on npmjs.com (if available): https://www.npmjs.com/package/jupyterlab-filesystem-access
• The python package on pypi.org (if available): https://pypi.org/project/jupyterlab-filesystem-access/
• The conda-forge recipe on https://github.com/conda-forge (if available): N/A
• The documentation website (if available): N/A

Reason

Visibility, discoverability and shared maintenance.

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online (not yet: https://github.com/jtpio/jupyterlab-filesystem-access/issues/24)
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

Transfer kernelspy

Target

This extension adds a button in the notebook toolbar, which opens a window that lets you inspect all messages going to/from the kernel.

• The code repository: https://github.com/vidartf/jupyterlab-kernelspy
• The npm package on npmjs.com (if available): jupyterlab-kernelspy
• The python package on pypi.org (if available): jupyterlab-kernelspy
• The conda-forge recipe on https://github.com/conda-forge (if available): N/A
• The documentation website (if available): N/A

Reason

To increase the bus factor to more than 1.

Checklist

• You are owner of the repository you want to transfer
• Your role in the transferred repository will be (check one of):
  • Maintainer of all jupyterlab-contrib repositories
  • Maintainer of the transferred repository only
  • Either is fine (I'm not usre I understand the difference)
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

Note: Is there a requirement that everyone with commit rights have 2FA enabled?

List of extensions to migrate from classic notebook

This list is very useful to the folks using the classic notebook so they know whether the extensions they are using has an equivalent for JupyterLab: https://jupyterlab-contrib.github.io/migrate_from_classical.html

Which seems to have been populated from https://jupyter-contrib-nbextensions.readthedocs.io/en/latest/

Wondering whether we could extend that list to also include extensions such as RISE and nbgrader which are being developed in separate repos. So we have a central place where most of the nbextensions are listed. Even though their JupyterLab extension might not be developed within the jupyterlab-contrib org (but it probably could).

Happy to help with spellchecker maintenance

• Which repository do you want to maintain:
  • All
  • https://github.com/jupyterlab-contrib/jupyterlab_spellchecker
• What do you want to do (multiple choices accepted):
  • Address reported issues and feature requests
  • Update a Archived repository to make it work on the latest JupyterLab version
  • Improve an extension: language pack integration, improvements to spellchecker and custom word lists
• Which level of help, would you need (choose one of):
  • Total beginner but enthusiast (you are more than welcome and we will help in your learning of the Jupyter ecosystem)
  • Good reviews with tips would be appreciated
  • I am a experienced developer with Jupyter ecosystem

Transfer `lckr/jupyterlab-variableInspector` to `jupyterlab-contrib`

Target

Variable inspector extension for JupyterLab. Currently supports table view of active variables and a data grid viewer for matrix like objects for python kernels (some minor support for R and scala is also available).

• The code repository: https://github.com/lckr/jupyterlab-variableInspector
• The npm package on npmjs.com (if available): @lckr/jupyterlab_variableinspector
• The python package on pypi.org (if available): https://pypi.org/project/lckr-jupyterlab-variableinspector/
• The conda-forge recipe on https://github.com/conda-forge (if available): https://github.com/conda-forge/jupyterlab-variableinspector-feedstock

Reason

I'm happy to see that there is some interest in keeping this extension alive. Since I couldn't find the time to keep it updated in the past (and will not be able to do so in the near future) but would love to see it getting supported in the future as well I want to transfer the project to the jupyterlab-contrib org.

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

Transfer of jupyterlab-vim extension

Target

Vim keybindings for jupyterlab notebooks.

• The code repository: https://github.com/axelfahy/jupyterlab-vim
• The npm package on npmjs.com (if available): https://www.npmjs.com/package/@axlair/jupyterlab_vim
• The python package on pypi.org (if available): https://pypi.org/project/jupyterlab-vim/
• The conda-forge recipe on https://github.com/conda-forge (if available):
• The documentation website (if available):

Reason

To avoid having only one maintainer and losing compatibility with next jupyterlab version. I forked the original extension (https://github.com/jwkvam/jupyterlab-vim) because it was not up-to-date with jupyterlab versions and I want to avoid the same issue for others if @ianhi or myself stop updating it.

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

Transfer `jupyterlab-plugin-graph`

Target

• The code repository: https://github.com/jtpio/jupyterlab-plugin-graph
• The npm package on npmjs.com (if available): https://www.npmjs.com/package/jupyterlab-plugin-graph
• The python package on pypi.org (if available): https://pypi.org/project/jupyterlab-plugin-graph/
• The conda-forge recipe on https://github.com/conda-forge (if available): Not available yet, but can easily be packaged afterwards
• The documentation website (if available):

Reason

Follow-up to the move of other extensions, and to increase visibility.

The intended audience is more towards extension authors than regular end users though.

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

Add link checker in CI

Host a JupyterLab metapackage

Following the discussion at the JupyterLab dev meeting, @tonyfast proposed to maintain a JupyterLab metapackage in this organization.

This is a great idea, now the question is which extensions should we include?

To make thing as simple as possible, I propose that people add an unique comment with the extensions they would like to see. Using the first comment as example.

---

As a first guess, extension appearing in 50% of the comments will get included.

Request for transferring the jupyterlab-logout repository into jupyterlab-contrib

Target

A Logout Button for JupyterLab useful when used with JupyterHub!

• The code repository: https://github.com/jtpio/jupyterlab-logout

Reason

It is a useful extension for JupyterLab when you are working with JupyterHub. The Logout Menu button is deep in the menu structure ...

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

I put @jtpio into the issue, he is the owner of the repository!

Request to help support favorites and recents

• Which repository do you want to maintain:
  • jupyterlab-favorites, jupyterlab-recents
    • original maintainer for the repos before they were forked to jupyterlab-contrib
  • https://github.com/jupyterlab-contrib/jupyterlab-favorites
  • https://github.com/jupyterlab-contrib/jupyterlab-recents
• What do you want to do (multiple choices accepted):
  • Address reported issues and feature requests
  • Update an Archived repository to make it work on the latest JupyterLab version
  • Improve an extension (if so please describe, what you want to achieve)
    • We are actively using both repos at NERSC for users, and it is likely that new features will either be requested from our users and/or that we will want to better integrate with new features in lab, such as RTC.
• Which level of help, would you need (choose one of):
  • Total beginner but enthusiast (you are more than welcome and we will help in your learning of the Jupyter ecosystem)
  • Good reviews with tips would be appreciated
  • I am an experienced developer with Jupyter ecosystem
    • Reviews and tips are still appreciated when they happen

transfer DerThorsten/jupyterlab_pytutor/

Target

• The code repository: https://github.com/DerThorsten/jupyterlab_pytutor/

Reason

Give this repo better visibility and increase the change of usage

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

Move jupyter-videochat repo to this org

Target

• The code repository: https://github.com/yuvipanda/jupyter-videochat
• The npm package on npmjs.com (if available): https://www.npmjs.com/package/jupyterlab-videochat
• The python package on pypi.org (if available): https://pypi.org/project/jupyter-videochat
• The conda-forge recipe on https://github.com/conda-forge (if available): https://github.com/conda-forge/jupyter-videochat-feedstock
• The documentation website (if available):

Reason

jupyterlab-contrib/jupyter-videochat#34 has some discussion. @bollwyvl has been the primary maintainer for a while, and moving it to an org is the way to go to get more contributors. @bollwyvl should have rights on the repo.

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

DOC: add extensions in extensions.tpl

In extensions.tpl, I suggest adding itables, QgridNext, and ipyaggrid.

Transfer TOC with code cells working on JupyterLab 4.x

Target

• The code repository: https://github.com/Rmarieta/jupyterlab-code-toc
• The npm package on npmjs.com (if available): https://www.npmjs.com/package/jupyterlabcodetoc
• The python package on pypi.org (if available): https://pypi.org/project/jupyterlabcodetoc/

Reason

As mentioned in the issue #14975 that I opened a few weeks back, I eventually implemented the Table of Contents with the code cell content as a new independent extension and thought it could be helpful to other people to host the extension on here. I also moved to using a code editor with CodeMirror6 so maybe it will be better performance-wise on large notebooks. I was thinking we could also close the issue mentioned above and provide a link to this issue or the extension once it is hosted in this organization. Let me know if anything is not okay with the current extension.

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

jupyterlab-fileopen

Target

• The code repository: https://github.com/martinRenou/jupyterlab-fileopen
• The npm package on npmjs.com (if available): NA
• The python package on pypi.org (if available): https://pypi.org/project/jupyterlab-fileopen/
• The conda-forge recipe on https://github.com/conda-forge (if available): https://github.com/conda-forge/jupyterlab-fileopen-feedstock
• The documentation website (if available): NA

Reason

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

JupyterLab app cookiecutter

Target

A cookiecutter for bootstraping a JupyterLab based standalone application

• The code repository: https://github.com/jtpio/jupyterlab-app-cookiecutter
• The npm package on npmjs.com (if available): None
• The python package on pypi.org (if available): None
• The conda-forge recipe on https://github.com/conda-forge (if available): None
• The documentation website (if available): None yet

Reason

I believe it's a good candidate for the jupyterlab-contrib org as it will make it easier for people to make their own web app based on JupyterLab components

Checklist

- [ ] You are owner of the repository you want to transfer Not the owner but I believe @jtpio gave his blessing on this

• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

I cannot open a file jupyter notebook

Read the migration plan to Notebook 7 to learn about the new features and the actions to take if you are using extensions.

https://jupyter-notebook.readthedocs.io/en/latest/migrate_to_notebook7.html

Please note that updating to Notebook 7 might break some of your extensions.

[W 14:24:39.421 NotebookApp] Loading JupyterLab as a classic notebook (v6) extension.
[W 2024-02-01 14:24:39.424 LabApp] 'notebook_dir' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2024-02-01 14:24:39.424 LabApp] 'notebook_dir' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[I 2024-02-01 14:24:39.426 LabApp] JupyterLab extension loaded from C:\Users\a-a-h\anaconda3\Lib\site-packages\jupyterlab
[I 2024-02-01 14:24:39.426 LabApp] JupyterLab application directory is C:\Users\a-a-h\anaconda3\share\jupyter\lab
[I 14:24:40.509 NotebookApp] The port 8888 is already in use, trying another port.
[I 14:24:40.509 NotebookApp] The port 8889 is already in use, trying another port.
[I 14:24:40.509 NotebookApp] The port 8890 is already in use, trying another port.
[I 14:24:40.509 NotebookApp] Serving notebooks from local directory: C:\Users\a-a-h
[I 14:24:40.509 NotebookApp] Jupyter Notebook 6.5.4 is running at:
[I 14:24:40.509 NotebookApp] http://localhost:8891/?token=cdd88cd09be8458e3cbe901fb6e387e4a8d13760e8e9a1c8
[I 14:24:40.509 NotebookApp] or http://127.0.0.1:8891/?token=cdd88cd09be8458e3cbe901fb6e387e4a8d13760e8e9a1c8
[I 14:24:40.509 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[C 14:24:40.536 NotebookApp]

To access the notebook, open this file in a browser:
    file:///C:/Users/a-a-h/AppData/Roaming/jupyter/runtime/nbserver-1472-open.html
Or copy and paste one of these URLs:
    http://localhost:8891/?token=cdd88cd09be8458e3cbe901fb6e387e4a8d13760e8e9a1c8
 or http://127.0.0.1:8891/?token=cdd88cd09be8458e3cbe901fb6e387e4a8d13760e8e9a1c8

transfer ipylgbst

Target

running a lego boost robot via web-bluetooth in the browser

• The code repository:https://github.com/DerThorsten/ipylgbst
• The npm package on npmjs.com (if available):
• The python package on pypi.org (if available): https://pypi.org/project/ipylgbst/
• The conda-forge recipe on https://github.com/conda-forge (if available):
• The documentation website (if available):

Reason

better exposure, simplify releasing

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • [x ] I don't care
• [ x] The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • [ x] The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • [x ] How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• [x ] I certify the extension is not using exclusively paid-plan of any commercial service
• [x ] I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub

Activate/transfer jupyter-videochat RTD project

Target

Enable a ReadTheDocs build for jupyterlab-contrib/jupyter-videochat#39.

Reason

To get CI-built docs without a gh-pages deploy. I don't have GH perms to create webhook integration (but do have the URL, but don't know if that's sensitive.... probably not).

Checklist

• You are owner of the RTD project you want to transfer

Follow-on

This seems like a worthy thing to have an issue template for, with a better thought-out checklist 😊. I think treating it like a transfer where "i, the issue reporter, already have the RTD name" is better than posting an issue about creating the name... and then getting namesquatted.

Also the person signing up to be the "scribe" should be expected to bear the burden of anything harder than "click the activate webhook button" stuff: sending emails for feature flags, navigating the rtd.yml, etc.

Change the minimal compatible version of Jupyterlab

Should we update the minimal compatible version of Jupyterlab to 3.x in the issue checklist ?

Checklist

• ...
• The extension is working on at least JupyterLab 2.x
• ...

Transfer `jupyterlab-cell-flash`

Target

• The code repository: https://github.com/jtpio/jupyterlab-cell-flash
• The npm package on npmjs.com (if available): https://www.npmjs.com/package/jupyterlab-cell-flash
• The python package on pypi.org (if available): https://pypi.org/project/jupyterlab-cell-flash/
• The conda-forge recipe on https://github.com/conda-forge (if available): https://github.com/conda-forge/jupyterlab-cell-flash-feedstock
• The documentation website (if available):

Reason

Increase visibility of the extension.

Checklist

• You are owner of the repository you want to transfer
• Which role do you want to have in the jupyterlab-contrib organization (check one of):
  • Help with all jupyterlab-contrib repositories
  • Help with the transferred repository only
  • I don't have time anymore to keep helping the project
• The transferred repository (check one of):
  • Must keep the extension name
  • Cannot use the original name
  • I don't care
• The code is available under a Open Source license
• A license file is present in the code repository
• The extension is working on at least JupyterLab 2.x
• The repository contains a README file describing:
  • The provided feature(s)
  • A picture illustrating the feature(s)
  • The available options/settings (if applicable)
  • How to install the extension
  • optional a Binder link to test the feature online
• optional The frontend code (Typescript/Javascript) is tested
• optional The backend code (Python) is tested
• I certify the extension is not using exclusively paid-plan of any commercial service
• I will help the transfer process on the code repository AND the built packages

You must enable two-factor authentication on GitHub