search

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
57 stars 30 forks source link

Council membership and release rights #204

Closed fcollonval closed 9 months ago

fcollonval commented 1 year ago

Problem

We have a GitHub team for the JupyterLab council and another one for people with release ability.

There are currently 21 people at the council and 10 in the release team.

We should clarify how we manage people in the release team. We should keep the list of people with release power as low as possible for security reasons. We should align PyPI and NPM rights for people within the release team to all packages hosted in JupyterLab organization.

jtpio commented 11 months ago

For reference the release team was created as a follow-up to https://github.com/jupyterlab/team-compass/issues/167 and the switch to the new Governance model. See https://github.com/jupyterlab/team-compass/issues/167#issuecomment-1467693712 for more context.

It was bootstrapped with a list of people who had made JupyterLab releases in the past, or had expressed in helping with releases. It's a subset of the JupyterLab Council team.

Agree that it would be simpler to align the rights on all platforms. There are still previous maintainers with release rights that should likely be removed from the list as they are not part of the JupyterLab council.