A new member can be added to the Core Team at any time through the following steps:
The Core Team meets on the third Tuesday of each month and anyone is welcome to join the call. Call logistics/agenda/notes for the meeting are available on the Core Team issue tracker. All meeting recordings are available at the Core Team meeting Playlist.
Core Team members can be reached by mentioning
@gitlab-org/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.
Anyone can open an issue in the Core Team issue tracker.
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.
All Core Team members are part of the
gitlab-org/gitlab-core-team group on GitLab.com. This group has a particular structure for specific automation purposes:
community-members group exists to:
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.
Core Team members are granted access to the GitLab team's Slack instance as part of their 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 Google Sheets and in the list below:
All the channels Core Team members have access to, should follow the SAFE guidelines when posting in the channel. Even though the Core Team Members have signed an NDA, they are not considered GitLab team members.
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.
Contributor Success 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 and ask a review from any member of Contributor Success.
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.
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.
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!