-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Call for interest: migrate Cal Poly comment extension to JupyterLab core #12032
Comments
ellisonbg
added
enhancement
status:Needs Triage
Applied to new issues that need triage
labels
Feb 9, 2022
Opps, if you are interested in working on this, please leave your GitHub username as a comment on this issue. |
#9885 was closed in deference to this, but I just want to call out that there is some interesting discussion there about implementation details, such as interaction with the RTC system. |
This was referenced May 10, 2022
Mentioned in #12032 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
The Cal Poly Jupyter interns have created a JupyterLab extension for commenting on notebooks and text files. This integrates with the new Yjs data models. There is strong interest from the Jupyter user community to have commenting capabilities and we are evaluating if we should begin work to migrate the existing commenting extension into core. Here is the link to the existing repo:
https://github.com/jupytercalpoly/jupyterlab-comments
There would be a significant amount of work required to bring this extension over to core and get it ready for users. The purpose of this issue is as a call for interest to see who would be interested in working on this. Once we get critical mass, we can begin to discuss the next steps.
Proposed Solution
Create an informal working group of people who would like to help improve and potentially merge https://github.com/jupytercalpoly/jupyterlab-comments into JupyterLab core.
Additional context
There is an existing commenting extension in the JupyterLab GitHub org that is older, probably less capable and hasn't been maintained for a while. We would need to figure out what to do with this code base along the way.
The text was updated successfully, but these errors were encountered: