@@ -364,7 +364,7 @@ Every time a contributor is opening a merge request to a GitLab namespace for th
### Working with the Core Team
More information on the [Core Team](https://about.gitlab.com/community/core-team/) is available in the [Core Team handbook page](/handbook/marketing/developer-relations/core-team/).
More information on the [Core Team](https://about.gitlab.com/community/core-team/) is available in the [Core Team handbook page](/handbook/marketing/developer-relations/engineering/core-team/).
@@ -8,7 +10,7 @@ A new member can be added to the [Core Team](https://about.gitlab.com/community/
1. Any Core Team member or GitLab Team member can nominate a new member from the wider community at any time using a confidential issue in [the Core Team group](https://gitlab.com/groups/gitlab-org/gitlab-core-team/-/issues) to limit any possible negative feedback in the smallest setting possible.
2. The nominee will be added to the Core Team if they have received positive votes from two-thirds (2/3) of all current core team members within a four-week period and accept the nomination.
3. Once a new member has been added, start the onboarding process by following the steps outlined in the [Core Team member orientation section](/handbook/marketing/developer-relations/core-team/#core-team-member-orientation) below.
3. Once a new member has been added, start the onboarding process by following the steps outlined in the [Core Team member orientation section](/handbook/marketing/developer-relations/engineering/core-team/#core-team-member-orientation) below.
## Monthly Core Team meetings
@@ -58,7 +60,7 @@ As part of the trust, value and recognition that joining the Core Team implies,
### Slack access
Core Team members are granted [access to the GitLab team's Slack instance](/handbook/tools-and-tips/#channels-access) as part of their [Core Team Member Orientation](#core-team-member-orientation).
Core Team members are granted [access to the GitLab team's Slack instance](/handbook/tools-and-tips/slack/#channels-access) as part of their [Core Team Member Orientation](#core-team-member-orientation).
A list of the up-to-date channels the Core should/have access to can be found in the [Core Team and Slack](https://docs.google.com/spreadsheets/d/1kohQBbvk2JSl3DXrmF5TDsWVoAMi_yujFWzzAP6vq2M/edit#gid=0) Google Sheets and in the list below:
@@ -316,7 +316,7 @@ Administrators can promote team members to trust level 4 manually, for example w
##### Core team members trust level
Core team members can be added to the [core-team](https://forum.gitlab.com/g/core-team) group through the [Core team onboarding process](/handbook/marketing/developer-relations/core-team/#becoming-a-core-team-member). This action grants [trust level 3](/handbook/marketing/developer-relations/workflows-tools/forum/#user-trust-levels). This group does not trigger any @-mention notifications in forum posts.
Core team members can be added to the [core-team](https://forum.gitlab.com/g/core-team) group through the [Core team onboarding process](/handbook/marketing/developer-relations/engineering/core-team/#becoming-a-core-team-member). This action grants [trust level 3](/handbook/marketing/developer-relations/workflows-tools/forum/#user-trust-levels). This group does not trigger any @-mention notifications in forum posts.
