@@ -119,12 +119,12 @@ Provide an outstanding, highly efficient and fast contributor experience, from o
#### Reduce Open Community MR Age
***Why:** Improve the speed of contribution to production by reducing [Open community MR Age (OCMA)](/handbook/marketing/developer-relations/performance-indicators/#open-community-mr-age) & review time. We have identified product groups with the highest OCMA. Analysis and improvements are needed to address product groups with the biggest opportunity. In addition to improving MR review and gathering feedback.
***Why:** Within [product groups](/handbook/company/structure/#product-groups), contribution submissions, backlog, and technology stack vary. Healthy community backlog alignment and the establishment of a common best practice for outreach are vital for contributor success. In addition, there should be a unified & known workflow for Wider Community Contributions.
@@ -148,7 +148,7 @@ Incentivize, attract and retain contributors by providing a compelling value and
#### Contributor recognition & advancement system
***Why:** In open source projects, contributors are motivated not only by solving bugs or adding features but also by gaining experience and building their online presence. This can be solved through levelling-up, badging or other incentivizing systems. In addition, providing sustained and impactful recognition to recognize & retain our contributors. Increase frequency and targeted recognition to types and persona of contributors
@@ -157,12 +157,12 @@ Center diversity, equity, and inclusion within our open source community relatio
#### Align with open source community DEI initiatives
***Why:** Aligning with open source communities practicing DEI initiatives will offer GitLab more ideas on reaching new contributors and signal our commitment to DEI to potential contributors.
***Why:** To improve the contributor experience for newcomers and returning contributors, and meet contributors at different experience levels. We can improve the changes of a contributor returning by creating a more inclusive experience for them.
@@ -176,12 +176,12 @@ Increase awareness with content and events to drive large amounts of contributor
#### Scale contributor events
***Why:** Build a sense of belonging, provide the social environment for contributors to have their voice, meet with their peers, share knowledge and celebrate.
***Why:** We need to scale office hour calls and our community pairing sessions that have traditionally been a unique opportunity for product groups to provide support, guidance to code contributors as well as gather feedback.
@@ -195,14 +195,14 @@ Leverage the full-time customer contributor model and create wider community tea
#### Returning & Frequent Contributors
***Why:** Increased contribution by motivating recurring contributions from organizations that use or extend GitLab, such as customers, partners and OSS communities. Reward those that achieve that status with GitLab benefits that are valuable to the individual and the organization.
***Why:** Our userbase is made of a lot of different personas who each can make valuable contributions and improve GitLab. Creating design proposals, code reviews, triaging our issues or facilitating healthy discussions between all actors involved helps us achieve our goals faster. In addition, recognizing non-code contributions such as helping GitLab with promoting the product, our events or other ways to contribute should be recognized and celebrated.
Hi! I started with GitLab in April, 2022 as a [Servant leader](/job-families/engineering/development/management/#requirements)(Director of Contributor Success) in the area of
