Core Team

1. You are here:
2. Handbook
3. Marketing
4. Community Relations
5. Code Contributor Program
6. Core Team

Maintained by:

On this page

• Becoming a Core Team member
• Monthly Core Team meetings
• Contacting Core Team members
• Offboarding and stepping down gracefully
• Core Team Member Orientation

Becoming a Core Team member

A new member can be added to the Core Team at any time through the following steps:

1. Current Core Team members can nominate a new member from the wider community at any time using a confidential issue in the Core Team group.
2. The nominee will be added to the Core Team if they accept the nomination and have received positive votes from two-thirds (2/3) of all current core team members within a two week period.
3. Once a new member has been added, create an onboarding issue in team-member-epics/employment using the onboarding template and fill out the "Core Team Members" section for developer access to gitlab-org, Slack access, etc. Core Team members are required to sign an NDA as a part of the on-boarding process.

Monthly Core Team meetings

The Core Team meets once a 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.

Contacting Core Team members

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 incoming+gitlab-core-team/general@incoming.gitlab.com. Core Team members who signed NDAs will also have access to GitLab Slack channels.

Offboarding and stepping down gracefully

If you are no longer able to or interested in serving in the Core Team, you should make an annoucement 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:

1. Move the individual from the team.yml file to the alumni.yml file.
2. Create an issue in team-member-epics/employment using the offboarding template and fill out the "Core Team Members" section to remove the individual from GitLab Slack, the Core Team Group, gitlab-org etc.

Core Team Member Orientation

1. Add the individual to the team.yml file.
2. Create an issue in the Lifecycle Management Project using the Core Team Member Orientation Issue Template and follow the steps outlined.