-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
“What should I work on?” – JupyterLab 4.0 feature-pairing meeting #124
Comments
Please add your availability here! |
This issue has been mentioned on Jupyter Community Forum. There might be relevant details there: https://discourse.jupyter.org/t/i-want-to-work-on-jupyterlab-4-0-what-should-i-work-on/8871/1 |
At the JupyterLab weekly meeting yesterday, we decided to postpone this call to next week: #117 (comment) |
I think it's time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After discussing the feature ideas for JupyterLab 4.0, we have many issues that are compelling but do not have individual contributors who have been able to commit to working on them.
Let's have a call where people who are interested in working on JupyterLab 4.0 and have some cycles to spare can become acquainted with the outstanding items on the list and sign up to work on them.
The text was updated successfully, but these errors were encountered: