Context

I have been working a new Python bindings for Yrs, the Rust port of Yjs. In the Jupyter stack, we currently use Ypy. See this issue for the motivations behind pycrdt.
I already opened the following PRs that update our stack to pycrdt:

• Use pycrdt instead of y-py jupyter_ydoc#194
• Use pycrdt instead of y-py y-crdt/ypy-websocket#89

I already merged a PR to update Jupyverse to pycrdt:

• Replace Ypy with pycrdt jupyverse#359

But I didn't open the equivalent PR in jupyter-collaboration, mainly because there are pending PRs that may change the code quite a bit, and that would result in a lot of conflicts.
If we decide to use pycrdt instead of Ypy, we should move it to either the y-crdt organization or the jupyter-server organization. I would prefer the latter for now (it could go back to y-crdt in the future). That means the new version of ypy-websocket that uses pycrdt should also move to jupyter-server.
Are there any objections about moving pycrdt to jupyter-server, along with ypy-websocket?

Proposal

Let's move pycrdt to jupyter-server

Votes

This vote was initiated on 16 November 2023.

• @damianavila
  • yes
  • no
  • abstain
• @kevin-bates
  • yes
  • no
  • abstain
• @echarles
  • yes
  • no
  • abstain
• @SylvainCorlay
  • yes
  • no
  • abstain
• @afshin
  • yes
  • no
  • abstain
• @vidartf
  • yes
  • no
  • abstain
• @rahul26goyal
  • yes
  • no
  • abstain
• @ellisonbg
  • yes
  • no
  • abstain
• @ivanov
  • yes
  • no
  • abstain
• @lresende
  • yes
  • no
  • abstain
• @Zsailer
  • yes
  • no
  • abstain
• @blink1073
  • yes
  • no
  • abstain
• @willingc
  • yes
  • no
  • abstain
• @3coins
  • yes
  • no
  • abstain