Use JupyterLab with RTC for the weekly meetings

[jtpio]

Problem

There have been reports of RTC issues with the latest JupyterLab 3.6.1 release recently:

• Damaged notebook (duplicate cells) in RTC-active hosted hub jupyterlab#14031
• CRITICAL - data loss and notebook corruption on a hosted Lab instance jupyterlab#12154

Proposed Solution

As discussed during the JupyterLab weekly call yesterday it would be great to resume taking notes with JupyterLab and RTC enabled during the meetings. This could help catch and reproduce issues that might only happen when a lot of people are connected to the same server.

We could use a GitHub gist with the latest jupyterlab and jupyter-collaboration pre-releases such as this one: https://gist.github.com/jtpio/6027b2adb7ae04bd266debf519d91474

Or the tip of the JupyterLab master branch: https://mybinder.org/v2/gh/jupyterlab/jupyterlab/master

And paste the link at the top of the current Hackmd for visibility.

Additional context

Opening this issue to discuss which setup or protocol to use, in case anyone has any suggestions.

[JasonWeill]

We tried this earlier today and ran into the "double paste" bug (jupyterlab/jupyterlab#13731) and into situations where multiple edits of the same large markdown cell led to data loss. We may need further improvement before trying again.

[jtpio]

cc @jupyterlab/jupyterlab-council for awareness.

There is now a small note at the top of the Hackmd to make it easier to test the latest state of RTC with a 4.0 pre-release or the tip of the JupyterLab master branch:

[jtpio]

What's the general feeling about trying to resume using jupyter-collaboration for the weekly meetings?

Should we try again during the next meeting? Not this week because there is a community meeting: #223. But the week after for example.

There are likely still quite a few issues with the current RTC implementation that could be more easily discovered when trying with 10-20 people during the call.