@@ -44,7 +43,6 @@ ambition of 170+ contributors with merged MRs per month to GitLab. This is align
In FY26 we will be continue our focus on the following key initiatives
- Increasing [MRARR](#mrarr) through our GitLab [co-create program](https://about.gitlab.com/community/co-create/). Aligned with our value [results for customers](/handbook/values/#results)
- Growing the number of unique new monthly contributors, code and non-code. Aligned with our [open source growth strategy](/handbook/engineering/open-source/growth-strategy/)
- Reducing [Open Community MR Age (OCMA)](#open-community-mr-age-ocma). Aligned with our [open source growth strategy](/handbook/engineering/open-source/growth-strategy/)
- Shifting the focus towards higher valued contributions aligned with our product roadmap. Aligned with our [open source growth strategy](/handbook/engineering/open-source/growth-strategy/)
@@ -154,21 +152,6 @@ More details can be found in the [Unique Wider Community Contributors per Month
More details can be found in the [OCMA Developer Relations PI section](/handbook/marketing/developer-relations/performance-indicators/#open-community-mr-age)
### MRARR
- Activities:
- Reach out to top tier enterprise customers
- Help take-on inactive customer contribution to completion & merge
- Partner with CSMs to enlist and facilitate contribution from customers
- Launch contribution materials targeting large enterprises
- Partner with Developer Advocacy and Strategy teams
- Maintain a list of known contributors with a mapping to their accounts and the accounts ARR contribution as input to this KPI
Please see [Contributing Orgs tracker](contributing-org-tracker) for details how to onboard or offboard a GitLab
account from being linked to a customer account, and being counted into the MRARR metric.
More details can be found at the [MRARR Developer Relations PI section](/handbook/marketing/developer-relations/performance-indicators/#mrarr)
## How we plan work
The team uses the [Developer Relations Engineering Kanban board](https://gitlab.com/groups/gitlab-org/-/boards/7745119?label_name[]=Contributor%20Success).
@@ -165,30 +165,6 @@ Adding a new corporate group under this namespace is as follows:
1.[Gitpod with GDK - Introduction (video)](https://www.youtube.com/watch?v=OzgGP5tT4bo)
1.[Gitpod with GDK - Setup (video)](https://www.youtube.com/watch?v=6VNm36wdXnI)
## Leading Organizations
### How do I add an organization or a user to an organization?
- Navigate to the [Contributing Org Tracker](/handbook/marketing/developer-relations/engineering/contributing-org-tracker).
- Go to the **MRARR Organization** tab.
- If a user is not listed here, you can add it to the respective row, or add a new
row at the bottom with the same structure.
### How do I enable the Leading Organizations program benefits for organizations
- Navigate to the [Contributing Org Tracker](/handbook/marketing/developer-relations/engineering/contributing-org-tracker).
- Go to the **Leading Organization** tab.
- Add the organization to the list with the exact same name as found in the **MRARR Organization** tab.
- Make sure you enter an entry date & current MR count from the last 3 months so we can look back and understand their performance over time.
### How do I stop the Leading Organizations program benefits for organizations
- Navigate to the [Contributing Org Tracker](/handbook/marketing/developer-relations/engineering/contributing-org-tracker).
- Go to the **Leading Organization** tab.
- Enter the exit date next to the respective organization that should no longer receive the benefits.
Caution: If an organization reaches the threshold it will be auto-enrolled in the program for receiving the review-time SLO.
## GitLab Notable Contributor Selection Process
See [GitLab Notable Contributor Selection Process](/handbook/marketing/developer-relations/engineering/notable-contributor-process).
@@ -555,7 +531,7 @@ Customized GitLab merchandise will be created for these contributors and will be
In an effort to understand, support, and empower the GitLab code contributor community, we have come up with the following lifecycle segments.
These lifecycle segments are assigned on an individual user level. For organizational recognition, see [Leading Organizations](/handbook/marketing/developer-relations/leading-organizations/).
These lifecycle segments are assigned on an individual user level.
- Link user accounts on GitLab.com to customers known to GitLab
- Format this in a form digestible to our BI tools by formatting it into JSON
- List the entry & exit dates of organizations into our Leading Organizations program
## Tabs
### MRARR Organization
Each customer known to GitLab to have contributed in the past is listed here with their Salesforce ID, a validation if they are already in the sheet and a tabular list of known user accounts that belong to that organization.
### MRARR Concise
Once the users are added to the MRARR Organization tab, the MRARR Concise summarizes this information for consumption by our BI tooling.
You should not edit this tab.
In our BI tooling, this tab can be found as `legacy.sheetload_gitlab_contributing_organizations` in the SAFE Intermediate Dashboards.
### Leading Organization
Each organization known to GitLab to have been onboarded in the [Leading Organization](/handbook/marketing/developer-relations/leading-organizations/) program is listed here, including the start date and the potential exit date.
It includes individuals that are not known in our Salesforce system, but still qualify for getting the benefits such as the Review Time SLO. The type of this column is a boolean.
In our BI tooling, this tab can be found as `workspace_engineering.leading_organization_entry_dates` in the SAFE Intermediate Dashboards.
