Verified Commit 9b4d3945 authored by Matija Čupić's avatar Matija Čupić
Browse files

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
 
In our [general guidelines](https://about.gitlab.com/handbook/general-guidelines/) we list: 'Use inclusive language. For example, prefer "Hi everybody" or "Hi people" to "Hi guys".'
In our [general guidelines](/handbook/general-guidelines/) we list: 'Use inclusive language. For example, prefer "Hi everybody" or "Hi people" to "Hi guys".'
 
### Inclusive interviewing
 
As part of [our interviewing process](https://about.gitlab.com/handbook/hiring/interviewing/) we list: "The candidate should be interviewed by at least one female GitLab team member."
As part of [our interviewing process](/handbook/hiring/interviewing/) we list: "The candidate should be interviewed by at least one female GitLab team member."
 
### Training
 
......@@ -69,8 +69,8 @@ To be truly inclusive is to be aware of your own ingrained biases as well as str
* [Equality Ally Strategies](https://trailhead.salesforce.com/trails/champion_workplace_equality/modules/workplace_equality_ally_strategies)
 
### GitLab Blog Posts
* [GitLab Offer Sponsorship of $500 for Diversity Events](https://about.gitlab.com/2016/02/02/gitlab-diversity-sponsorship/)
* [Rails Girls Summer of Code 2016](https://about.gitlab.com/2016/02/23/rails-girls-summer-of-code-2016/)
* [GitLab Offer Sponsorship of $500 for Diversity Events](/2016/02/02/gitlab-diversity-sponsorship/)
* [Rails Girls Summer of Code 2016](/2016/02/23/rails-girls-summer-of-code-2016/)
 
### Never done
 
......
......@@ -5,16 +5,16 @@ title: "GitLab Culture"
 
## Other pages related to Culture
 
- [GitLab 101](https://about.gitlab.com/culture/gitlab-101/)
- [GitLab Summits](https://about.gitlab.com/culture/summits)
- [Internal Feedback](https://about.gitlab.com/culture/internal-feedback)
- [Inclusion and Development](https://about.gitlab.com/culture/inclusion)
- [Top Team Member](https://about.gitlab.com/culture/top-team-member)
- [Remote Only](https://about.gitlab.com/culture/remote-only/)
- [GitLab 101](/culture/gitlab-101/)
- [GitLab Summits](/culture/summits)
- [Internal Feedback](/culture/internal-feedback)
- [Inclusion and Development](/culture/inclusion)
- [Top Team Member](/culture/top-team-member)
- [Remote Only](/culture/remote-only/)
 
## Introduction
 
Please see our [primer](https://about.gitlab.com/primer/) for more general information about GitLab.
Please see our [primer](/primer/) for more general information about GitLab.
 
![The GitLab Team in October 2017](/images/gitlab_team_summit_greece_2017.png){: .illustration}*<small>When October 2017 came around, the whole team already counted 200 GitLabbers!</small>*
 
......@@ -39,24 +39,24 @@ Sid announced [GitLab on HN](https://news.ycombinator.com/item?id=4428278).
 
### _September 14th, 2012_
 
[First 10 people get access](https://about.gitlab.com/2012/09/14/first-10-people-got-access/)
[First 10 people get access](/2012/09/14/first-10-people-got-access/)
to GitLab Cloud (now known as GitLab.com).
 
### _November 13th, 2012_
 
[GitLab CI is officially announced](https://about.gitlab.com/2012/11/13/continuous-integration-server-from-gitlab/).
[GitLab CI is officially announced](/2012/11/13/continuous-integration-server-from-gitlab/).
 
### _July 22nd, 2013_
 
[GitLab Enterprise Edition is announced](https://about.gitlab.com/2013/07/22/announcing-gitlab-enterprise-edition/).
[GitLab Enterprise Edition is announced](/2013/07/22/announcing-gitlab-enterprise-edition/).
 
### _April 18th, 2014_
 
[GitLab Cloud renamed to GitLab.com](https://about.gitlab.com/2014/04/18/gitlab-cloud-becomes-gitlab-com/).
[GitLab Cloud renamed to GitLab.com](/2014/04/18/gitlab-cloud-becomes-gitlab-com/).
 
### _March 4th, 2015_
 
[GitLab in Y Combinator winter 2015 batch](https://about.gitlab.com/2015/03/04/gitlab-is-part-of-the-y-combinator-family/).
[GitLab in Y Combinator winter 2015 batch](/2015/03/04/gitlab-is-part-of-the-y-combinator-family/).
 
### _August 15th, 2015_
 
......@@ -80,7 +80,7 @@ What better way to convey a sense of who we are and how we work together, than b
<div class="row">
<div class="col-sm-8 col-xm-12"><img src="../images/blogimages/boat.jpg" alt="The Boat"></div>
<div class="col-md-4 col-xm-12">
<p class="justify"><a href="https://about.gitlab.com/2016/01/06/our-y-combinator-experience/">Back then</a>, the whole team used to fit in one car. And the car was called "the Boat".</p>
<p class="justify"><a href="/2016/01/06/our-y-combinator-experience/">Back then</a>, the whole team used to fit in one car. And the car was called "the Boat".</p>
</div>
</div>
 
......
......@@ -19,25 +19,25 @@ title: "Remote Only"
1. Bond in real life
1. Give credit where it's due and remember to say thank you
 
For more information on working remotely at GitLab check out our [Remote Manifesto blog post](https://about.gitlab.com/2015/04/08/the-remote-manifesto/).
For more information on working remotely at GitLab check out our [Remote Manifesto blog post](/2015/04/08/the-remote-manifesto/).
 
## What Have We Learned about Remote Working?
 
How do we manage our entire [team](https://about.gitlab.com/team/) remotely? Sid Sijbrandij, CEO, shares the [secrets to managing 200 employees in 200 locations](https://www.youtube.com/watch?v=e56PbkJdmZ8).
How do we manage our entire [team](/team/) remotely? Sid Sijbrandij, CEO, shares the [secrets to managing 200 employees in 200 locations](https://www.youtube.com/watch?v=e56PbkJdmZ8).
 
Our policy of remote work comes from our [value](https://about.gitlab.com/handbook/values/) of boring solutions and was a natural evolution of team members choosing to work from home. Remote work allowed for the development of our publicly viewable [handbook](https://about.gitlab.com/handbook/). We like efficiency and do not like having to explain things twice.
Our policy of remote work comes from our [value](/handbook/values/) of boring solutions and was a natural evolution of team members choosing to work from home. Remote work allowed for the development of our publicly viewable [handbook](/handbook/). We like efficiency and do not like having to explain things twice.
 
In on-site companies they take processes, camaraderie, and culture for granted and have it develop organically. In a remote-only company you have to organize it, this is hard to do but as you scale it becomes more efficient while the the on-site organic approach fizzles out.
 
We have had success bonding with our coworkers in real life through our [Summits](https://about.gitlab.com/culture/summits/) that are organized every 9 months and our [Visiting Grants](https://about.gitlab.com/handbook/incentives/#sts=Visiting grant).
We have had success bonding with our coworkers in real life through our [Summits](/culture/summits/) that are organized every 9 months and our [Visiting Grants](/handbook/incentives/#sts=Visiting grant).
 
We have a daily [team call](https://about.gitlab.com/handbook/communication/#team-call) to talk about what we did outside of work. There is also a daily [functional group update](https://about.gitlab.com/handbook/people-operations/functional-group-updates/) in which one department shares their progress and challenges.
We have a daily [team call](/handbook/communication/#team-call) to talk about what we did outside of work. There is also a daily [functional group update](/handbook/people-operations/functional-group-updates/) in which one department shares their progress and challenges.
 
Our [expense policy](/handbook/spending-company-money/) provides for equipment, internet service, office space if they want that, and a local holiday party.
 
We encourage people to have [virtual coffee breaks](https://work.qz.com/1147877/remote-work-why-we-put-virtual-coffee-breaks-in-our-company-handbook/) and do a [monthly AMA with the CEO](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/2649/diffs).
 
We have an extensive [onboarding template](https://gitlab.com/gitlab-com/people-ops/employment/blob/master/.gitlab/issue_templates/onboarding.md) for new hires and organize a [GitLab 101](https://about.gitlab.com/culture/gitlab-101/) to ask questions.
We have an extensive [onboarding template](https://gitlab.com/gitlab-com/people-ops/employment/blob/master/.gitlab/issue_templates/onboarding.md) for new hires and organize a [GitLab 101](/culture/gitlab-101/) to ask questions.
 
 
 
......@@ -61,7 +61,7 @@ personal life although it might be difficult to find the right **balance**.
This can be mitigated by either explicitly planning your time off or plan when
you do work. When you don't work it is recommended to make yourself unavailable
by turning off Slack and closing down your email client. Coworkers should
allow this to work by abiding by the [communication guidelines](https://about.gitlab.com/2016/03/23/remote-communication#asynchronous-communication-so-everyone-can-focus).
allow this to work by abiding by the [communication guidelines](/2016/03/23/remote-communication#asynchronous-communication-so-everyone-can-focus).
 
If you worked at an office before, now you lack a default group to go out to
lunch with. To look at it from a different perspective, now you can select who
......@@ -84,7 +84,7 @@ You can join the #donut_be_strangers Slack channel to be paired with a random te
 
### Tips on Ergonomic Working
 
The goal of [office ergonomics](http://ergo-plus.com/office-ergonomics-10-tips-to-help-you-avoid-fatigue/) is to design your office work station so that it fits you and allows for a comfortable working environment for maximum productivity and efficiency. Since we all work from home offices, GitLab wants to ensure that each team member has the [supplies](https://about.gitlab.com/handbook/spending-company-money/) and knowledge to create an ergonomic home office.
The goal of [office ergonomics](http://ergo-plus.com/office-ergonomics-10-tips-to-help-you-avoid-fatigue/) is to design your office work station so that it fits you and allows for a comfortable working environment for maximum productivity and efficiency. Since we all work from home offices, GitLab wants to ensure that each team member has the [supplies](/handbook/spending-company-money/) and knowledge to create an ergonomic home office.
 
Below are some tips from the [Mayo Clinic](http://www.mayoclinic.org/healthy-lifestyle/adult-health/in-depth/office-ergonomics/art-20046169) how on how arrange your work station. If however, you develop any pains which you think might be related to your working position, please visit a doctor.
 
......
......@@ -75,7 +75,7 @@ Here's some footage our team put together to show how much fun we had.
 
### Summit in Amsterdam, the Netherlands
 
Here are some impressions from our [first Summit](https://about.gitlab.com/2015/11/30/gitlab-summit-2015/) in October 2015.
Here are some impressions from our [first Summit](/2015/11/30/gitlab-summit-2015/) in October 2015.
 
<br>
 
......@@ -129,7 +129,7 @@ growth of the organization.
* Use fist-bumps instead of handshaking to [reduce the number of people who get sick](https://www.health.harvard.edu/blog/fist-bump-better-handshake-cleanliness-201407297305).
* Use hand sanitizer after getting your food and before eating. [Shared buffet utensils spread disease.](http://www.cruisereport.com/crBlogDetail.aspx?id=3683) We will try to provide hand sanitizer.
* If you are sick please wear a [surgical mask](https://www.amazon.com/Maryger-Disposable-Procedure-Surgical-Counts/dp/B06XVMT3ZH/ref=sr_1_1_sspa?s=hpc&ie=UTF8&qid=1509481716&sr=1-1-spons&keywords=surgical+mask&psc=1) which [reduces the spreading by up to 80%](https://www.healthline.com/health/cold-flu/mask). We'll try to provide them.
* Remember our [values](https://about.gitlab.com/handbook/values/) and specifically the [permission to play](https://about.gitlab.com/handbook/values/#permission-to-play) behavior
* Remember our [values](/handbook/values/) and specifically the [permission to play](/handbook/values/#permission-to-play) behavior
* Be respectful of other hotel guests (e.g. don't talk on your floor when returning
to your room at night & keep your volume down at restaurants/bars).
* Utilize the resources available to understand the safety and crime considerations in the location we are visiting. Examples are the [UK's Foreign Travel Site](https://www.gov.uk/foreign-travel-advice) and the [U.S. State Department](https://travel.state.gov/content/passports/en/country.html). If you are alarmed by what you are reading, please feel free to reach out to People Ops Team with your concerns. We also advise reviewing the data for countries you feel are safe. You may find that even the safest countries have warnings on crime and safety. Staying with a group and away from known dangerous areas is the most basic way of avoiding problems.
......
......@@ -46,7 +46,7 @@ extra_js:
.row
.col-md-8
.c-brand
%a.c-brand-logo-wordmark{ href: "https://about.gitlab.com/"}
%a.c-brand-logo-wordmark{ href: "/"}
= partial "includes/logos/gitlab-wordmark-rgb-white.svg"
 
%h1
......@@ -1086,11 +1086,11 @@ extra_js:
 
.social-sharing
.social-sharing-item
%a.twitter-share-button{ href: "https://twitter.com/share?ref_src=twsrc%5Etfw", 'data-text' => "See the results from @gitlab's 2018 Global Developer Survey", 'data-url' => "https://about.gitlab.com/developer-survey/2018/", 'data-show-count' => "false" }Tweet
%a.twitter-share-button{ href: "https://twitter.com/share?ref_src=twsrc%5Etfw", 'data-text' => "See the results from @gitlab's 2018 Global Developer Survey", 'data-url' => "/developer-survey/2018/", 'data-show-count' => "false" }Tweet
%script{ async: true, src: "https://platform.twitter.com/widgets.js", charset: "utf-8" }
.social-sharing-item
%script{ src: "//platform.linkedin.com/in.js", type: "text/javascript" } lang: en_US
%script{ type: "IN/Share", 'data-url' => "https://about.gitlab.com/developer-survey/2018/" }
%script{ type: "IN/Share", 'data-url' => "/developer-survey/2018/" }
 
.row.u-margin-bottom-md.u-margin-bottom-xl
.col-md-8.col-md-offset-2
......
......@@ -240,7 +240,7 @@ easily manage their deployments.
 
<i class="vision-item fa fa-square-o" aria-hidden="true"></i> Push to Geo secondary (proxied to primary) <kbd>Premium</kbd><br>
<i class="vision-item fa fa-square-o" aria-hidden="true"></i> Automatic DR <kbd>Premium</kbd><br>
<i class="vision-item fa fa-square-o" aria-hidden="true"></i> Improve speed index https://about.gitlab.com/handbook/engineering/performance/#speed-index<br>
<i class="vision-item fa fa-square-o" aria-hidden="true"></i> Improve speed index /handbook/engineering/performance/#speed-index<br>
<%= product_vision["performance"] %>
 
## Distribution
......
......@@ -125,7 +125,7 @@ We want to help developers get their code into production; providing convenience
 
![GitLab CI/CD Scope](/images/direction/cicd/revised-gitlab-ci-scope.svg)
 
We define our vision as “[Auto DevOps](https://www.youtube.com/watch?v=KGrJguM361c)”: leveraging our [single application](https://about.gitlab.com/handbook/product/single-application/), it is simple to assist users in every phase of the development process, implementing automatic tasks that can be customized and refined to get the best fit for their needs.
We define our vision as “[Auto DevOps](https://www.youtube.com/watch?v=KGrJguM361c)”: leveraging our [single application](/handbook/product/single-application/), it is simple to assist users in every phase of the development process, implementing automatic tasks that can be customized and refined to get the best fit for their needs.
Our idea is that the future will have “auto CI” to compile and test software based on best practices for the most common languages and frameworks, “auto review” with the help of automatic analysis tools like Code Climate, “auto deploy” based on Review Apps and incremental rollouts on Kubernetes clusters, and “auto metrics” to collect statistical data from all the previous steps in order to guarantee performances and optimization of the whole process.
Dependencies and artifacts will be first-class citizens in this world: everything must be fully reproducible at any given time, and fully connected as part of the great GitLab experience.
 
......@@ -293,9 +293,9 @@ Moonshots are big hairy audacious goals that may take a long time to deliver.
 
## Scope
 
[Our vision](#vision) is to replace disparate DevOps toolchains with a single integrated application that is pre-configured to work by default across the complete DevOps lifecycle. Consider viewing [the presentation of our plan for 2018](https://about.gitlab.com/2017/10/11/from-dev-to-devops/).
[Our vision](#vision) is to replace disparate DevOps toolchains with a single integrated application that is pre-configured to work by default across the complete DevOps lifecycle. Consider viewing [the presentation of our plan for 2018](/2017/10/11/from-dev-to-devops/).
 
Inside our scope are the 7 stages of the DevOps lifecycle as detailed on [our features page](https://about.gitlab.com/features/). Also see our [complete DevOps vision](https://about.gitlab.com/2017/10/11/from-dev-to-devops/) for where we're going in 2018.
Inside our scope are the 7 stages of the DevOps lifecycle as detailed on [our features page](/features/). Also see our [complete DevOps vision](/2017/10/11/from-dev-to-devops/) for where we're going in 2018.
 
We try to prevent maintaining functionality that is language or platform specific because they slow down our ability to get results. Examples of how we handle it instead are:
 
......@@ -385,7 +385,7 @@ locking across branches.
 
GitLab allows you to develop and operate in GitLab, from planning to monitoring.
 
GitLab provides an [_single application_](https://about.gitlab.com/handbook/product/single-application/) that [_plays well with others_](#plays-well-with-others) for [_teams of any size_](#teams-of-any-size) with [_any kind of projects_](#any-project), while giving you [_actionable feedback_](#actionable-feedback).
GitLab provides an [_single application_](/handbook/product/single-application/) that [_plays well with others_](#plays-well-with-others) for [_teams of any size_](#teams-of-any-size) with [_any kind of projects_](#any-project), while giving you [_actionable feedback_](#actionable-feedback).
 
## Plays well with others
 
......@@ -395,9 +395,9 @@ GitLab plays well with others, even when you use only one part of GitLab it shou
 
GitLab ships with built-in integrations to many popular applications. We aspire to have the worlds best integrations for Slack, JIRA, and Jenkins.
 
Many other applications [integrate with GitLab](https://about.gitlab.com/integrations/), and we are open to adding new integrations to our [applications page](https://about.gitlab.com/applications/). New integrations with GitLab can very in richness and complexity; from a simple webhook, and all the way to a [Project Service](https://docs.gitlab.com/ee/user/project/integrations/project_services.html).
Many other applications [integrate with GitLab](/integrations/), and we are open to adding new integrations to our [applications page](/applications/). New integrations with GitLab can very in richness and complexity; from a simple webhook, and all the way to a [Project Service](https://docs.gitlab.com/ee/user/project/integrations/project_services.html).
 
GitLab [welcomes and supports new integrations](https://about.gitlab.com/integrations/) to be created to extend collaborations with other products.
GitLab [welcomes and supports new integrations](/integrations/) to be created to extend collaborations with other products.
GitLab plays well with others by providing APIs for nearly anything you can do within GitLab.
GitLab can be a [provider of authentication](https://docs.gitlab.com/ee/integration/oauth_provider.html) for external applications.
And of course GitLab is open source so people are very welcome to add anything that they are missing.
......
......@@ -8,16 +8,16 @@ acknowledge receipt of your vulnerability report the next business day and striv
 
Alternatively you may also send us your report via [HackerOne](https://hackerone.com/gitlab).
 
Please refrain from requesting compensation for reporting vulnerabilities. If you want we will [publicly acknowledge](https://about.gitlab.com/vulnerability-acknowledgements/) your responsible disclosure. We also try to make the confidential issue public after the vulnerability is announced, for an example see our [impersonation feature issue](https://gitlab.com/gitlab-org/gitlab-ce/issues/15548). HackerOne also makes the bug reports [public after 30 days](https://hackerone.com/disclosure-guidelines) if neither party objects, for an example see [the report for a persistent XSS on public project page](https://hackerone.com/reports/129736).
Please refrain from requesting compensation for reporting vulnerabilities. If you want we will [publicly acknowledge](/vulnerability-acknowledgements/) your responsible disclosure. We also try to make the confidential issue public after the vulnerability is announced, for an example see our [impersonation feature issue](https://gitlab.com/gitlab-org/gitlab-ce/issues/15548). HackerOne also makes the bug reports [public after 30 days](https://hackerone.com/disclosure-guidelines) if neither party objects, for an example see [the report for a persistent XSS on public project page](https://hackerone.com/reports/129736).
 
You are not allowed to search for vulnerabilities on GitLab.com itself. GitLab
is open source software, you can install a copy yourself and test against that. You can either download [CE](https://about.gitlab.com/downloads/), [EE](https://about.gitlab.com/downloads-ee/), or the [GitLab Development Kit](https://gitlab.com/gitlab-org/gitlab-development-kit).
is open source software, you can install a copy yourself and test against that. You can either download [CE](/downloads/), [EE](/downloads-ee/), or the [GitLab Development Kit](https://gitlab.com/gitlab-org/gitlab-development-kit).
If you want to perform testing without setting GitLab up yourself please contact us to
arrange access to a staging server.
 
You can find more details on how we handle [security releases here](https://gitlab.com/gitlab-org/release-tools/blob/master/doc/security.md).
 
On our website you can find more about [the availability and security of GitLab.com](https://about.gitlab.com/gitlab-com/#faq). Security issues that are not vulnerabilities can be seen on [our public issue tracker](https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=security).
On our website you can find more about [the availability and security of GitLab.com](/gitlab-com/#faq). Security issues that are not vulnerabilities can be seen on [our public issue tracker](https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=security).
 
## Confidential issues
 
......@@ -25,4 +25,4 @@ When a vulnerability is discovered we create a [confidential issue](https://docs
Security patches are pushed to [dev.gitlab.org](https://dev.gitlab.org), which is not publicly accessible, and merged into the `security` branch.
They should not appear on [GitLab.com](https://gitlab.com) until the security release has been announced and updated packages are available.
 
Details can be found in our [critical release process](https://about.gitlab.com/handbook/engineering/critical-release-process/).
Details can be found in our [critical release process](/handbook/engineering/critical-release-process/).
......@@ -12,4 +12,4 @@ However, Starter, Premium and Ultimate are all applicable under the policy.
 
GitLab's Educational pricing is for educational institutions, As per this model only staff are counted towards the 'user count', Students can be added free of charge after a purchase for staff users.
 
To avail of this offer please contact our sales team at https://about.gitlab.com/sales/
\ No newline at end of file
To avail of this offer please contact our sales team at /sales/
\ No newline at end of file
......@@ -137,5 +137,5 @@ extra_font:
.rad-event.rad-event-alt
%h1
GitLab Diversity Sponsorship
%a.btn.btn-lg.btn-red{type:"button", href: " https://about.gitlab.com/2016/03/24/sponsorship-update/"}
%a.btn.btn-lg.btn-red{type:"button", href: " /2016/03/24/sponsorship-update/"}
Learn more
......@@ -42,7 +42,7 @@ extra_css:
While GitLab is designed to use SCM & CI/CD in the same application, we understand the appeal of using GitLab CI/CD with GitHub version control. So, for the next year we are making the GitLab CI/CD for GitHub feature a part of our [GitLab.com](http://GitLab.com) Free tier. That means anyone using GitHub from personal projects and startups to SMBs can use GitLab CI/CD for free. Starting at 2000 free CI pipeline minutes, folks can also [add their own Runners](https://docs.gitlab.com/ee/ci/runners/README.html#registering-a-specific-runner) or upgrade plans to get more.
### Gemnasium customers
We recently [acquired Gemnasium](https://about.gitlab.com/press/releases/2018-01-30-gemnasium-acquisition.html). While we are super excited about having such a great team join our ranks, we also want to take care of folks that were using Gemnasium and provide them a migration path. We’ve already [shipped Gemnasium features](https://about.gitlab.com/2018/02/22/gitlab-10-5-released/#gemnasium-dependency-checks) as part of our built-in security scanning. Now, GitLab CI/CD for GitHub allows Gemnasium customers that were using GitHub + Gemnasium to begin using GitLab CI/CD for their security needs without needing to migrate their code.
We recently [acquired Gemnasium](/press/releases/2018-01-30-gemnasium-acquisition.html). While we are super excited about having such a great team join our ranks, we also want to take care of folks that were using Gemnasium and provide them a migration path. We’ve already [shipped Gemnasium features](/2018/02/22/gitlab-10-5-released/#gemnasium-dependency-checks) as part of our built-in security scanning. Now, GitLab CI/CD for GitHub allows Gemnasium customers that were using GitHub + Gemnasium to begin using GitLab CI/CD for their security needs without needing to migrate their code.
.col-md-4.col-md-offset-1.hidden-xs.hidden-sm
.ee-feature-icon
%img.hidden-xs{alt: "GitHub logo", src: "/images/logos/github-logo.svg"}/
......@@ -71,7 +71,7 @@ extra_css:
%h2 Use the #1 CI with GitHub
.overview
:markdown
GitLab has been [rated as industry-leading](https://about.gitlab.com/2017/09/27/gitlab-leader-continuous-integration-forrester-wave/) by Forrester. Previously, in order to take advantage of the best CI, you needed to host your code on GitLab. But now, you can use GitLab's top-rated CI tool with your code hosted on GitHub.
GitLab has been [rated as industry-leading](/2017/09/27/gitlab-leader-continuous-integration-forrester-wave/) by Forrester. Previously, in order to take advantage of the best CI, you needed to host your code on GitLab. But now, you can use GitLab's top-rated CI tool with your code hosted on GitHub.
%hr.divider/
.row#ci-cd-external-repo
......
......@@ -86,7 +86,7 @@ extra_css:
%li
%b Autoscaling:
you can
%a{href: "https://about.gitlab.com/2016/03/29/gitlab-runner-1-1-released/"} automatically spin up and down VM's
%a{href: "/2016/03/29/gitlab-runner-1-1-released/"} automatically spin up and down VM's
to make sure your builds get processed immediately and minimize costs.
%li
%b Build artifacts:
......@@ -124,7 +124,7 @@ extra_css:
to check if your code is valid
%li
Look at a live preview of your development branch with
%a{href: "https://about.gitlab.com/features/review-apps/"}Review Apps
%a{href: "/features/review-apps/"}Review Apps
before merging into stable
%li
%b Deploy
......@@ -214,7 +214,7 @@ extra_css:
%ul
%li
Please see
%a{href: "https://about.gitlab.com/getting-help/"} Getting help for GitLab
%a{href: "/getting-help/"} Getting help for GitLab
if you have questions
%li
Propose and discuss new features of CI/CD in the
......
Markdown is supported
0%