Top Misused Terms - GitLab Communication

The wider community shouldn’t be excluded from being a GitLabber, we use team member instead. By definition, we are all international.

We might do a direct listing instead of an offering.

EE is a distribution and not all people who use EE pay us.

CE is a distribution and many Core users use EE.

We want to use inclusive language

We want to attract a diverse set of people

We have team members who are contractors

We are more than just our output.

People at GitLab are part of the community too.

Radical tends to be absolute and infers a lack of discretion. We are thoughtful and intentional about many things — informal communication, handbook-first documentation, onboarding, etc. — and have exceptions to transparency.

We are in it for the long-term and sprint implies fast, not quick.

The term has negative connotations and the word refinement is used by the Scrum Guide.

Using things like “obvious/as we all know/clearly” discourages people who don’t understand from asking for clarification.

There is no “they” or “headquarters” - there is only us as team members, and it’s one team. You could instead say something like “The Product team is looking at that issue…”. When used in the context of a pronoun, they is as valid as he, she, or any other pronoun someone decides to use.

We usually mean we’re removing a document or feature whereas deprecation is actually leaving the thing intact while discouraging its use. Unlike other terms on this list, there are times where “deprecate” is the right word, for example in formal product process.

A single person cannot be “diverse.” Using “diverse” as a noun is an “othering” term. Instead, someone may be from an underrepresented group. It is okay to describe a team or any collection of people as “diverse”, however.

Everyone has a technical knowledge that they used to perform in their role.

There are many kinds of search in the GitLab application; use complete feature names to describe areas.

Avoid this word since it has the connotation of third-party analytics. It also is too broad so use something more specific.

Rule of thumb is of dubious historical origins and can be considered a violent or non-inclusive term.

Deadline may have violent origins and we use due date in our user interface for issues.

Grandfathered has discriminatory origins.

Whitelist/Blacklist have connotations about value and map to racial terms.

Monitoring dashboard is too generic and is often confused with the GitLab’s self-monitoring features.

When referencing people, “different class of team member” or “being treated like you don’t belong/like an outsider” is preferred when discussing such environments, since citizen has political and socioeconomic connotations. In a hybrid-remote environment (e.g. not GitLab, which is all-remote), those outside of the office may feel inferior or deprioritized compared to coworkers who routinely work onsite.

While most timezones in the world are offset from UTC by a whole number of hours, a few are offset by 30 or 45 minutes.

It is gender-specific and therefore exclusionary.

It is gender-specific and implies that someone with less money would come up with a substandard solution compared to someone who has more money.

We should not associate forgetfulness with senior citizens.

Biweekly and bimonthly are ambiguous terms.

The term “functional group leader” is a past term that has now been updated. See Org Structure.

“Functional group” is a past term that is no longer used. See Org Structure.

Using these terms can cause confusion and lead to duplicate content. For example: Call it Contract Negotiation Handbook instead of Contract Negotiation Playbook

The original terms are outdated references and have socioeconomic connotations. There are also other color classifications that are less common.

We want to train ourselves to not mention customer names to allow us to be as transparent as possible. Whenever possible, we want to live stream our meetings to YouTube and to do that we need to be in the habit of not mentioning customer names. So we should avoid mentioning them even in privately streamed meetings.

The (Customer) Portal is an overloaded term which has come to represent multiple aspects in GitLab’s Fulfillment process. To disambiguate the different components of the system we should use more specific language.

This phrase is meant to refer to a situation where someone remembers something you did and holds it against you unfairly in a later circumstance. However it can unintentionally reinforce the idea that black is associated with negative or undesirable traits.

In the recruiting industry these are common terms to refer to companies targeting other company’s team members to hire them away. But they are violent and warlike. So it’s better to use the more literal, technical terms. While we want to keep voluntary attrition low as a company we should never forget that it is great for our team members if they get lots of great offers from other companies.

All solutions come with a trade-off between cost/complexity and uptime. Each availability component comes with its own complexity and maintenance. Users should thoroughly analyze the benefits of a solution against its costs and the team’s readiness.

While often natural to use this phrase when referring to a theoretical end-point of a developing feature there is historical sensitivity around the term and its use during World War II.