Transferring jupyter ydoc (and pycrdt?)

jupyterlab / frontends-team-compass

A repository for team interaction, syncing, and handling meeting notes across the JupyterLab ecosystem.

https://jupyterlab-team-compass.readthedocs.io/en/latest/

BSD 3-Clause "New" or "Revised" License

59 stars 30 forks source link

Transferring jupyter ydoc (and pycrdt?) #257

Open fcollonval opened 3 months ago

fcollonval commented 3 months ago

Problem

Collaboration features are provided by the extension https://github.com/jupyterlab/jupyter-collaboration But some key components (ydoc, pycrdt and pycrdt websocket) are not in Jupyterlab org but in jupyter server. This results in maintainers rights discrepancies between repo and increase rights management fatigue.

What do you think about moving all collaboration related in the same org? Which one would be best; jupyterlab or jupyter-server?

Proposed Solution

Additional context

echarles commented 3 months ago

fyi we had done some work in https://github.com/jupyter-rtc (which could be renamed to https://github.com/jupyter-collaboration). Having such a common org for both client and server side code would remove those difficulties).

davidbrochart commented 2 weeks ago

It's true that we need to reduce maintenance pain, but we also need to put the repositories in the right place. If we don't create a new https://github.com/jupyter-collaboration organization, we could:

leave pycrdt, pycrdt-websocket and jupyter_ydoc in jupyter-server, and move jupyter_server_ydoc in there.
leave jupyter-collaboration-ui, jupyter-docprovider and jupyter-collaboration in jupyterlab.

So basically just move jupyter_server_ydoc in https://github.com/jupyter-server, which shouldn't live in https://github.com/jupyterlab (see https://github.com/jupyterlab/jupyter-collaboration/issues/391#issuecomment-2446316936).

jtpio commented 2 weeks ago

For reference there are some points for not creating additional GitHub organizations: https://github.com/jupyter-governance/ec-team-compass/issues/12