Sed absolute links

parent ea5a5fc5
Pipeline #21244850 passed with stages
in 17 minutes and 21 seconds
......@@ -3,14 +3,14 @@ layout: markdown_page
title: About Us
---
1. GitLab is a [single application](https://about.gitlab.com/handbook/product/single-application/) with [features](/features/) for the whole software development and operations (DevOps) [lifecycle](https://about.gitlab.com/sdlc/).
1. GitLab, the open source project, is used by more than [100,000 organizations](/is-it-any-good/) and has a large [community](https://about.gitlab.com/community/) of more than [1900 people who contributed code](http://contributors.gitlab.com/).
1. GitLab is a [single application](/handbook/product/single-application/) with [features](/features/) for the whole software development and operations (DevOps) [lifecycle](/sdlc/).
1. GitLab, the open source project, is used by more than [100,000 organizations](/is-it-any-good/) and has a large [community](/community/) of more than [1900 people who contributed code](http://contributors.gitlab.com/).
1. GitLab Inc. is a open-core company that sells [subscriptions that offer more feature and support for GitLab](/products).
1. The company is [remote only](https://about.gitlab.com/culture/remote-only/) with [250 people working from their own location in more than 39 countries](/team/).
1. The company is [remote only](/culture/remote-only/) with [250 people working from their own location in more than 39 countries](/team/).
1. GitLab Inc. is an active participant in this community, see [our stewardship](/stewardship) for more information.
1. [Our history](/history) starts in 2011 for the open source project, and in 2015 we joined Y Combinator and started growing faster, we have a public [strategy](https://about.gitlab.com/strategy/#sequence).
1. [Our mission](https://about.gitlab.com/strategy/#mission) is to change all creative work from read-only to read-write so that **everyone can contribute**.
1. [Our history](/history) starts in 2011 for the open source project, and in 2015 we joined Y Combinator and started growing faster, we have a public [strategy](/strategy/#sequence).
1. [Our mission](/strategy/#mission) is to change all creative work from read-only to read-write so that **everyone can contribute**.
1. Our Tanuki (Japanese for raccoon dog) logo symbolizes this with a smart animal that works in a group to achieve a common goal, you can download it on our [press page](/press).
1. [Our values](/handbook/values) are Collaboration, Results, Efficiency, Diversity, Iteration, and Transparency (CREDIT) and these form an important part of our [culture](/culture).
1. Most of our internal procedures can be found in [publicly viewable 1000+ page handbook](/handbook) and our objects are documented in our [OKRs](https://about.gitlab.com/okrs/).
1. We [release](/releases/) every month on the 22nd and have a public [direction](https://about.gitlab.com/direction/#scope).
1. Most of our internal procedures can be found in [publicly viewable 1000+ page handbook](/handbook) and our objects are documented in our [OKRs](/okrs/).
1. We [release](/releases/) every month on the 22nd and have a public [direction](/direction/#scope).
......@@ -23,7 +23,7 @@ extra_js:
.container.js-suggestions
.container
%p.application-info
Every application that supports Git will work with GitLab. Below are some of the applications we wanted to highlight. To view the project services which are integrated into GitLab visit our <a href="https://docs.gitlab.com/ee/user/project/integrations/project_services.html">documentation page</a>. To learn more about integrating with GitLab and read how to add an application to this page, please head to our <a href="https://about.gitlab.com/integrations/">partners page</a>.
Every application that supports Git will work with GitLab. Below are some of the applications we wanted to highlight. To view the project services which are integrated into GitLab visit our <a href="https://docs.gitlab.com/ee/user/project/integrations/project_services.html">documentation page</a>. To learn more about integrating with GitLab and read how to add an application to this page, please head to our <a href="/integrations/">partners page</a>.
%h2.categories-header Application categories
.app-categories
- data.applications.each do |category|
......
......@@ -30,7 +30,7 @@ extra_js:
Because cloud native applications are often architectured using microservices instead of a monolithic application structure, they rely on containers to package the application’s libraries and processes for deployment. Microservices allow developers to build deployable apps that are decomposed into individual modules that focus on performing one specific service. This decentralization makes for a more stable environment by limiting the potential of full application failure due to an isolated problem.
%p.overview
Cloud orchestration tools, like
%a{ href: "https://about.gitlab.com/kubernetes/" }Kubernetes,
%a{ href: "/kubernetes/" }Kubernetes,
allow developers to coordinate the way in which an application’s containers will function, including scaling and deployment.
%p.overview
Cloud native app development requires a shift to a DevOps operating structure. This means development and operations teams will much work more collaboratively, leading to a faster and smoother production process.
......@@ -59,7 +59,7 @@ extra_js:
%p.overview
%strong
GitLab is a single application with everything you need for
%a{ href: "https://about.gitlab.com/sdlc/" }end-to-end software development and operations.
%a{ href: "/sdlc/" }end-to-end software development and operations.
From issue tracking and source code management to CI/CD and monitoring, having it all in one place simplifies toolchain complexity and speeds up cycle times. With a
%a{ href: "https://docs.gitlab.com/ee/user/project/container_registry.html" }built-in container registry
and
......@@ -97,7 +97,7 @@ extra_js:
%h3.feature-label Resource
%h2.feature-title Cloud Native Development with GitLab
%p.feature-description
%a.feature-more{ href: "https://about.gitlab.com/2017/04/18/cloud-native-demo/", target: "_blank" } Read more
%a.feature-more{ href: "/2017/04/18/cloud-native-demo/", target: "_blank" } Read more
.col-sm-12.col-md-6.col-lg-3.feature.js-all-clickable
.feature-media
= image_tag "/images/home/feature-thumb-gitlab-com.png", alt: 'GitLab.com screenshot'
......
......@@ -58,7 +58,7 @@ extra_js:
How does it work?
%h3.getting-started-subheader.text-center
:markdown
Your content will be published on the [GitLab blog](https://about.gitlab.com/blog){:.purple}.
Your content will be published on the [GitLab blog](/blog){:.purple}.
Occasionally more technical guides will be published as a [Technical Article](https://docs.gitlab.com/ee/development/writing_documentation.html#technical-articles){:.purple}
on the [GitLab Documentation site](https://docs.gitlab.com).
%section#steps.steps
......@@ -111,7 +111,7 @@ extra_js:
3. An introduction for your post
4. A line accepting the [terms and conditions](terms-and-conditions/):
> @rebecca I would like to write about this subject and I accept the `[terms](https://about.gitlab.com/community-writers/terms-and-conditions/)` of the Community Writers Program.
> @rebecca I would like to write about this subject and I accept the `[terms](/community-writers/terms-and-conditions/)` of the Community Writers Program.
Your sample will be pre-evaluated based on your writing style, approach, grammar, structure, context, and flow.
%hr
......@@ -211,7 +211,7 @@ extra_js:
We might ask you for further adjustments, and, once accomplished, it will be merged.
Most contributions to the Community Writers Program will be published on [the GitLab blog](http://about.gitlab.com/blog), but occasionally posts will be better suited to publishing in the [GitLab Documentation](https://docs.gitlab.com/) as a [Technical Article](https://docs.gitlab.com/ee/development/writing_documentation.html#technical-articles). We will let you know beforehand where your content will be published.
Most contributions to the Community Writers Program will be published on [the GitLab blog](/blog), but occasionally posts will be better suited to publishing in the [GitLab Documentation](https://docs.gitlab.com/) as a [Technical Article](https://docs.gitlab.com/ee/development/writing_documentation.html#technical-articles). We will let you know beforehand where your content will be published.
%hr
#step-7.step.js-step
......
......@@ -21,7 +21,7 @@ For an overview, please check the [Community Writers Program](../) webpage.
### Purpose of the program
The [Community Writers Program](../) has the purpose of sourcing high-quality stories for the [GitLab blog](http://about.gitlab.com/blog).
The [Community Writers Program](../) has the purpose of sourcing high-quality stories for the [GitLab blog](/blog).
### Requirements
......@@ -41,7 +41,7 @@ and to ensure it meets the standard of quality required by GitLab.
#### Desirable
- Writers should preferably be **experienced in writing in [Markdown](https://about.gitlab.com/handbook/product/technical-writing/markdown-guide/)** and able to structure
- Writers should preferably be **experienced in writing in [Markdown](/handbook/product/technical-writing/markdown-guide/)** and able to structure
their files without further assistance.
- Writers should preferably be active users of **Git and GitLab**, and must have a user
account on GitLab.com.
......@@ -69,7 +69,7 @@ drop us a line in the issue thread to let us know you're willing to tackle it:
```md
@rebecca I would like to write about this subject and I accept the
[terms](https://about.gitlab.com/community-writers/terms-and-conditions/)
[terms](/community-writers/terms-and-conditions/)
of the Community Writers Program.
```
......@@ -80,7 +80,7 @@ drop us a line in the issue thread to let us know you're willing to tackle it:
send us the first draft. In this case, the editor will drop a line in the issue thread:
```md
@user, you got it! Please write your draft in [Markdown](https://about.gitlab.com/handbook/product/technical-writing/markdown-guide/) and send
@user, you got it! Please write your draft in [Markdown](/handbook/product/technical-writing/markdown-guide/) and send
it in a [new confidential issue](https://gitlab.com/gitlab-com/community-writers/issues/new)
to this project. We do not open any attachments.
```
......@@ -95,7 +95,7 @@ Both labels "pre-assess" and "up-for-grabs" will be removed.
#### 3. Draft
- Writers should write based on our [**editorial style guide**](https://gitlab.com/gitlab-com/marketing/blob/master/content/editorial-style-guide.md).
- Writers should send us the first draft (written in **[Markdown](https://about.gitlab.com/handbook/product/technical-writing/markdown-guide/)**) through
- Writers should send us the first draft (written in **[Markdown](/handbook/product/technical-writing/markdown-guide/)**) through
a new confidential issue to be created by the authors themselves. We will not
open any attachments.
The new issue will be **confidential**, preserving the author's
......@@ -132,7 +132,7 @@ and the label "review in progress" will be removed.
#### 7. Get published and get paid
- Once your content has been approved for publishing, it will be scheduled by the editor and the merge request will be merged. The article will most likely be
published on the [GitLab blog](http://about.gitlab.com/blog), but occasionally posts will be better suited to publishing in the [GitLab Documentation](https://docs.gitlab.com/) as a [Technical Article](https://docs.gitlab.com/ee/development/writing_documentation.html#technical-articles). The editor will inform you if this is the case.
published on the [GitLab blog](/blog), but occasionally posts will be better suited to publishing in the [GitLab Documentation](https://docs.gitlab.com/) as a [Technical Article](https://docs.gitlab.com/ee/development/writing_documentation.html#technical-articles). The editor will inform you if this is the case.
- The original issue will be labeled "published".
- Once your content has been published, we will send you an invoice template to be filled with your personal data and instructions to proceed to receive the compensation previously agreed. GitLab will pay you in American Dollars (USD) from a bank account in the USA, via wired transfer to your bank account. Please check the [compensation limitations](#compensation-limitations) below.
- Both issues will be closed.
......@@ -176,7 +176,7 @@ the author **cannot** publish that content somewhere else until it's published b
totally or partially, on their own blog or somewhere else, as long as they provide attribution to GitLab:
```
This article was [originally published](link-to-article) by [GitLab](https://about.gitlab.com).
This article was [originally published](link-to-article) by [GitLab]().
```
**Note:** Once the content is published, GitLab reserves the right to change,
......@@ -209,7 +209,7 @@ In this case, you might be eligible for a [Guest Blog Post](/handbook/marketing/
### Program manager
The Community Writers Program is part of the [Content Marketing](https://about.gitlab.com/handbook/marketing/marketing-sales-development/content/) Team at GitLab.
The Community Writers Program is part of the [Content Marketing](/handbook/marketing/marketing-sales-development/content/) Team at GitLab.
[Rebecca Dodd](/team/#rebecca), the **Content Editor**, manages the program.
### Important notes
......
......@@ -8,7 +8,7 @@ suppress_header: true
![Community Sponsorship](/images/community/gitlab-growth.jpg)
In February 2016, [we announced a $500 USD grant](https://about.gitlab.com/2016/02/02/gitlab-diversity-sponsorship/) for events which promote diversity in technology.
In February 2016, [we announced a $500 USD grant](/2016/02/02/gitlab-diversity-sponsorship/) for events which promote diversity in technology.
Yep, all events which help increase diversity in technology automatically receive the grant.
If you intend to apply, please leave enough lead time (at least 4 weeks but
......@@ -30,9 +30,9 @@ If you're hosting an event which doesn't meet the description of an "event which
### Sponsored Events
You can take a look at the diversity events we sponsor on our [events page](https://about.gitlab.com/events/).
You can take a look at the diversity events we sponsor on our [events page](/events/).
### Other sponsorships
- In 2017 we are sponsoring larger initatives such as [Ruby Together](https://rubytogether.org/), but would like to expand our reach into the community through a more localized sponsorship program.
- A special grant for the integration of GitLab into the Open Science Framework (OSF). Please read how you can help: [OSF grant.](https://about.gitlab.com/2015/09/03/a-grant-to-help-us-integrate-gitlab-with-open-source-osf/)
- A special grant for the integration of GitLab into the Open Science Framework (OSF). Please read how you can help: [OSF grant.](/2015/09/03/a-grant-to-help-us-integrate-gitlab-with-open-source-osf/)
......@@ -9,16 +9,16 @@ title: "GitLab 101"
There is a monthly GitLab CEO 101 call with new hires and the CEO. Here we talk about the following topics. This is a zoom call. Please read the history and values links provided below and come prepared with questions. The call will be driven by questions asked by new employees. Make sure your full name is set in Zoom.
1. Questions about GitLab history [https://about.gitlab.com/history/](https://about.gitlab.com/history/)
1. Questions about our values [https://about.gitlab.com/handbook/values](https://about.gitlab.com/handbook/values)
1. Team structure [https://about.gitlab.com/team/structure/](https://about.gitlab.com/team/structure/) or [organization chart](/team/chart)
1. How we work [https://about.gitlab.com/handbook/general-guidelines](https://about.gitlab.com/handbook/general-guidelines)
1. Questions about GitLab history [/history/](/history/)
1. Questions about our values [/handbook/values](/handbook/values)
1. Team structure [/team/structure/](/team/structure/) or [organization chart](/team/chart)
1. How we work [/handbook/general-guidelines](/handbook/general-guidelines)
- Please pay special attention to the guideline about developing content and procedures in a public, transparent, [handbook-first](/handbook/general-guidelines/#handbook-first) manner
All questions and answers during the call are added to the FAQ on [https://about.gitlab.com/culture/gitlab-101/](https://about.gitlab.com/culture/gitlab-101/).
All questions and answers during the call are added to the FAQ on [/culture/gitlab-101/](/culture/gitlab-101/).
This is done during the call to immediately make any changes; for example we created [this commit](https://gitlab.com/gitlab-com/www-gitlab-com/commit/8cf1b0117dce5439f61e207315f75db96c917056) together on the call.
The calendar invite will say: "You need to prepare for this call, please see https://about.gitlab.com/culture/gitlab-101/ for details."
The calendar invite will say: "You need to prepare for this call, please see /culture/gitlab-101/ for details."
Below an example of the GitLab 101
......@@ -41,7 +41,7 @@ After you're finished with your introduction, invite the next person to talk.
### People Ops 101s
There is a monthly People Ops 101 Zoom call with new hires, our Chief Culture Officer (CCO), and members of the People Ops team. It is meant to occur following GitLabbers' participation in the CEO 101. The links above are good reading for both meetings. In addition to the topics above, new hires may be interested in our culture, [people priorities](https://about.gitlab.com/okrs/), [diversity](https://about.gitlab.com/handbook/values/#diversity) and [inclusion](https://about.gitlab.com/culture/inclusion/), [hiring](https://about.gitlab.com/handbook/hiring/), and a variety of other topics. Our CCO welcomes the team's questions and comments, but also appreciates hearing suggestions and ideas from GitLab's new hires.
There is a monthly People Ops 101 Zoom call with new hires, our Chief Culture Officer (CCO), and members of the People Ops team. It is meant to occur following GitLabbers' participation in the CEO 101. The links above are good reading for both meetings. In addition to the topics above, new hires may be interested in our culture, [people priorities](/okrs/), [diversity](/handbook/values/#diversity) and [inclusion](/culture/inclusion/), [hiring](/handbook/hiring/), and a variety of other topics. Our CCO welcomes the team's questions and comments, but also appreciates hearing suggestions and ideas from GitLab's new hires.
### Frequently Asked Questions about the GitLab Culture
......@@ -75,7 +75,7 @@ It's aggressive, it's possible, and it's realistic. Having a goal gives us clari
If we can make a product that is strong with all features from planning to monitoring, and it works well, then you have a chance. It should have benefits that you can only have with an integrated product, such as Cycle Analytics.
##### Q: Is it worth investing in trying to win the open source market from our competitors?
Our plan is to start with becoming the most popular tool for people’s own git hosting service; we’ve managed that so far. Secondly we want to get to be the one with the most revenue. Thirdly we want to become the most popular tool for hosting private repos. Once we’ve reached that we want to be the most popular tool for hosting public repos and lastly we want to be the number one tool for people to host not code but books, tech papers, visual models. movies etc. More info on this is on our [strategy page](https://about.gitlab.com/strategy/)
Our plan is to start with becoming the most popular tool for people’s own git hosting service; we’ve managed that so far. Secondly we want to get to be the one with the most revenue. Thirdly we want to become the most popular tool for hosting private repos. Once we’ve reached that we want to be the most popular tool for hosting public repos and lastly we want to be the number one tool for people to host not code but books, tech papers, visual models. movies etc. More info on this is on our [strategy page](/strategy/)
##### Q: Doesn't constant iteration sometimes lead to shipping lower quality work and a worse product?
We know that iteration is painful. If you're doing iteration correctly, it should be painful. However, if we take smaller steps and ship smaller simpler features, we get feedback sooner. Instead of spending time working on the wrong feature or going in the wrong direction, we can ship the smallest product, receive fast feedback, and course correct.
......@@ -112,7 +112,7 @@ By the end of the year, GitLab.com should be ready for mission critical workload
##### Q: How much fear is there in our user base that the open source edition of GitLab will deteriorate?
We have tried different business models and many didn’t work. As a company, we realized we need recurring revenue. To obtain that, we introduced Enterprise Edition. Initially, everyone was worried innovation would stop on the Community Edition. Within six months the Enterprise Edition was under the MIT license. The community saw we were building both products, which helped to build trust. Customers became confused, so after six months the arrangement stopped. Response was positive about the shift. We should keep improving both and keep our [stewardship promises](https://about.gitlab.com/stewardship).
We have tried different business models and many didn’t work. As a company, we realized we need recurring revenue. To obtain that, we introduced Enterprise Edition. Initially, everyone was worried innovation would stop on the Community Edition. Within six months the Enterprise Edition was under the MIT license. The community saw we were building both products, which helped to build trust. Customers became confused, so after six months the arrangement stopped. Response was positive about the shift. We should keep improving both and keep our [stewardship promises](/stewardship).
##### Q: How do you determine the line between open source and proprietary features?
It's ambiguous and difficult to get right. We listened to the community to find a good balance, and we were willing to iterate and make changes in order to make the community happy. The value needs to be there in order for people to pay for premium, and we think we provide that.
......
......@@ -17,7 +17,7 @@ We have also recorded a training on this subject:
### Identity data
Please see our [identity data](https://about.gitlab.com/culture/inclusion/identity-data)
Please see our [identity data](/culture/inclusion/identity-data)
### 100% remote
......@@ -29,29 +29,29 @@ Another practice we employ is to ask GitLab candidates to work on real issues as
### Diversity Sponsorship program
One of our biggest initiatives is the [GitLab Diversity Sponsorship program](https://about.gitlab.com/community/sponsorship/). This is a sponsorship opportunity we offer to any “diversity in tech” event globally. We offer funds to help support the event financially and, if the event is in a city we have a GitLab team member, we get hands-on by offering to coach and/or give a talk whenever possible.
One of our biggest initiatives is the [GitLab Diversity Sponsorship program](/community/sponsorship/). This is a sponsorship opportunity we offer to any “diversity in tech” event globally. We offer funds to help support the event financially and, if the event is in a city we have a GitLab team member, we get hands-on by offering to coach and/or give a talk whenever possible.
### Values
We try to make sure [our values](https://about.gitlab.com/handbook/values/) reflect our goal to be inclusive, [one of our top 6 values is diversity](https://about.gitlab.com/handbook/values/#diversity).
We try to make sure [our values](/handbook/values/) reflect our goal to be inclusive, [one of our top 6 values is diversity](/handbook/values/#diversity).
In addition, the very nature of our company is meant to facilitate inclusion. We believe in asynchronous communication where possible which enables our teammates to have flexibility in the hours and locations from which they work. The no-ask vacation time also contributes to making it easier to combine work with other obligations and activities, whether that be volunteering with inner city youth, helping your kids with homework, going to the gym or a variety of other activities.
### Double referral bonus
We want to encourage and support diversity on our team and in our hiring practices, so we will offer a [$2000 referral bonus](https://about.gitlab.com/handbook/incentives/#referral-bonuses) for hires from underrepresented groups in the tech industry for engineering roles at GitLab. This underrepresented group is defined as: women, African-Americans, Hispanic-Americans/Latinos, and veterans.
We want to encourage and support diversity on our team and in our hiring practices, so we will offer a [$2000 referral bonus](/handbook/incentives/#referral-bonuses) for hires from underrepresented groups in the tech industry for engineering roles at GitLab. This underrepresented group is defined as: women, African-Americans, Hispanic-Americans/Latinos, and veterans.
### Inclusive benefits
We list our [Transgender Medical Services](https://about.gitlab.com/handbook/benefits/#transgender-medical-services) and [Pregnancy & Maternity Care](https://about.gitlab.com/handbook/benefits/#pregnancy--maternity-care) publicly so people don't have to ask for them during interviews.
We list our [Transgender Medical Services](/handbook/benefits/#transgender-medical-services) and [Pregnancy & Maternity Care](/handbook/benefits/#pregnancy--maternity-care) publicly so people don't have to ask for them during interviews.
### Inclusive language