Office Hours

[jtpio]

Opening a new issue to track some ideas that were raised during the previous weekly calls.

As part of the Notebook v6 -> v7 transition, we should welcome folks from the community and help them with potential issues they might face. For example:

• migrating a Classic Notebook Server Extension to Jupyter Server
• migrating Notebook frontend extensions to JupyterLab / Notebook v7 extensions:
  • the extension might already be available as a built-in feature, or a third-party extension: https://jupyterlab-contrib.github.io/migrate_from_classical.html
  • if not, we should provide pointers and help them develop a prebuilt extension for Notebook v7 and JupyterLab
• providing both Notebook v7 and the v6 UI (only the UI) on the same deployment, especially for JupyterHub administrators. See proposal in Notebook Weekly Meetings Nov 2021 - Dec 2022 #5 (comment)

Probably this can take the form of another (weekly / bi-weekly) call. The Jupyter calendar being already pretty busy, it might however be difficult to find a good time for everyone.

[jtpio]

This was discussed yesterday during the Notebook Weekly Call: #5 (comment)

With the following notes:

• What's a good time for Jupyter Notebook / extension authoring office hours:
  • [william] I'm interested in this meeting, but mainly from the perspective of understanding more extensions more deeply, e.g., to encourage their porting to other frontends besides just JupyterLab. Example: https://github.com/jfbercher/jupyter_latex_envs
• Tentatively alternating Tuesdays at the same slot as Jupyter Security (8am Pacific)
• Potentially inviting people involved with these extensions.

One outcome was that we could start using this slot to work on nbgrader and see if folks join the call.

If they do, we can decide to continue working on nbgrader or other funded work. Or sometimes alternate with simpler extensions, for example based on the list in https://jupyterlab-contrib.github.io/migrate_from_classical.html

[jtpio]

If folks start joining the office hours and get comfortable writing extensions, it would also be a good way to onboard them to also contribute to core Notebook v7, since Notebook v7 is mostly a set of JupyterLab plugins.

[afshin]

I've added a slot in the Project Jupyter community calendar for our first Notebook v7 Extension Migration Office Hours on 3 May 2022.

[jtpio]

Given that Notebook 7 final is now released, we could try to reinstate these office hours to help users and extension authors port their extensions or simply answer the questions they may have.

Since we are often running out of time during the Notebook weekly call (which normally lasts 30 minutes), how about making the call 1 hour long instead for a little while? It could be for a couple of weeks or maybe months if it turns out to be useful.

So the proposal is: have the Notebook weekly call take the full hour on Wednesdays from 8am to 9am Pacific.

If no-one shows up we could also use this time for knowledge transfer (how to make a release, the lab / server stack, other topics).

cc @jupyter/notebook-council what do you think? I'm happy to post a message on Discourse and other places to announce this afterwards if that's something we would like to do.

[jtpio]

Closing in favor of jupyterlab/frontends-team-compass#237