|GitLab Team Handle||
|Team Boards||Backlog board, Kanban board, Technical board|
This team directly follows the strategy outlined in our open source growth strategy.
The goal of the team is to increase the technical improvements and efficiency of our contribution process to sustain our ambition of 1000+ contributors with merged MRs per month to GitLab.
In FY23 we will be focused on growing the number of unique new monthly contributors, reducing Open Community MR Age (OCMA) and increasing MRARR. This will increase development velocity without requiring additional engineering resources.
Parallel to this we'll increase observability of community contributed value through improving the business intelligence around it. This will allow us to create some predictability through foreshadowing. These efforts are cross-functional and require working together with Marketing and Product Development.
This accounts for 70 - 80% of the workload. The remaining 20 - 30% is ad-hoc work. The ad-hoc work is eclectic and ranges from supporting customers on contributions, supporting various open source initiatives and supporting the Engineering Productivity team.
|Nick Veenhof||Director, Contributor Success|
|Daniel Murphy||Fullstack Engineer, Contributor Success|
|Raimund Hook||Senior Fullstack Engineer, Contributor Success|
|Rémy Coutable||Staff Backend Engineer, Contributor Success|
There are 2 GitLab groups where the contributor success team is working with, so it can be confusing to understand what to put where. We should strive to be as transparent as possible and default to solutions and discussions that benefit the wider community. This is why, if you are in doubt, we ask you to default to projects in the gitlab-org group.
All issues that relate to the Open Source project GitLab and that can serve to enhance the contributor flow and are public by nature should be created here by default. We aim to not have any distinction between contributors or GitLab team-members for which we expect by default that everyone should be able to contribute to.
All issues that relate to the inner working of the company GitLab, including specific internal team workings, onboardings-issues or issues relating to customers that should be separated from the Open Source project GitLab can be placed here.
This team has the following immediate work items planned.
Every quarter, the team commits to Objectives and Key Results (OKRs). The below shows current and previous quarter OKRs, it updates automatically as the quarter progresses.
We have the following Performance Indicators
Community contributionlabel is automatically applied by the GitLab Bot to MRs submitted by wider community members.
gitLab-orglist of merge requests.
1st contributionlabel is added to first-time contributions. Every time a contributor is opening a merge request under the
gitlab-orgnamespace for the first time, the label
1st contributionis automatically applied to the merge request.
Merge request coaches are available to help contributors with their MRs. This includes:
coach will finishlabel will be added to the MR and the coach will either directly push new commits to the MR, or re-create a new MR with the original changes.
The list of current merge request coaches can be found in the team page by selecting
Merge Request Coach in the department filter.
There is also the
#mr-coaching channel in GitLab Slack if GitLab team members have any questions related to community contributions.
More information on merge request coaches (including how to become a merge request coach) can be found in the MR coach lifecycle page.
All external contributions to GitLab are subject to the GitLab DCO or CLA, depending on where the contribution is made and on whose behalf.
Instructions for corporate contributors to enter into an overarching Corporate CLA covering all contributions made on their behalf are set out on the DCO-CLA page.
We work with the Community Relations team, to recognize contributors
A nomination process is also available to nominate a contributor
There's a working group with members from Quality and Community Relations that aims to streamline and improve contributor efficiency. It implements key business iterations that results in substantial and sustained increases to community contributors & contributions.
The code contributor user journey is documented in the handbook - User Journey