Add policy for membership

docs/team/becoming-member.md

@@ -1,10 +1,16 @@
 # Becoming a JupyterLab Council member
 
-## JupyterLab Council responsibilities
+This document describes how to become a council member. It includes information about the two subgroups of JupyterLab Council members:
+- The release group (see [Release team member](#release-team-member))
+- The admin group (see [Admin team member](#github-organization-owners))
+
+## JupyterLab Council member
+
+### JupyterLab Council responsibilities
 
 Active members actively carry out the responsibilities listed in the [Membership Guide Page](membership_guidelines).
 
-## Active and inactive membership
+### Active and inactive membership
 
 There are two types of JupyterLab Council members, **active** and **inactive**.
 
@@ -31,7 +37,7 @@ This means an inactive member can "reactivate" themselves at any time by publicl
 
 For example, a member who is going out on a long leave/vacation (>2 weeks) can temporarily change their status to inactive during their absence and immediately reactivate upon return. This isn't required, but this can relieve them from having to watch this repository for any formal votes that happen during their absence.
 
-## Nominating a new member
+### Nominating a new member
 
 For someone to become a JupyterLab Council member, they should already be a consistent,
 positive, productive member of the community. Newcomers are encouraged to
@@ -55,8 +61,54 @@ This process takes the following steps:
    if they are interested. Don't forget to run them by the {ref}`membership_guidelines`
    page to make sure they understand what they're signing up for.
 
-## Membership Maintenance
+### Membership Maintenance
 
-Every six months, one currently active member should open an issue in the team-compass repo asking all currently active team members to reply if they still consider themselves active. If not (or no response is given by a team member), it will be assumed that they have gone inactive. This will help keep the active member list up-to-date.
+Every six months, one currently active member should open an issue in the team-compass repo asking all currently active team members to reply within three weeks if they still consider themselves active. If a team member replies no, or does not reply, we will conclude that they are inactive. This will help keep the active member list up to date.
 
 Remember, an inactive member can return at any time by simply changing their status on the team-compass page.
+
+## Release team member
+
+### Joining the team
+
+Any JupyterLab Council member can ask to be part of the release team using the weekly call, chat, or official council email list.
+
+### Release team responsibilities
+
+Release team members can manage the following teams:
+
+- GitHub JupyterLab organization: membership of the [release team](https://github.com/orgs/jupyterlab/teams/release)
+- PyPI Jupyter organization: manager of the [JupyterLab team](https://pypi.org/manage/organization/jupyter/team/jupyterlab)
+- NPM jupyterlab organization: membership of the [jupyterlab team](https://www.npmjs.com/settings/jupyterlab/teams)
+- conda-forge jupyterlab recipe: maintainer rights
+
+> An admin will need to add a new member to all three teams.
+
+Members of these teams have publication rights for major JupyterLab-related packages. Team members can publish a release and can react quickly in case a published package is broken or corrupted.
+
+### Membership Maintenance
+
+Every six months, a bot will open an issue in the team-compass repo asking all currently team members to reply within three weeks if they still consider themselves active. If a member replies no, or they do not reply, we will conclude that they are inactive. Inactive members may be removed from their teams.
+
+## Admin team member
+
+### Joining the admin team
+
+Any JupyterLab Council member can ask to be part of the admin team using the weekly call, chat, or official council email list. There should be no more than four administrators. If there are four administrators already, consensus should be achieved between the new admin candidate and the existing administrators to determine a new four-person admin team.
+
+> The Software Steering Council representative will automatically be part of this group, in addition to the four members chosen above.
+
+### Admin team responsibilities
+
+Admin team members manage the following teams:
+
+- GitHub JupyterLab organization: [ownership](https://github.com/orgs/jupyterlab)
+- PyPI Jupyter organization: manager of the [JupyterLab team](https://pypi.org/manage/organization/jupyter/team/jupyterlab)
+- NPM jupyterlab organization: [ownership](https://www.npmjs.com/settings/jupyterlab)
+- conda-forge jupyterlab recipe: maintainer rights
+
+Administrators maintain membership of the teams listed above.
+
+### Membership Maintenance
+
+Every six months, a bot will open an issue in the team-compass repo asking all currently team members to reply within three weeks if they still consider themselves active. If a member says no, or they do not respond, we will conclude that they are inactive. Inactive members may be removed from their teams.

docs/team/member-guide.md

@@ -26,8 +26,10 @@ maintainers find and choose the right communication channels and have a positive
 In this respect, we are using:
 1. GitHub issues for specific discussions related to changing a repository's content
 (e.g. feature requests, bug reports).
-2. The [Discourse forum](http://discourse.jupyter.org/) for general discussions, support
+2. The [Discourse forum](https://discourse.jupyter.org/) for general discussions, support
 questions, or just as a place where we can inspire each other.
+3. The [Gitter channel](https://app.gitter.im/#/room/#jupyterlab_jupyterlab:gitter.im) for discussions and support questions.
+4. The [JupyterLab council mailing list](https://groups.google.com/u/1/g/jupyterlab-council) for discussing membership, none-public questions,... .
 
 ## How can I help?