A new member can be added to the Core Team at any time through the following steps:
The Core Team meets on the second Wednesday of each month and anyone is welcome to join the call. Call logistics/agenda/notes for the meeting are available on the Core Team meeting page. All meeting recordings are available at the Core Team meeting Playlist.
Core Team members can be reached by mentioning
@gitlab-core-team in issues or merge requests.
While GitLab is the primary means of contact, the Core Team can also be contacted on the #core Slack channel.
Service Desk will also be used as a communication tool for Core Team members. Anyone can open an issue in the
gitlab-core-team project or contact the core team through email by sending an email directly to
firstname.lastname@example.org. Core Team members who signed NDAs will also have access to GitLab Slack channels.
If you are no longer able to or interested in serving in the Core Team, you should make an announcement on the
#core Slack channel. When you step down, you will become a Core Team Alumni. Once a Core Team member steps down, GitLab team member(s) will start the off-boarding activities to:
team.ymlfile to the
offboardingtemplate and fill out the "Core Team Members" section to remove the individual from GitLab Slack, the Core Team Group, gitlab-org etc.
As part of the trust, value and recognition that joining the Core Team implies, each member is granted a number of benefits to support them in their contributions.
The level of access varies from full to limited (as a multi-channel guest), depending on when the Core Team member joined the team. The ultimate goal is to have a consistent access level for all Core Team members, which is part of the discussion at https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/10371
To improve their development experience, Core Team members are granted
Developer permissions on the
gitlab-org group, where the vast majority of projects for GitLab (the product) reside. For any project under that group, and among other abilities, this enables them to:
At this time, Core Team members are not added to the
gitlab-com group , which is used for projects and processes associated to the GitLab company.
The Code Contributor Program Manager will generally take the action to grant this permission as part of the new Core Team member's orientation issue.
To emphasize their affiliation and closeness to the GitLab team, and to raise visibility on their profile, Core Team members can add themselves to the GitLab team page via the Code Contributor Program Manager (who will be able to merge the MR).
This will list their profile on the Core Team page as well.
To enable contributions and to gain insight on GitLab capabilities, Core Team members can request a free top tier license for development purposes via the Code Contributor Program Manager.
GitLab top tier licenses in SaaS or self-managed instances are granted to Core Team members for 1 year and can be renewed for another year during the Core Team member term. If a member decides to step down but still wishes to contribute to GitLab occasionally, they will still be eligible for a GitLab license, but the renewal period will be the standard 3 months given to other GitLab community members.
There is no specific limit on the number of seats that Core Team members can request. We trust Core Team members to use their own judgement to estimate the number of users they will need for development purposes, and not to use the license for for-profit purposes.
To support their code contributions to GitLab, Core Team members can request a JetBrains license for development purposes via the Code Contributor Program Manager.
To support contribution at in-person or virtual events, Core Team members will be eligible for sponsored access (subscription, accommodation, travel) to GitLab events (e.g. GitLab Contribute, GitLab Commit).
On occasion, the GitLab team might offer personalized merchandise exclusive to Core Team members to contribute in style!