<commit_before>---
layout: markdown_page
title: "GitLab Values"
---

## Summary

Our five values are results, efficiency, transparency, kindness, and diversity.
We want to get results because it enables us to do everything else.
We get results by being efficient with each-others time and with company money.
We communicate transparent both inside and outside the company.
We value kindness in our fellow team members.
And our team members are a set of diverse people.

## Results

1. **Do what you promised** We do what we promised to each-other, customers, users, and investors.
1. **Measure results not hours** We care about what you achieve; the code you shipped, the user you made happy, and the team member you helped. Do not compete by proclaiming how many hours you worked yesterday because we don't want someone who took the afternoon
off to feel like they did something wrong. Instead, celebrate the achievements of
yourself and your teammates.

## Efficiency

How: Efficiency, Iteration, Frugality, Boring solutions, ConvDev

Communicate (fear of conflict, lack of commitment): Transparency, Directness (being transparent with each-other), disagree and commit

Value (absence of trust): Collaboration, Kindness:

Who: Diversity, Quirkiness



1. **Transparency**: Be open about as many things as possible. By making information
public we can reduce the threshold to contribution and make collaboration easier.
An example is the [public repository of this website](https://gitlab.com/gitlab-com/www-gitlab-com/)
that also contains this [company handbook](https://about.gitlab.com/handbook/). Everything we do is public by default, for example, the [GitLab CE](https://gitlab.com/gitlab-org/gitlab-ce/issues) and [GitLab EE](https://gitlab.com/gitlab-org/gitlab-ee/issues) issue trackers, but also [marketing](https://gitlab.com/gitlab-com/marketing/issues) and [infrastructure](https://gitlab.com/gitlab-com/infrastructure/issues). Transparency creates awareness for GitLab, allows us to recruit people that care about our culture, it gets us more and faster feedback from people outside the company, and makes it easier to collaborate with them. It is also about sharing great software, documentation, examples, lessons,
and processes with the world in the spirit of open source, which we believe creates more value than it captures.
There are exceptions, material that is not public by default is documented in the [general guidelines](#general-guidelines). On a personal level, you should tell it like it is instead of putting up a poker face. Don't be afraid to admit you made a mistake or were wrong. When something went wrong it is a great opportunity to say "What’s the [kaizen](https://en.wikipedia.org/wiki/Kaizen) moment here?" and find a better way without hurt feelings.
1. **Efficiency**: We care about working on the right things, not doing more than needed,
and not duplicating work. This enables us to achieve more progress which makes our work more fulfilling.
We do the [smallest thing possible and get it out as quickly as possible](https://about.gitlab.com/2017/01/04/behind-the-scenes-how-we-built-review-apps/). If you make suggestions that can be excluded from the first iteration turn them into a separate issue that you link. Don't write a large plan, only write the first step. Close the meta issue after you defined the first iteration. Trust that you'll know better how to proceed after something is released. You're doing it right if you're slightly embarrassed by the minimal feature set shipped in the first iteration. Give short answers to verbal questions so the other party has to opportunity to ask more or move on. And keep 1 to many written communication short, as mentioned in [this HBR study](https://hbr.org/2016/09/bad-writing-is-destroying-your-companys-productivity): "A majority say that what they read is frequently ineffective because it’s too long, poorly organized, unclear, filled with jargon, and imprecise.".<commit_msg>Whitespace edit.<commit_after>---
layout: markdown_page
title: "GitLab Values"
---

## Summary

Our five values are results, efficiency, transparency, kindness, and diversity.
We want to get results because it enables us to do everything else.
We get results by being efficient with each-others time and with company money.
We communicate transparent both inside and outside the company.
We value kindness in our fellow team members.
And our team members are a set of diverse people.

## Results

1. **Do what you promised** We do what we promised to each-other, customers, users, and investors.
1. **Measure results not hours** We care about what you achieve; the code you shipped, the user you made happy, and the team member you helped. Do not compete by proclaiming how many hours you worked yesterday because we don't want someone who took the afternoon
off to feel like they did something wrong. Instead, celebrate the achievements of
yourself and your teammates.

## Efficiency

How: Efficiency, Iteration, Frugality, Boring solutions, ConvDev

Communicate (fear of conflict, lack of commitment): Transparency, Directness (being transparent with each-other), disagree and commit

Value (absence of trust): Collaboration, Kindness:

Who: Diversity, Quirkiness


1. **Transparency**: Be open about as many things as possible. By making information
public we can reduce the threshold to contribution and make collaboration easier.
An example is the [public repository of this website](https://gitlab.com/gitlab-com/www-gitlab-com/)
that also contains this [company handbook](https://about.gitlab.com/handbook/). Everything we do is public by default, for example, the [GitLab CE](https://gitlab.com/gitlab-org/gitlab-ce/issues) and [GitLab EE](https://gitlab.com/gitlab-org/gitlab-ee/issues) issue trackers, but also [marketing](https://gitlab.com/gitlab-com/marketing/issues) and [infrastructure](https://gitlab.com/gitlab-com/infrastructure/issues). Transparency creates awareness for GitLab, allows us to recruit people that care about our culture, it gets us more and faster feedback from people outside the company, and makes it easier to collaborate with them. It is also about sharing great software, documentation, examples, lessons,
and processes with the world in the spirit of open source, which we believe creates more value than it captures.
There are exceptions, material that is not public by default is documented in the [general guidelines](#general-guidelines). On a personal level, you should tell it like it is instead of putting up a poker face. Don't be afraid to admit you made a mistake or were wrong. When something went wrong it is a great opportunity to say "What’s the [kaizen](https://en.wikipedia.org/wiki/Kaizen) moment here?" and find a better way without hurt feelings.
1. **Efficiency**: We care about working on the right things, not doing more than needed,
and not duplicating work. This enables us to achieve more progress which makes our work more fulfilling.
We do the [smallest thing possible and get it out as quickly as possible](https://about.gitlab.com/2017/01/04/behind-the-scenes-how-we-built-review-apps/). If you make suggestions that can be excluded from the first iteration turn them into a separate issue that you link. Don't write a large plan, only write the first step. Close the meta issue after you defined the first iteration. Trust that you'll know better how to proceed after something is released. You're doing it right if you're slightly embarrassed by the minimal feature set shipped in the first iteration. Give short answers to verbal questions so the other party has to opportunity to ask more or move on. And keep 1 to many written communication short, as mentioned in [this HBR study](https://hbr.org/2016/09/bad-writing-is-destroying-your-companys-productivity): "A majority say that what they read is frequently ineffective because it’s too long, poorly organized, unclear, filled with jargon, and imprecise.".
{'fraction_non_alphanumeric': 0.06818181818181818, 'fraction_numerical': 0.004771471622300351, 'mean_word_length': 4.755057803468208, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 18, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3612801', 'n_tokens_mistral': 2012, 'n_tokens_neox': 1918, 'n_words': 1104}