From 2191e957b03bf25a10b90c4fbe755deadbfa49e5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20Collonval?= Date: Wed, 19 Jul 2023 18:29:18 +0200 Subject: [PATCH 1/8] Add policy for membership --- docs/team/becoming-member.md | 62 ++++++++++++++++++++++++++++++++---- docs/team/member-guide.md | 3 +- 2 files changed, 58 insertions(+), 7 deletions(-) diff --git a/docs/team/becoming-member.md b/docs/team/becoming-member.md index dcc4243..ff22cd1 100644 --- a/docs/team/becoming-member.md +++ b/docs/team/becoming-member.md @@ -1,10 +1,16 @@ -# Becoming a JupyterLab Council member +# Becoming a JupyterLab team member -## JupyterLab Council responsibilities +This document describe first how to become a council member. Then the two subgroups of JupyterLab Council member will be specified: +- 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,52 @@ 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 3 weeks 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. 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 or the chat. + +### Release team responsibilities + +Release team member are granting the following rights: + +- 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) + +> One of the admin will need to grant the new rights on all three web services. + +Being part of those teams, you will be granted publication rights of major JupyterLab-related packages. Meaning you should be able to carry out a release and 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 3 weeks 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 imply the member will be removed for this subteam. + +## Admin team member + +### Joining the admin + +Any JupyterLab Council member can ask to be part of the admin team using the weekly call or the chat. If the number of administrators has reached 4 people; consensus should be achieved between the interestee and the existing administrators to get the new 4-people team. + +> The Software Steering Council representative will automatically be part of this group in addition to the 4 members. + +### Admin team responsibilities + +Admin team member are granting the following rights: + +- 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) + +Being administrators, you will have to maintain the rights of the member on the different projects. + +### Membership Maintenance + +Every six months, a bot will open an issue in the team-compass repo asking all currently team members to reply within 3 weeks 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 imply the member will be removed for this subteam. diff --git a/docs/team/member-guide.md b/docs/team/member-guide.md index 23e481f..0e98e68 100644 --- a/docs/team/member-guide.md +++ b/docs/team/member-guide.md @@ -26,8 +26,9 @@ 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. ## How can I help? From 0768c2c8ecfa1a79963c76823deab51685601d2b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20Collonval?= Date: Wed, 2 Aug 2023 17:23:08 +0200 Subject: [PATCH 2/8] Apply suggestions from code review Co-authored-by: Jason Grout Co-authored-by: Jason Weill <93281816+JasonWeill@users.noreply.github.com> --- docs/team/becoming-member.md | 28 +++++++++++++++------------- docs/team/member-guide.md | 1 + 2 files changed, 16 insertions(+), 13 deletions(-) diff --git a/docs/team/becoming-member.md b/docs/team/becoming-member.md index ff22cd1..a7c6c6d 100644 --- a/docs/team/becoming-member.md +++ b/docs/team/becoming-member.md @@ -1,6 +1,6 @@ -# Becoming a JupyterLab team member +# Becoming a JupyterLab Council member -This document describe first how to become a council member. Then the two subgroups of JupyterLab Council member will be specified: +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)) @@ -63,7 +63,7 @@ This process takes the following steps: ### 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 within 3 weeks 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. @@ -71,7 +71,7 @@ Remember, an inactive member can return at any time by simply changing their sta ### Joining the team -Any JupyterLab Council member can ask to be part of the release team using the weekly call or the chat. +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 @@ -80,33 +80,35 @@ Release team member are granting the following rights: - 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 -> One of the admin will need to grant the new rights on all three web services. +> An admin will need to add a new member to all three teams. -Being part of those teams, you will be granted publication rights of major JupyterLab-related packages. Meaning you should be able to carry out a release and react quickly in case a published package is broken or corrupted. +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 3 weeks 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 imply the member will be removed for this subteam. +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 +### Joining the admin team -Any JupyterLab Council member can ask to be part of the admin team using the weekly call or the chat. If the number of administrators has reached 4 people; consensus should be achieved between the interestee and the existing administrators to get the new 4-people 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 4 members. +> 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 member are granting the following rights: +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 -Being administrators, you will have to maintain the rights of the member on the different projects. +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 3 weeks 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 imply the member will be removed for this subteam. +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. diff --git a/docs/team/member-guide.md b/docs/team/member-guide.md index 0e98e68..48145d6 100644 --- a/docs/team/member-guide.md +++ b/docs/team/member-guide.md @@ -29,6 +29,7 @@ In this respect, we are using: 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? From f4e350a30ae86d49d18cc69c4bd23de2e76504dd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20Collonval?= Date: Wed, 2 Aug 2023 17:43:57 +0200 Subject: [PATCH 3/8] Update docs/team/becoming-member.md Co-authored-by: Jason Weill <93281816+JasonWeill@users.noreply.github.com> --- docs/team/becoming-member.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/team/becoming-member.md b/docs/team/becoming-member.md index a7c6c6d..c3bcc10 100644 --- a/docs/team/becoming-member.md +++ b/docs/team/becoming-member.md @@ -75,7 +75,7 @@ Any JupyterLab Council member can ask to be part of the release team using the w ### Release team responsibilities -Release team member are granting the following rights: +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) From 83fc397639742ddadae10bf575fa245d701bbb58 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20Collonval?= Date: Wed, 2 Aug 2023 17:44:58 +0200 Subject: [PATCH 4/8] Switch to use a bot also for Council membership active status --- docs/team/becoming-member.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/team/becoming-member.md b/docs/team/becoming-member.md index c3bcc10..0e8304d 100644 --- a/docs/team/becoming-member.md +++ b/docs/team/becoming-member.md @@ -63,7 +63,7 @@ This process takes the following steps: ### 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 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. +Every six months, a bot will 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. From 93ce1f49aa09109851e88a23616e449530cf47c8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20Collonval?= Date: Wed, 9 Aug 2023 18:12:45 +0200 Subject: [PATCH 5/8] Clarify the wording following Brian's suggestions --- docs/team/becoming-member.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/team/becoming-member.md b/docs/team/becoming-member.md index 0e8304d..f373a11 100644 --- a/docs/team/becoming-member.md +++ b/docs/team/becoming-member.md @@ -63,7 +63,7 @@ This process takes the following steps: ### Membership Maintenance -Every six months, a bot will 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. +Every six months, a bot will open an issue in the team-compass repo asking all currently active JupyterLab council 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. @@ -84,11 +84,11 @@ Release team members can manage the following teams: > 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. +Members of the release team have publication rights for major JupyterLab-related packages through the PyPI and NPM teams. 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. +Every six months, a bot will open an issue in the team-compass repo asking all current release 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 the release team (and be removed from the publication teams on PyPI and NPM). ## Admin team member @@ -111,4 +111,4 @@ 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. +Every six months, a bot will open an issue in the team-compass repo asking all current administrator 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. From 5008268de1890bb0077eb8418228634bc5ed2ab4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20Collonval?= Date: Wed, 16 Aug 2023 18:03:19 +0200 Subject: [PATCH 6/8] Remove the inactive member notion Vote will take place in the private council repo for security reasons --- docs/team/becoming-member.md | 63 ++++++++++++++---------------------- docs/team/member-guide.md | 2 +- 2 files changed, 26 insertions(+), 39 deletions(-) diff --git a/docs/team/becoming-member.md b/docs/team/becoming-member.md index f373a11..d793e25 100644 --- a/docs/team/becoming-member.md +++ b/docs/team/becoming-member.md @@ -8,34 +8,16 @@ This document describes how to become a council member. It includes information ### JupyterLab Council responsibilities -Active members actively carry out the responsibilities listed in the [Membership Guide Page](membership_guidelines). - -### Active and inactive membership - -There are two types of JupyterLab Council members, **active** and **inactive**. - -Active members: +Members actively carry out the responsibilities listed in the [Membership Guide Page](membership_guidelines): * Must be nominated by a current member. * Can be elected as the Software Steering Council representative for JupyterLab. * Get a vote in a voting situation. * Count towards quorum in a voting situation. -* Are expected to participate in a majority of votes. +* Are expected to participate in a 2/3 of votes (through a year). * Can nominate new members. * Should actively participate, either synchronously or asynchronously, in meetings. -Inactive members: - -* Were previously an active member. -* Do not vote. -* Are not counted towards voting quorum. -* Can "reactivate" at any time by expressing their change in status publicly. - -Council members can freely pass between active and inactive at any time. They *should* publicly state their status change in a pull request that updates the `contributors.yaml` file with their status change. - -This means an inactive member can "reactivate" themselves at any time by publicly stating their change in status. This does not require a nomination from another team member. - -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 @@ -61,54 +43,59 @@ 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 - -Every six months, a bot will open an issue in the team-compass repo asking all currently active JupyterLab council 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. +### Membership maintenance -Remember, an inactive member can return at any time by simply changing their status on the team-compass page. +Every six months, a bot will open an issue in the [council repo](https://github.com/jupyterlab/council) asking all currently active JupyterLab council team members to reply within three weeks if they still consider themselves active. If a team member replies no, they will be removed from the council. If a member does not reply, the council may reach that member personnaly for membership confirmation. If that request for confirmation is not answer within a month, the member will be removed from the council. ## Release team member -### Joining the team +### Joining the release team Any JupyterLab Council member can ask to be part of the release team using the weekly call, chat, or official council email list. +> Private channel is recommended to limit the exposure of such information for security reason. + ### Release team responsibilities -Release team members can manage the following teams: +Release team members will be added to the following groups: - 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 +- conda-forge jupyterlab recipes: maintainer rights -> An admin will need to add a new member to all three teams. +> An admin will need to add a new member to all three teams and the conda recipes. Members of the release team have publication rights for major JupyterLab-related packages through the PyPI and NPM teams. Team members can publish a release and can react quickly in case a published package is broken or corrupted. -### Membership Maintenance +### Release membership maintenance -Every six months, a bot will open an issue in the team-compass repo asking all current release 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 the release team (and be removed from the publication teams on PyPI and NPM). +Every six months, a bot will open an issue in the [council repo](https://github.com/jupyterlab/council) asking all current release 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 step down of the release team. Stepping down members may be removed from the publication groups on PyPI and NPM and the conda recipes maintainers. ## 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. +Any JupyterLab Council member can ask to be part of the admin team using the weekly call, chat, or official council email list. + +> Private channel is recommended to limit the exposure of such information for security reason. + +There should be no more than seven administrators. If there are seven administrators already, consensus should be achieved between the new admin candidate and the existing administrators to determine a new seven-person admin team. -> The Software Steering Council representative will automatically be part of this group, in addition to the four members chosen above. +> The Software Steering Council representative will automatically be part of this group. +> The Executive Council will and must own at least one administrator seat. If the last executive council administrator resigns, the executive council must nominate a new administrator. ### Admin team responsibilities -Admin team members manage the following teams: +Admin team members will be added to the following groups: -- GitHub JupyterLab organization: [ownership](https://github.com/orgs/jupyterlab) +- GitHub JupyterLab organization: [owners](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) +- NPM jupyterlab organization: [owners](https://www.npmjs.com/settings/jupyterlab) - conda-forge jupyterlab recipe: maintainer rights -Administrators maintain membership of the teams listed above. +Administrators maintain membership of the groups listed above as well as the JupyterLab council and release team. -### Membership Maintenance +### Membership maintenance -Every six months, a bot will open an issue in the team-compass repo asking all current administrator 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. +Every six months, a bot will open an issue in the [council repo](https://github.com/jupyterlab/council) asking all current administrator 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 step down. Stepping down member may be removed from the groups mentionned above. diff --git a/docs/team/member-guide.md b/docs/team/member-guide.md index 48145d6..8903bf5 100644 --- a/docs/team/member-guide.md +++ b/docs/team/member-guide.md @@ -48,7 +48,7 @@ We don't want team membership to be a big burden (many of us have one or more other jobs too!) but there are a few things that you should do as a new member: -1. **"Watch" the [team compass repository](https://github.com/jupyterlab/team-compass)** +1. **"Watch" the [team compass repository](https://github.com/jupyterlab/team-compass)** and the [counci repository](https://github.com/jupyterlab/council) so that you're notified when team conversations are happening. 2. **Stay up-to-date on team meetings**. You can find a notes from previous meetings pinned at the [top of the team-compass issues page](https://github.com/jupyterlab/team-compass/issues). From 1dfa48842ccc69ed8712bf54d66314e72b0a6fbe Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20Collonval?= Date: Thu, 7 Sep 2023 18:03:34 +0200 Subject: [PATCH 7/8] Update docs/team/becoming-member.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Michał Krassowski <5832902+krassowski@users.noreply.github.com> --- docs/team/becoming-member.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/team/becoming-member.md b/docs/team/becoming-member.md index d793e25..829bae0 100644 --- a/docs/team/becoming-member.md +++ b/docs/team/becoming-member.md @@ -45,7 +45,7 @@ This process takes the following steps: ### Membership maintenance -Every six months, a bot will open an issue in the [council repo](https://github.com/jupyterlab/council) asking all currently active JupyterLab council team members to reply within three weeks if they still consider themselves active. If a team member replies no, they will be removed from the council. If a member does not reply, the council may reach that member personnaly for membership confirmation. If that request for confirmation is not answer within a month, the member will be removed from the council. +Every six months, a bot will open an issue in the [council repo](https://github.com/jupyterlab/council) asking all currently active JupyterLab council team members to reply within three weeks if they still consider themselves active. If a team member replies no, they will be removed from the council. If a member does not reply, the council may reach that member personnaly for membership confirmation. If that request for confirmation is not answered within a month, the member will be removed from the council. ## Release team member From 81f50086dae6477815c434fe957bfe6d5656b866 Mon Sep 17 00:00:00 2001 From: Paul Ivanov Date: Fri, 8 Sep 2023 15:20:08 -0700 Subject: [PATCH 8/8] typo fixes --- docs/team/becoming-member.md | 4 ++-- docs/team/member-guide.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/team/becoming-member.md b/docs/team/becoming-member.md index 829bae0..d4aa3f8 100644 --- a/docs/team/becoming-member.md +++ b/docs/team/becoming-member.md @@ -45,7 +45,7 @@ This process takes the following steps: ### Membership maintenance -Every six months, a bot will open an issue in the [council repo](https://github.com/jupyterlab/council) asking all currently active JupyterLab council team members to reply within three weeks if they still consider themselves active. If a team member replies no, they will be removed from the council. If a member does not reply, the council may reach that member personnaly for membership confirmation. If that request for confirmation is not answered within a month, the member will be removed from the council. +Every six months, a bot will open an issue in the [council repo](https://github.com/jupyterlab/council) asking all currently active JupyterLab council team members to reply within three weeks if they still consider themselves active. If a team member replies no, they will be removed from the council. If a member does not reply, the council may reach that member personally for membership confirmation. If that request for confirmation is not answered within a month, the member will be removed from the council. ## Release team member @@ -98,4 +98,4 @@ Administrators maintain membership of the groups listed above as well as the Jup ### Membership maintenance -Every six months, a bot will open an issue in the [council repo](https://github.com/jupyterlab/council) asking all current administrator 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 step down. Stepping down member may be removed from the groups mentionned above. +Every six months, a bot will open an issue in the [council repo](https://github.com/jupyterlab/council) asking all current administrator 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 step down. Stepping down member may be removed from the groups mentioned above. diff --git a/docs/team/member-guide.md b/docs/team/member-guide.md index 8903bf5..84c4b01 100644 --- a/docs/team/member-guide.md +++ b/docs/team/member-guide.md @@ -42,13 +42,13 @@ when you interact with people (online and offline). Try to keep a friendly, posi attitude, and be welcoming and helpful in bringing others into the community and answering their questions. -### Are there any specific responsibilies? +### Are there any specific responsibilities? We don't want team membership to be a big burden (many of us have one or more other jobs too!) but there are a few things that you should do as a new member: -1. **"Watch" the [team compass repository](https://github.com/jupyterlab/team-compass)** and the [counci repository](https://github.com/jupyterlab/council) +1. **"Watch" the [team compass repository](https://github.com/jupyterlab/team-compass)** and the [council repository](https://github.com/jupyterlab/council) so that you're notified when team conversations are happening. 2. **Stay up-to-date on team meetings**. You can find a notes from previous meetings pinned at the [top of the team-compass issues page](https://github.com/jupyterlab/team-compass/issues).