Commit d50b7306 authored by Shane Rice's avatar Shane Rice

updated internal links that were using JS redirects

parent 74e15749
Pipeline #39081740 passed with stages
in 32 minutes and 16 seconds
......@@ -4838,7 +4838,7 @@ features:
Connect your projects hosted on GitHub and leverage
the power of GitLab CI/CD pipelines to build, test, and deploy your applications easily.
link_description: "Learn more about CI/CD for for GitHub"
link: /features/github/
link: /solutions/github/
screenshot_url: 'images/feature_page/screenshots/cicd_project.png'
category:
- continuous_integration
......
......@@ -112,7 +112,7 @@ features:
For many organizations, GitLab is a critical component of their software engineering
tool chain, powering not only their code repository but also CI/CD, issue management,
and much more. To ensure GitLab is available around the clock it can be deployed in a
[highly available configuration](/high-availability/), providing additional redundancy
[highly available configuration](/solutions/high-availability/), providing additional redundancy
and scale.
With GitLab 10.2, we are proud to announce that PostgreSQL High Availability is now
......
......@@ -605,7 +605,7 @@ features:
reporter: akaemmerle
issueboard_url: 'https://gitlab.com/groups/gitlab-org/-/boards/629512?milestone_title=11.2&=&label_name[]=Geo'
description: |
We continually focus on improving our [Geo](/features/gitlab-geo/) feature for distributed teams. Some of the noteworthy improvements in GitLab 11.2 include:
We continually focus on improving our [Geo](/solutions/geo/) feature for distributed teams. Some of the noteworthy improvements in GitLab 11.2 include:
* [Expose Geo project/file registry in the UI](https://gitlab.com/gitlab-org/gitlab-ee/issues/6851)
* [Repository and wiki verification errors now available via API](https://gitlab.com/gitlab-org/gitlab-ee/issues/5594)
......
......@@ -371,7 +371,7 @@ features:
reporter: akaemmerle
issueboard_url: 'https://gitlab.com/groups/gitlab-org/-/boards/763904?milestone_title=11.3&&label_name[]=Geo'
description: |
We continually focus on improving our [Geo](/features/gitlab-geo/) feature for distributed teams. Some of the noteworthy improvements in GitLab 11.3 include:
We continually focus on improving our [Geo](/solutions/geo/) feature for distributed teams. Some of the noteworthy improvements in GitLab 11.3 include:
- [`git fetch` and `git push` operations on secondary Geo nodes are now automatically redirected to the primary node when using SSH](https://gitlab.com/gitlab-org/gitlab-ee/issues/6533)
- [Disabled project wikis are now synced correctly](https://gitlab.com/gitlab-org/gitlab-ee/issues/6142)
......
......@@ -626,7 +626,7 @@ features:
reporter: akaemmerle
issueboard_url: 'https://gitlab.com/groups/gitlab-org/-/boards/796982?scope=all&utf8=✓&state=opened&label_name[]=Geo&milestone_title=11.4'
description: |
We continually focus on improving our [Geo](/features/gitlab-geo/) feature for distributed teams. Some of the additional noteworthy improvements in GitLab 11.4 include:
We continually focus on improving our [Geo](/solutions/geo/) feature for distributed teams. Some of the additional noteworthy improvements in GitLab 11.4 include:
- [Major performance improvements](https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8=✓&state=closed&label_name%5B%5D=Geo%20Performance&milestone_title=11.4)
- [Include keep-around references in checksum calculation](https://gitlab.com/gitlab-org/gitlab-ee/issues/5196)
......
......@@ -719,7 +719,7 @@ features:
reporter: akaemmerle
issueboard_url: 'https://gitlab.com/groups/gitlab-org/-/boards/805065?milestone_title=11.5&label_name[]=Geo'
description: |
We continually focus on improving our [Geo](/features/gitlab-geo/) feature for distributed teams. Some of the additional noteworthy improvements in GitLab 11.5 include:
We continually focus on improving our [Geo](/solutions/geo/) feature for distributed teams. Some of the additional noteworthy improvements in GitLab 11.5 include:
- [Rails console now always displays primary/secondary state correctly](https://gitlab.com/gitlab-org/gitlab-ee/issues/7963).
- [Secondary instances now show a more specific flash message on actionable pages](https://gitlab.com/gitlab-org/gitlab-ee/issues/8124).
......
......@@ -62,7 +62,7 @@ extra_css:
1. Mention `@gl/-docsteam` in a comment, then wait for a review. You may need to change things if a reviewer requests it.
1. Get your changes merged!
For those interested in writing full technical articles, we also have a [GitLab Community Writers Program](/community-writers/) which includes compensation.
For those interested in writing full technical articles, we also have a [GitLab Community Writers Program](/community/writers/) which includes compensation.
.block
.block-content
......
......@@ -109,7 +109,7 @@ extra_css:
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](/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
......@@ -161,7 +161,7 @@ extra_css:
:markdown
Your content will be evaluated by our content team. We will let you know if your post was approved to proceed or not. If approved, you'll receive feedback on your content.
The evaluation is based on particular [criteria](/community-writers/terms-and-conditions/#evaluation-criteria), defined by the [terms and conditions](/community-writers/terms-and-conditions/).
The evaluation is based on particular [criteria](/community-writers/terms-and-conditions/#evaluation-criteria), defined by the [terms and conditions](/community/writers/terms-and-conditions/).
%hr
#step-5.step.js-step
.container
......
......@@ -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](/community-writers/terms-and-conditions/)
[terms](/community/writers/terms-and-conditions/)
of the Community Writers Program.
```
......
......@@ -120,7 +120,7 @@ Our policy of remote work comes from our [value](/handbook/values/) of boring so
In on-site companies they take processes, camaraderie, and culture for granted and have it develop organically. In an all-remote 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](/company/culture/summits/) that are organized every 9 months and our [Visiting Grants](/handbook/incentives/#sts=Visiting grant).
We have had success bonding with our coworkers in real life through our [Summits](/company/culture/contribute/) that are organized every 9 months and our [Visiting Grants](/handbook/incentives/#sts=Visiting grant).
We have a daily [team call](/handbook/communication/#team-call) to talk about what we did outside of work. There is also a daily [Group Conversation](/handbook/people-operations/group-conversations/) in which one department shares their progress and challenges.
......
......@@ -72,7 +72,7 @@ extra_js:
%h2 Who
%p
:markdown
All team members of the [GitLab company](/company/team/), SOs, [Core Team](/core-team/), contributors, customers, press, and anyone interested in joining.
All team members of the [GitLab company](/company/team/), SOs, [Core Team](/community/core-team/), contributors, customers, press, and anyone interested in joining.
%h1 Attending Contribute
%br
......
......@@ -68,7 +68,7 @@ We do this when we realize that we've made a mistake applying our criteria, for
when we learned that a branded homepage was an [essential feature](https://news.ycombinator.com/item?id=10931347) or
when we [brought GitLab Pages to the Community Edition](/2016/12/24/were-bringing-gitlab-pages-to-community-edition/).
Our plan is to become the most popular tool for people’s own git hosting service; we’ve managed that so far. Secondarily, 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 just code but books, tech papers, visual models, movies, etc. More info on this is on our [strategy page](/strategy/)
Our plan is to become the most popular tool for people’s own git hosting service; we’ve managed that so far. Secondarily, 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 just code but books, tech papers, visual models, movies, etc. More info on this is on our [strategy page](/company/strategy/)
## How open source benefits from open core
......
......@@ -52,7 +52,7 @@ On June 4, 2018, Microsoft announced it had reached an agreement to acquire GitH
GitHuba is also offered in a self-managed version called GitHub Enterprise (GHE).
## Comments/Anecdotes
- Feedback from customers is that GitHub Enterprise (GHE) has trouble scaling. It seems like anyone nearing 2k users starts to run into issues. [GitLab is enterprise class](/enterprise-class/) and scales to > 32K users.
- Feedback from customers is that GitHub Enterprise (GHE) has trouble scaling. It seems like anyone nearing 2k users starts to run into issues. [GitLab is enterprise class](/solutions/enterprise-class/) and scales to > 32K users.
- 2018-09-10 - GitHub announces that [Microsoft Azure Pipelines are available in the GitHub Marketplace](https://blog.github.com/2018-09-10-azure-pipelines-now-available-in-github-marketplace/). This is in parallel with Microsoft (who recently acquired GitHub) announcing their Azure DevOps (rebranded VSTS/TFS). Related? Yes!
- 2018-09-10 - Microsoft announces the [addition of GitHub Pull Requests integrated directly into Visual Studio Code](https://code.visualstudio.com/blogs/2018/09/10/introducing-github-pullrequests). Visual Studio Code is [Microsoft's lightweight (but still not web based) code editor](https://azure.microsoft.com/en-us/products/visual-studio-code/).
- Statement from GitLab PS on 2018-11-12 - For scaling the fact that GitLab is so open makes it much easier to scale - especially for specific workloads. For GitHub Enterprise it’s a black box - only way to scale is “add another box”. Whereas GitLab can utilize cloud native technology - like Kubernetes or AWS tooling to scale.
......
......@@ -12,7 +12,7 @@ description: "Summary of how the Geo Team operates"
## The Geo Team
[Geo](/features/gitlab-geo/) is a [Premium](/pricing/) feature, built to help speed up the development of distributed teams by providing one or more read-only mirrors of a primary GitLab instance. This mirror (a Geo secondary node) reduces the time to clone or fetch large repositories and projects, can be used to run automated tests, or can be part of a Disaster Recovery solution.
[Geo](/solutions/geo/) is a [Premium](/pricing/) feature, built to help speed up the development of distributed teams by providing one or more read-only mirrors of a primary GitLab instance. This mirror (a Geo secondary node) reduces the time to clone or fetch large repositories and projects, can be used to run automated tests, or can be part of a Disaster Recovery solution.
### Team members
......
......@@ -13,7 +13,7 @@ title: "Deltas: Self-Managed and GitLab.com"
As GitLab's largest instance in operation, **GitLab.com is at the forefront of pushing GitLab's scalability limits**.
**GitLab.com** is the first production instance to run newer versions of GitLab and do so at scale. Thus, most scalability issues will usually manifest themselves on GitLab.com first. Its *always-on* nature coupled with its scale and our [committed availability objectives](/okrs/), drive GitLab.com to operate on **extremely tight time scales**:
**GitLab.com** is the first production instance to run newer versions of GitLab and do so at scale. Thus, most scalability issues will usually manifest themselves on GitLab.com first. Its *always-on* nature coupled with its scale and our [committed availability objectives](/company/okrs/), drive GitLab.com to operate on **extremely tight time scales**:
- GitLab.com will approach and potentially breach scalability walls before any other instance in operation
- Incidents have an immediate effect on our users, which is rapidly visible to the rest of the world.
......
......@@ -18,7 +18,7 @@ The goal of UX Research at GitLab is to connect with GitLab users all around the
1. Create a new issue using the `Research proposal` template in the [UX research project](https://gitlab.com/gitlab-org/ux-research) and `@` mention the relevant UX Researcher, UX Designer, and Product Manager for the product stage. Ensure you answer all questions outlined in the `Research proposal` template.
* You can find out who the relevant UX Researcher and/or UX Designer is by looking at the [team page](/team/) and filtering by the `UX` department. To find out who the relevant Product Manager is, take a look at the [Product category page](/handbook/product/categories/).
* You can find out who the relevant UX Researcher and/or UX Designer is by looking at the [team page](/company/team/) and filtering by the `UX` department. To find out who the relevant Product Manager is, take a look at the [Product category page](/handbook/product/categories/).
* Anybody across GitLab can raise a research proposal, this includes UX Researchers.
......
......@@ -5,4 +5,4 @@ description: "Start today and earn up to $200 an article."
twitter_image: /images/handbook/marketing/community-writers-twitter-illustration.png
---
This page has been [moved](/community-writers/).
This page has been [moved](/community/writers/).
......@@ -137,7 +137,7 @@ More info about why this skill is so helpful to the tanuki is explained in the f
- [GitLab Resources](/resources/)
- [GitLab Blog](/blog/)
- [GLU GitLab University](https://docs.gitlab.com/ee/university/)
- [GitLab Primer](/primer/)
- [GitLab Primer](/company/)
- [Sales Qualification Questions](/handbook/sales-qualification-questions/)
- [FAQ from Prospects](/handbook/sales-faq-from-prospects/)
- [Platzi GitLab Workshop](https://courses.platzi.com/classes/git-gitlab/)
......
......@@ -260,7 +260,7 @@ To add a new feature, add a feature block to under the `features:` section of th
- link_description: OPTIONAL, anchor text of a link that will appear below the descriptions e.g. `link: https://docs.gitlab.com/ee/user/project/milestones/`
- link: OPTIONAL, the url of the link (no quotes)
- screenshot_url: OPTIONAL, the path to a screenshot of the feature in quotes. e.g. `screenshot_url: 'images/feature_page/screenshots/28-group-milestones.png'`
- category: a list of one or more categories that this features belongs to. Adding a category to a feature causes it to show up in the features section on the product page for that category (e.g. see the [Continuous Integration page](/product/ci/))
- category: a list of one or more categories that this features belongs to. Adding a category to a feature causes it to show up in the features section on the product page for that category (e.g. see the [Continuous Integration page](/product/continuous-integration/))
- solution: REQUIRED legacy field. A [stage of the DevOps lifecycle](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/stages.yml). Will be [removed soon](https://gitlab.com/gitlab-com/www-gitlab-com/issues/2435).
- tier: `true` or `false` is this feature or capability available in this tier? `gitlab_core`, `gitlab_starter`, `gitlab_premium`, `gitlab_ultimate`
- gitlab_com: `true` or `false` is this feature or capability available on GitLab.com? Because GitLab.com tiers map 1:1 to self-managed tiers setting this will automatically assign the GitLab.com tier. E.g. `gitlab_core: true` + `gitlab_com: true` == `GitLab.com Free`. Adding a tiers fields is what powers the tier badges on product pages and comparison pages, as well as powers the tier [feature comparison of the pricing page](https://about.gitlab.com/pricing/self-managed/feature-comparison/).
......
......@@ -96,7 +96,7 @@ Our company is committed to following all applicable wage and hour laws and regu
### Substance Abuse
GitLab strives to maintain a workplace that is free from illegal use, possession, sale, or distribution of alcohol or controlled substances. Legal or illegal substances shall not be used in a manner that impairs a person’s performance of assigned tasks. This will help to maintain the efficient and effective operation of the business, and to ensure customers receive the proper service. GitLab team members must also adhere the local laws of where they reside and where they travel to, including the [GitLab Summit](/company/culture/summits/).
GitLab strives to maintain a workplace that is free from illegal use, possession, sale, or distribution of alcohol or controlled substances. Legal or illegal substances shall not be used in a manner that impairs a person’s performance of assigned tasks. This will help to maintain the efficient and effective operation of the business, and to ensure customers receive the proper service. GitLab team members must also adhere the local laws of where they reside and where they travel to, including the [GitLab Summit](/company/culture/contribute/).
### Employee Information Privacy
......
......@@ -204,7 +204,7 @@ Maybe we should make our features easier to search to replace the section below.
[Clement Ho]: /company/team/#ClemMakesApps
[Aricka]: /company/team/#arickaflowers
[Suri]: /company/team/#suripatel
[Pages]: /features/pages/
[Pages]: /product/pages/
[Geo]: /features/gitlab-geo/
[Continuous Integration (CI)]: /features/gitlab-ci-cd/
[Continuous Delivery (CD)]: /features/gitlab-ci-cd/
......
......@@ -1102,7 +1102,7 @@ UX in order to commit to the contents of the next release.
#### Special consideration
The roadmap should also delimit which items will be delivered prior to the
next [summit](/company/culture/summits/), as well as prior to
next [summit](/company/culture/contribute/), as well as prior to
the end of the current calendar year. These delimitations will help determine
both the internal and external communication for both product and marketing.
......
......@@ -17,7 +17,7 @@ title: "Technical Writing"
* [Workflow][technical writing workflow]
* [Markdown Guide](/handbook/product/technical-writing/markdown-guide/)
* [Community writers](/community-writers/)
* [Community writers](/community/writers/)
* [Release posts](/handbook/marketing/blog/release-posts/)
## Technical Writing
......
......@@ -266,7 +266,7 @@ Here is also a list of resources that you may find useful to include on your lan
- [What is GitLab EE](/features/#enterprise)
- [CE vs EE comparison](/products/#compare-options)
- [GitLab CI](/features/gitlab-ci-cd/)
- [GitLab Geo](/features/gitlab-geo/)
- [GitLab Geo](/solutions/geo/)
- [Pricing](/products/)
- [GitLab Blog](/blog/)
- [GitLab Culture](/company/culture/)
......
......@@ -111,7 +111,7 @@ Workflow for creating an issue:
- Choose a template from the **Choose a template** dropdown and take a look at the
**Typical kinds of issues created** below.
- Fill in all the relevant sections
- @mention someone in the issue to attract attention to it. Choose an expert [here](/team/) or feel free to ask
- @mention someone in the issue to attract attention to it. Choose an expert [here](/company/team/) or feel free to ask
in the `#support-team-chat` channel on Slack who it should be reviewed by. Do not worry that you are poking
someone to review a job when you don't even know them and they might be much more senior than you,
if it's not appropriate for them, they will know the right person to pass it along to and do that.
......
......@@ -28,7 +28,7 @@ help and advice—in fact, you're expected to do so. Anyone can chime in on any
feedback in the smallest setting possible. One-on-one video calls are preferred.
1. **Say thanks** Recognize the people that helped you publicly, for example in our [#thanks chat channel](/handbook/communication/#internal-communication).
1. **Give feedback effectively** Giving feedback is challenging, but it's important to deliver it effectively. When providing feedback, always make it about the work itself, focus on the business impact and not the person. Make sure to provide at least one clear and recent example. If a person is going through a hard time in their personal life, then take that into account. An example of giving positive feedback is our [thanks chat channel](/handbook/communication/#internal-communication). For managers, it's important to realize that employees react to a negative incident with their managers [six times more strongly](https://hbr.org/2013/03/the-delicate-art-of-giving-fee) than they do to a positive one. Keeping that in mind, if an error is so inconsequential that the value gained from providing criticism is low, it might make sense to keep that feedback to yourself. In the situations where negative feedback must be given, focus on the purpose for that feedback: to improve the employee’s performance going forward. Give recognition generously, in the open, and often to [generate more engagement](http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=SA&subtype=WH&htmlfid=LOW14298USEN) from your team.
1. **Get to know each other** We use a lot of text-based communication, and if you know the person behind the text, it will be easier to prevent conflicts. So encourage people to get to know each other on a personal level through our [company calls](/handbook/communication/#company-call), [virtual coffee breaks](/company/culture/all-remote/#coffee-break-calls), and during our [summit](/company/culture/summits/).
1. **Get to know each other** We use a lot of text-based communication, and if you know the person behind the text, it will be easier to prevent conflicts. So encourage people to get to know each other on a personal level through our [company calls](/handbook/communication/#company-call), [virtual coffee breaks](/company/culture/all-remote/#coffee-break-calls), and during our [summit](/company/culture/contribute/).
1. **Don't pull rank** If you have to remind someone of the position you have in the company, you're doing something wrong. People already know [our decision-making process](https://about.gitlab.com/handbook/leadership/#making-decisions). Explain why you're making the decision, and respect everyone irrespective of their function.
1. **Address behavior, but don't label people** There is a lot of good in [this article](http://bobsutton.typepad.com/my_weblog/2006/10/the_no_asshole_.html) about not wanting jerks on our team, but we believe that **jerk** is a label for behavior rather than an inherent classification of a person. We avoid classifications.
1. **Say sorry** If you made a mistake apologize, saying sorry is not a sign of weakness but one of strength. The people that do the most work will likely make the most mistakes. Additionally, when we share our mistakes and bring attention to them, others can learn from us, and the same mistake is less likely to repeated by someone else.
......@@ -190,7 +190,7 @@ Occasionally, values can contradict each other. For instance, transparency would
## Updating our values
Our values are updated continually when needed. Everyone is welcome to make a suggestion to improve them. To update: make a merge request and assign it to the CEO. If you're a [team member](/company/team/) or in the [core team](/core-team/) please post a link to the MR in the #values channel. If you're not part of those groups please send a direct Twitter message to [@sytses](https://twitter.com/sytses).
Our values are updated continually when needed. Everyone is welcome to make a suggestion to improve them. To update: make a merge request and assign it to the CEO. If you're a [team member](/company/team/) or in the [core team](/community/core-team/) please post a link to the MR in the #values channel. If you're not part of those groups please send a direct Twitter message to [@sytses](https://twitter.com/sytses).
## How do we reinforce our values
......
......@@ -28,7 +28,7 @@
%li{class: ("active" if current_page.url == "/features/jira/")}
%a{href: "/features/jira"}
JIRA Integration
%li{class: ("active" if current_page.url == "/features/github/")}
%li{class: ("active" if current_page.url == "/solutions/github/")}
%a{href: "/features/github"}
GitHub Integration
%li{class: ("active" if current_page.url == "/features/jenkins/")}
......
......@@ -14,6 +14,6 @@ CVE-2014-3514 affects applications which pass unsanitized user input to the Acti
GitLab 7.1 nor its dependencies use `create_with`.
GitLab 7.2 (to be released) does use `create_with` in two locations, but neither of those two call sites passes user input to the method.
We would like to thank Robert Schilling and Jeroen van Baarsen of the [GitLab core team](/core-team/) for their assistance in investigating this issue.
We would like to thank Robert Schilling and Jeroen van Baarsen of the [GitLab core team](/community/core-team/) for their assistance in investigating this issue.
Please contact us at support@gitlab.com if you have any questions about this issue.
......@@ -44,7 +44,7 @@ Being aware that our code is open source also makes us hold ourselves to a highe
We want to ensure that GitLab has a long future and will always be maintained with great care.
We have found that release management, vulnerability disclosure handling and performance improvement take a lot of time.
And while more than [680 people contributed to GitLab](http://contributors.gitlab.com/) there is always a need for more effort.
The [GitLab Core team](/core-team/) is full of people donating their time to help with this.
The [GitLab Core team](/community/core-team/) is full of people donating their time to help with this.
But to offer a worry-free experience to the most demanding users we do need a paid development effort as well.
We want to be good stewards of GitLab and we do never want to be [forced to sell to an organization that doesn't share our goals](http://en.wikipedia.org/wiki/Sun_acquisition_by_Oracle#MySQL_petition_and_forks).
......
......@@ -36,7 +36,7 @@ you can restart GitLab with `sudo gitlab-ctl restart` (for Omnibus packages) or
Rebooting one of our [gitlab.com production
servers](/2015/01/03/the-hardware-that-powers-100k-git-repos/) can easily take
5 minutes. To reduce the downtime for our users we used our [DRBD-based High
Availability setup](/high-availability/). First we
Availability setup](/solutions/high-availability/). First we
installed updated packages on our stand-by server, followed by a reboot. Then
we did a failover from the active server to the stand-by in under a minute.
This gives us the same end result as a server reboot, namely gitlab.com running
......
......@@ -58,7 +58,7 @@ Once point of contact for your questions, one contract to bother legal with, one
Sure, there might be caveats.
You now have a single solution.
However, that solution is [scalable](/high-availability/) and you can set up disaster recovery if you want.
However, that solution is [scalable](/solutions/high-availability/) and you can set up disaster recovery if you want.
You might think that one tool restricts you to just one workflow.
However, Git allows for a number of different workflows for your teams to choose from.
......
......@@ -38,4 +38,4 @@ You will be asked about how it should be configured. Once you do it you are pret
## Final word
I'm also happy to join [GitLab Core Team](/core-team/). I guess that my role there will be to make this project better and better and to make the CI solution simpler and more robust.
I'm also happy to join [GitLab Core Team](/community/core-team/). I guess that my role there will be to make this project better and better and to make the CI solution simpler and more robust.
......@@ -232,7 +232,7 @@ file](http://doc.gitlab.com/omnibus/update/README.html).
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
## Updating
......
......@@ -259,7 +259,7 @@ using the new 'Jenkins CI' project service instead. See [GitLab Jenkins document
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
## Updating
......
......@@ -258,7 +258,7 @@ file](http://doc.gitlab.com/omnibus/update/README.html).
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
## Updating
......
......@@ -7,7 +7,7 @@ image_title: '/images/blogimages/write-gitlab.jpg'
categories: company
---
Update: Please see our updated [Community Writers Program](/community-writers/)
Update: Please see our updated [Community Writers Program](/community/writers/)
We’re opening our blog up to contributions from the community.
When you get published on our blog at [GitLab](/blog) you can earn $50 to $200 for technical articles.
......@@ -38,7 +38,7 @@ What we're looking for...
- In-depth tutorials or opinion pieces of 1,500+ words.
Review [our call for writers](/community-writers/) for the kinds of topics we're looking for.
Review [our call for writers](/community/writers/) for the kinds of topics we're looking for.
## New to GitLab? That's OK!
......@@ -72,4 +72,4 @@ These are some ideas our team have in their wishlist. Do you see something you c
1. Publish.
1. Get paid.
Visit [our call for writers](/community-writers/) for more information on how to get started.
Visit [our call for writers](/community/writers/) for more information on how to get started.
......@@ -310,7 +310,7 @@ We recommend everybody to keep using Ruby 2.1 for now._
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
## Updating
......
......@@ -379,7 +379,7 @@ file](http://doc.gitlab.com/omnibus/update/README.html).
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
## Updating
......
......@@ -302,7 +302,7 @@ can be changed by adding a [`/etc/gitlab/skip-auto-migrations` file](http://doc.
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
## Updating
......
......@@ -52,13 +52,13 @@ but you're free to [define any other stage][stages-doc] in your
## GitLab Container Registry
In this release, we are supercharging GitLab CI. First with Pipelines and now with GitLab Container Registry.
GitLab Container Registry is a secure and private registry for Docker images. It isn't just a
standalone registry; it's completely integrated with GitLab. In fact, our container registry is
actually the first Docker registry that is fully-integrated with git repository
GitLab Container Registry is a secure and private registry for Docker images. It isn't just a
standalone registry; it's completely integrated with GitLab. In fact, our container registry is
actually the first Docker registry that is fully-integrated with git repository
management and comes out of the box with GitLab 8.8. So if you've upgraded, you already have it!
Our integrated Container Registry requires no additional installation. It allows for easy
Our integrated Container Registry requires no additional installation. It allows for easy
upload and download of images from GitLab CI. And it's free. We were so excited about this feature
that we wrote a whole blog post about it. [Read the full post](/2016/05/23/gitlab-container-registry/).
that we wrote a whole blog post about it. [Read the full post](/2016/05/23/gitlab-container-registry/).
## .gitignore templates
......@@ -204,8 +204,8 @@ If you installed GitLab from source using a custom SystemD / Upstart service def
## GitLab Mattermost 3.0 not included in the 8.8 release
[Mattermost 3.0](http://www.mattermost.org/mattermost-3-0-multi-team-accounts-mobile-desktop-upgrades-japanese-integrations-for-outlook-ruby-rust/) is a major release requiring [manual upgrade steps](http://www.mattermost.org/upgrade-to-3.0/) and therefore not included in 8.8 omnibus-gitlab package.
Existing GitLab Mattermost users will have to wait until GitLab 8.9 where upgrade to Mattermost 3.1 should be automated.
[Mattermost 3.0](http://www.mattermost.org/mattermost-3-0-multi-team-accounts-mobile-desktop-upgrades-japanese-integrations-for-outlook-ruby-rust/) is a major release requiring [manual upgrade steps](http://www.mattermost.org/upgrade-to-3.0/) and therefore not included in 8.8 omnibus-gitlab package.
Existing GitLab Mattermost users will have to wait until GitLab 8.9 where upgrade to Mattermost 3.1 should be automated.
If you're interested in reading more about how this decision was made, check out [the issue on GitLab.com](https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1286).
Also the upgrade design for the next release will be discussed in the same issue so please share your feedback there.
......@@ -214,7 +214,7 @@ Also the upgrade design for the next release will be discussed in the same issue
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
## Updating
......
......@@ -31,7 +31,7 @@ Contributors, you are awesome! As a thank you, we will be sending you a letter a
a special sticker that we’ve designed just for our contributors. Our community means a lot to us
and we hope that this shows a small token of our appreciation!
If you’re thinking about contributing, please do! Here’s where you can [find out more about contributing to GitLab](/contributing/).
If you’re thinking about contributing, please do! Here’s where you can [find out more about contributing to GitLab](/community/contribute/).
No problem if you’re new to Ruby -- we welcome learners, and
there are multiple checks in place to help you improve your skills and to help us make sure
everything’s up to scratch by the time it goes out.
......
......@@ -490,7 +490,7 @@ file](http://doc.gitlab.com/omnibus/update/README.html).
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
## Updating
......
......@@ -378,7 +378,7 @@ file](http://doc.gitlab.com/omnibus/update/README.html).
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
## Updating
......
......@@ -536,7 +536,7 @@ _**Note:** this article was originally posted by [AkitaOnRails]._
[doc-runner]: https://gitlab.com/gitlab-org/gitlab-runner/blob/master/docs/install/autoscaling.md#prepare-the-docker-registry-and-cache-server
[Docker image]: https://hub.docker.com/r/codeminer42/ci-ruby/
[docker-conf]: http://www.rubyconf.com.br/pt-BR/speakers#Paulo%20Diovani%20Gon%C3%A7alves
[documentation]: /installation/
[documentation]: /install/
[douglas]: https://gitlab.com/u/dbalexandre
[evang]: http://www.akitaonrails.com/2007/9/22/jogar-pedra-em-gato-morto-por-que-subversion-no-presta
[gabriel]: https://gitlab.com/u/brodock
......
......@@ -66,7 +66,7 @@ To update, check out our [update page](/update).
## Sign up for security notices
Want to be alerted to new security patches as soon as they're available? Sign up
for our [Security Newsletter](/contact/).
for our [Security Newsletter](/company/contact/).
## Enterprise Edition
......
......@@ -60,7 +60,7 @@ To update, check out our [update page](/update).
## Sign up for security notices
Want to be alerted to new security patches as soon as they're available? Sign up
for our [Security Newsletter](/contact/).
for our [Security Newsletter](/company/contact/).
## Enterprise Edition
......
......@@ -510,7 +510,7 @@ file](http://doc.gitlab.com/omnibus/update/README.html).
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
## Updating
......
......@@ -104,7 +104,7 @@ To update, check out our [update page](/update/).
## Sign up for security notices
Want to be alerted to new security patches as soon as they're available? Sign up
for our [Security Newsletter](/contact/).
for our [Security Newsletter](/company/contact/).
## Enterprise Edition
......
......@@ -65,7 +65,7 @@ To update, check out our [update page](/update/).
## Sign up for security notices
Want to be alerted to new security patches as soon as they're available? Sign up
for our [Security Newsletter](/contact/).
for our [Security Newsletter](/company/contact/).
## Enterprise Edition
......
......@@ -402,7 +402,7 @@ file](http://doc.gitlab.com/omnibus/update/README.html).
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
## Updating
......
......@@ -344,7 +344,7 @@ file](http://doc.gitlab.com/omnibus/update/README.html).
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
## Updating
......
......@@ -16,7 +16,7 @@ Most teams use external tools to track time, but we wanted to give them a more n
- The `/spend` command will let you record the time you spent working on a task e.g. `/spend 10h 45m`. Multiple spend commands add to the total time spent, visible in the sidebar.
- The `/estimate` command will let you enter a time estimate. Contrary to the `/spend` command, the last `/estimate` entry overrides any previous.
The `/spend` and `/estimate` commands can also be used independently of each other e.g tracking time without a formal estimation stage. With these two simple commands, you and your team have everything you need to get started estimating and track your time, all from within GitLab. You can read more about the exact specification in the [corresponding issue](https://gitlab.com/gitlab-org/gitlab-ee/issues/985), or in the [landing page](/features/time-tracking/).
The `/spend` and `/estimate` commands can also be used independently of each other e.g tracking time without a formal estimation stage. With these two simple commands, you and your team have everything you need to get started estimating and track your time, all from within GitLab. You can read more about the exact specification in the [corresponding issue](https://gitlab.com/gitlab-org/gitlab-ee/issues/985), or in the [landing page](/solutions/time-tracking/).
![time tracking example](images/blogimages/track-your-time-in-the-same-tool-you-do-your-work/time_tracking.png)
......
......@@ -67,7 +67,7 @@ for example between CI and the private container registry
To replicate the demo you need a private Openshift origin environment.
The [demo script](/handbook/sales/idea-to-production-demo/)
is public (along with the version numbers of OpenShift and Kubernetes we're using!) and the RedHat OpenShift template is linked from our
[installation page](/installation/).
[installation page](/install/).
We believe container schedulers such as Kubernetes are the future of
application lifecycle management and are working on Mesosphere support.
......
......@@ -397,7 +397,7 @@ file](http://doc.gitlab.com/omnibus/update/README.html).
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
## Updating
......
......@@ -476,7 +476,7 @@ file](https://docs.gitlab.com/omnibus/update/README.html).
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
## Updating
......
......@@ -381,7 +381,7 @@ file](http://doc.gitlab.com/omnibus/update/README.html).
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
## Updating
......
......@@ -74,4 +74,4 @@ prize winners, drawn at random, will be contacted in the weeks that follow.
## Questions? More info?
[GitLab team](/company/team/) members [@markglenfletcher](https://gitlab.com/markglenfletcher), [@ClemMakesApps](https://gitlab.com/ClemMakesApps), and the [core team](/core-team/) member [@haynes](https://gitlab.com/haynes) will be on hand to answer questions and close issues.
[GitLab team](/company/team/) members [@markglenfletcher](https://gitlab.com/markglenfletcher), [@ClemMakesApps](https://gitlab.com/ClemMakesApps), and the [core team](/community/core-team/) member [@haynes](https://gitlab.com/haynes) will be on hand to answer questions and close issues.
......@@ -38,7 +38,7 @@ In [8.0](/2015/09/22/gitlab-8-0-released/), we refreshed GitLab's look and feel,
In an effort to continue improving our UX, we now have a [research panel](/researchpanel) where you can help shape the future of GitLab! By joining our panel, you'll be the first to see new features and your thoughts will drive product improvements!
[Join our research panel](/researchpanel/){:.btn .btn-lg .btn-red .webcast-button}
[Join our research panel](/community/researchpanel/){:.btn .btn-lg .btn-red .webcast-button}
### Collaboration on Digital Work
......@@ -331,7 +331,7 @@ offer a disaster recovery solution built in GitLab and today we are introducing
a first step towards supporting this.
Since [GitLab 8.5](/2016/02/22/gitlab-8-5-released/),
GitLab ships with [Geo](/features/gitlab-geo/), a
GitLab ships with [Geo](/solutions/geo/), a
feature that lets you have one or more secondary instances that mirror your main
GitLab instance. Geo's primary goal was to drastically speed up cloning and
fetching projects over large distances. While Geo works really well for this
......@@ -686,7 +686,7 @@ Please check out the changelog to see all the named changes:
### Installing
If you are setting up a new GitLab installation please see the
[download GitLab page](/installation/).
[download GitLab page](/install/).
### Updating
......
......@@ -20,7 +20,7 @@ as [Technical Articles](https://docs.gitlab.com/ee/development/writing_documenta
You write, we publish, you earn up to USD 200 per article! 😃
Please check the [program webpage](/community-writers/) for a full overview, and the [terms and conditions](/community-writers/terms-and-conditions/) for all the details.
Please check the [program webpage](/community/writers/) for a full overview, and the [terms and conditions](/community/writers/terms-and-conditions/) for all the details.
## What has changed?
......@@ -81,6 +81,6 @@ We moved the most relevant issues from the [blog-post](https://gitlab.com/gitlab
Community writers who had already submitted their content through merge requests to the blog will be oriented to move their content to the documentation. Compensation offers will remain intact for these cases.
New content and new proposals submitted to us by prospect community writers are subjected to the [new rules](/community-writers/terms-and-conditions/).
New content and new proposals submitted to us by prospect community writers are subjected to the [new rules](/community/writers/terms-and-conditions/).
We apologize for the inconvenience caused by delays on reviews and feedback for your current proposals and articles. We wanted to improve the program to provide a better resource of technical content to our users and customers, and to offer you a better policy, as a community writer, before moving forward.