search

jupyter-governance / ec-team-compass

A repository for Executive Council discussion, syncing, and meeting notes.
https://executive-council-team-compass.readthedocs.io/
BSD 3-Clause "New" or "Revised" License
3 stars 5 forks source link

Releases for `notebook` and `nbclassic` #55

Open RRosio opened 1 month ago

RRosio commented 1 month ago

The Notebook and NbClassic projects are currently part of the jupyter organization and are represented within the Jupyter Frontends team. However, the jupyterlab organization owns the frontends-team-compass and is also where the team responsible for managing JupyterLab releases resides. To streamline the release process for notebook and nbclassic, it might be beneficial to consolidate them under the same organization and establish a unified Jupyter Frontends release team by:

This came up during a conversation in this week's jupyter-frontends call.

cc: @krassowski

krassowski commented 1 month ago

This was in context of "who can add trusted publishers" on PyPI side.

For context, https://pypi.org/manage/organization/jupyter/teams/ currently has teams like "JupyterLab-owners" and "JupyterLab-maintainers". I am not sure what other teams there are and if there is a dedicated team for notebook.

Zsailer commented 1 month ago

The EC briefly discussed this today (apologies for the delay here; the LF transition has taken most of our bandwidth).

This should be an SSC decision instead of an EC. That said, both of these points made sense to the EC. I would engage the SSC to see what steps they would like you take. They may ask you to write a small JEP.