Commit f2bb476f authored by William Chia's avatar William Chia 🌴

Update links to pages

parent b0a7b784
Pipeline #33924781 passed with stages
in 27 minutes and 11 seconds
This diff is collapsed.
......@@ -31,7 +31,7 @@ Labels to use:
- `MktgOPS - On Hold`: Issue that is not within existing scope of Mktg OPS current targets, waiting on another team or department, any other blocker
- `MktgOPS - Planning`: Issue that does not directly fit into Mktg OPS focus and is being evaluated if it will replace
- `MktgOPS - In Process`: Issues that are not a top priority but have had worked started on them
- `MktgOPS - Top Priority`: Issue that is related to a breaking change, OKR focus, any other prioritized project by Mktg OPS leadership. This category will be limited because not everything can be a priority.
- `MktgOPS - Top Priority`: Issue that is related to a breaking change, OKR focus, any other prioritized project by Mktg OPS leadership. This category will be limited because not everything can be a priority.
- `MktgOPS - Complete`: Issue that involved operations and/or direct action item/tasks Mktg OPS is responsible for has been completed; issue that have been worked on and are done (should also be a closed issue)
Mktg OPS also has a [**Marketing only** issue board](https://gitlab.com/gitlab-com/marketing/general/boards/331422) that captures the items within the [general Marketing group](https://gitlab.com/gitlab-com/marketing/general), this board also uses the same global labels above.
......@@ -43,7 +43,7 @@ Mktg OPS also has a [**Marketing only** issue board](https://gitlab.com/gitlab-c
When creating a live or ondemand webcast it is important to integrate the event program across the platforms/programs used - GitLab Marketing site (`about.gitlab.com`), Marketo (Marketing Automation), Zoom (Webcast video software) and Salesforce (CRM). This provides transparency about the webcast to anyone with access to Salesforce, namely the Sales and Marketing teams.
For a comprehensive overview on how to set up a webcast, please visit the [Business Operations section](/handbook/business-ops#Webinars) of the handbook.
## Marketing Expense Tracking
| GL Code | Account Name | Purpose |
......@@ -69,7 +69,7 @@ Marketing Program Managers track costs associated with campaigns - such as event
**Things to Note:**
* All costs, including attendee travel expenses, must be tagged in order to capture the true cost of campaigns.
* All costs, including attendee travel expenses, must be tagged in order to capture the true cost of campaigns.
* Tagging expenses that are processed by Accounts Payable require Marketing to provide explicit instruction on when to apply tags, which should happen during the normal course of reviewing and approving vendor invoices.
* For expenses that are not campaign related, include a note to Accounts Payable clearly stating that campaigns are not applicable to the expense. This is required to ensure all campaign expenses are tagged.
......@@ -78,19 +78,19 @@ Marketing Program Managers track costs associated with campaigns - such as event
Email database management is a core responsibility for Mktg OPS. Ensuring GitLab is following email best practices, in compliance with Global spam laws and overall health of active database are all priorities.
Email creation, campaigns, follow up reporting and sending is the responsibility of the Marketing Program Managers. To request an email of any kind, please see the [instructions](/handbook/business-ops/#requesting-an-email) in the Business OPS section of the handbook.
Email creation, campaigns, follow up reporting and sending is the responsibility of the Marketing Program Managers. To request an email of any kind, please see the [instructions](/handbook/business-ops/#requesting-an-email) in the Business OPS section of the handbook.
### Email Communication Policy
At GitLab, we strive to communicate with people in a way that is beneficial to them, most of our email marketing communications follow an explicit opt-in policy, although at times, we will communicate via email to people who have not explicitly opted-in. We do this to offer something of value (ex. an invite to a workshop, dinner, the opportunity to meet an industry leader, etc. Not an email inviting you to read a blog post) to the person. We always include the unsubscribe link in our communications and we respect the unsubscribe list. In addition to the unsubscribe button at the bottom of all of our emails, we have available our [Email Subscription Center](https://page.gitlab.com/SubscriptionCenter.html), where people can control their email communication preferences. There are currently 4 [email segments](/handbook/marketing/marketing-sales-development/marketing-operations//#email-segments).
At GitLab, we strive to communicate with people in a way that is beneficial to them, most of our email marketing communications follow an explicit opt-in policy, although at times, we will communicate via email to people who have not explicitly opted-in. We do this to offer something of value (ex. an invite to a workshop, dinner, the opportunity to meet an industry leader, etc. Not an email inviting you to read a blog post) to the person. We always include the unsubscribe link in our communications and we respect the unsubscribe list. In addition to the unsubscribe button at the bottom of all of our emails, we have available our [Email Subscription Center](/company/preference-center/), where people can control their email communication preferences. There are currently 4 [email segments](/handbook/marketing/marketing-sales-development/marketing-operations//#email-segments).
### Email Segments
Database segments and how someone subscribes to specific segment:
- **Newsletter**: Users can subscribe to the newsletter through the blog, Contact Us page, and CE download page.
- **Security Alerts**: Subscribe on the GitLab [Contact Us page](/contact/)
- **Newsletter**: Users can [subscribe to the newsletter](/company/contact/) through the blog, Contact us page, and CE download page.
- **Security Alerts**: [Subscribe to security notices](/company/contact/#security-notices) on the GitLab Contact us page.
- **Webcasts**: When someone registers to a live or on-demand webcast
- **Live Events**: When someone registers to attend a live event, meet up or in-person training. Use of this segment is narrowed down by geolocation so notification and invitation emails are specific to related area.
......
......@@ -154,7 +154,7 @@ Want to know more about our free GitLab.com? /gitlab-com/
GitLab License FAQ - /products/
Questions?? - /contact/
Questions?? - /company/contact/
- After the video is done uploading, click "Video Manager" in the bottom right corner.
......
......@@ -31,13 +31,13 @@ The topics are ordered by priority in which they need to be tackled, and the mai
`@reseller` please complete the tasks below in the `Tasks for reseller` section as promptly as you can
`@partner marketing manager` please complete the tasks below in the `Tasks for Partner Marketing` section as promptly as you can
# Tasks for reseller: `@reseller`
# Tasks for reseller: `@reseller`
## Training
## Training
- [ ] Partner read [Reseller Handbook](/handbook/resellers/)
- [ ] `Technical Contact` completed reseller SE training
- [ ] `Technical Contact` completed reseller SE training
## General on-boarding - to be completed before we can accept an order
## General on-boarding - to be completed before we can accept an order
- [ ] GitLab@reseller.com email address set up
- [ ] All members of the reseller's gitlab team have a gitlab.com login
List them here:
......@@ -46,7 +46,7 @@ The topics are ordered by priority in which they need to be tackled, and the mai
* Technical Contact: (your consultant/SE and/or technical support person)
* Marketing Contact:
* Billing Contact: (To who's attention we should send invoices)
US ONLY - [ ] Uniform Sales and Use Tax Exemption Certificate completed and emailed to partners@ gitlab.com
## [Website Listing] (/resellers) - To be completed before we can list you on our website
......@@ -55,29 +55,29 @@ US ONLY - [ ] Uniform Sales and Use Tax Exemption Certificate completed and emai
- [ ] 250 character English Language Company overview added as a comment below
- [ ] 250 character Local Language Company overview added as a comment below
- [ ] Partner social media links added here:
* Twitter:
* Linked In:
* Facebook:
* You Tube:
* Twitter:
* Linked In:
* Facebook:
* You Tube:
* Google+:
* Other:
## Promotion - to be completed before we can announce you to our customer base
## Promotion - to be completed before we can announce you to our customer base
- [ ] `Partner` listed on /resellers (ie: complete the section above)
- [ ] Press release completed See: ***List issue here***
MARKET PARTNERS ONLY - [ ] Localised introduction email added to this issue
MARKET PARTNERS ONLY - [ ] Localised introduction email added to this issue
- [ ] Localised referral emails added to this issue [Example](/handbook/resellers/#lead-referral-and-follow-up for an example)
## Other
## Other
MARKET PARTNERS ONLY - [ ] Local TLD acquired
- [ ] Introduce your value to our blog readers per /handbook/marketing/blog/#team-members-posts
# Tasks for Partner Marketing (`@partner marketing manager`):
## General on-boarding
- [ ] GitLab@reseller email address added to [news@gitlab.com mailing list](/contact/)
# Tasks for Partner Marketing (`@partner marketing manager`):
## General on-boarding
- [ ] GitLab@reseller email address added to [news@gitlab.com mailing list](/company/contact/)
- [ ] Partner email address added to partner newsletter mail list
## Swag
## Swag
- [ ] Partner sent SWAG codes so their team can be outfitted in TanukiGear
- [ ] Partner sent Partner Swag Box so they have SWAG for their prospects
- [ ] Partner sent authorised reseller plaque engraved with their business name
......@@ -87,7 +87,7 @@ MARKET PARTNERS ONLY - [ ] Local TLD acquired
- [ ] BDR/Reseller introduction call completed
# Tasks for Channel Team: (`@Channel Partner Manager`)
## General on-boarding
## General on-boarding
- [ ] Add partner to [reseller spreadsheet](https://docs.google.com/spreadsheets/d/1tQjPMRUuzsDR4mNj74aY-W8jBQH4u9h7PpEsw088Zx0/edit#gid=1395032632)
- [ ] Welcome aboard email sent
- [ ] Partner Gitlab logins added to [resellers project] (https://gitlab.com/gitlab-com/resellers/)
......@@ -96,10 +96,10 @@ MARKET PARTNERS ONLY - [ ] Local TLD acquired
- [ ] Partner Demo License sent
- [ ] Partner announced during company call
- [ ] Partner guested at Sales Team call
- [ ] Bi-weekly call with partner set up
- [ ] Bi-weekly call with partner set up
- [ ] Added to Resellers Slack Channel `@gl-peopleopsgl-peopleops`
### SFDC
### SFDC
- [ ] Partner team members added to SFDC
- [ ] SFDC Communities enabled
- [ ] `SFDC URL for SFDC user` added to the Channel director's forecast rollup `@francisaquino`
......@@ -109,14 +109,14 @@ MARKET PARTNERS ONLY - [ ] Local TLD acquired
- [ ] Reports set up
## Promotion
## Promotion
- [ ] Partner.com/GitLab landing page reviewed `@marcia and/or local language speaker`
- [ ] Logo added to [GitLab website image repository](https://gitlab.com/gitlab-com/www-gitlab-com/source/images/resellers)
- [ ] Logo added to [GitLab website image repository](https://gitlab.com/gitlab-com/www-gitlab-com/source/images/resellers)
- [ ] Reseller listing added to data/resellers.yml
- [ ] Merge request added with graphic designer tagged to massage image if necessary *** Link MR here***
- [ ] Press Release Issue created ***Link issue here***
with the following tasks:
> - [ ] [Press release questionnaire] (https://docs.google.com/forms/d/1IBrpLR8BcLO1G9W-vvYSwdNmBNmbXW-mYeJlfx0iM9Y/viewform?edit_requested=true) completed by `@partner marketing contact`
> - [ ] Quote provided by `@partner manager`
> - [ ] Press release draft created by `@partner marketing manager`
......@@ -128,7 +128,7 @@ MARKET PARTNERS ONLY - [ ] Local TLD acquired
- [ ] Create issue for campaign to introduce reseller to all names in region ***link issue here***
## Training
## Training
- [ ] `Technical Contact` invited to next reseller SE training `@xiaogang_gitlab`
......
......@@ -21,7 +21,7 @@
%ul.animated.footer-links
%li= link_to('All resources', '/resources/', :class => 'footer-nav-link')
%li= link_to('Blog', '/blog/', :class => 'footer-nav-link')
%li= link_to('Newsletter', '/contact/', :class => 'footer-nav-link')
%li= link_to('Newsletter', '/company/contact/', :class => 'footer-nav-link')
%li= link_to('Events', '/events/', :class => 'footer-nav-link')
%li= link_to('Training', '/training/', :class => 'footer-nav-link')
%li= link_to('Docs', 'https://docs.gitlab.com/', :class => 'footer-nav-link')
......@@ -56,7 +56,7 @@
%li= link_to('Team', '/team/', :class => 'footer-nav-link')
%li= link_to('Analyst Relations', '/analysts/', :class => 'footer-nav-link')
%li= link_to('Security', '/security/', :class => 'footer-nav-link')
%li= link_to('Contact', '/contact/', :class => 'footer-nav-link')
%li= link_to('Contact', '/company/contact/', :class => 'footer-nav-link')
%li= link_to('Handbook', '/handbook/', :class => 'footer-nav-link')
%li= link_to('Strategy', '/company/strategy/', :class => 'footer-nav-link')
%li= link_to('Terms', '/terms/', :class => 'footer-nav-link')
......
......@@ -13,7 +13,7 @@
%a.main-nav-link{href: "/resources/"} Resources
.dropdown
%a.main-nav-sub-link{href: "/blog/"} Blog
%a.main-nav-sub-link{href: "/contact/"} Newsletter
%a.main-nav-sub-link{href: "/company/contact/"} Newsletter
%a.main-nav-sub-link{href: "/events/"} Events
%a.main-nav-sub-link{href: "/training/"} Training
%a.main-nav-sub-link{href: "https://docs.gitlab.com/"} Docs
......
......@@ -44,7 +44,7 @@
4. Set up your communication preferences
%p
Visit our
%a{ href:"/preference-center/" }email subscription preference center
%a{ href:"/company/preference-center/" }email subscription preference center
to let us know when to communicate with you. We have an explicit email opt-in policy so you have complete control over what and how often we send you emails.
%p
Twice a month, we send out the GitLab news you need to know, including new features, integrations, docs, and behind the scenes stories from our dev teams. For critical security updates related to bugs and system performance, sign up for our dedicated security newsletter.
......
......@@ -5,8 +5,8 @@ title: Licensing and subscription FAQ
### How do I purchase a license?
You can purchase a license for GitLab Enterprise Edition (self-hosted) or for
GitLab.com (hosted by GitLab) on our [Customer Portal](https://customers.gitlab.com/)
You can purchase a license for GitLab Enterprise Edition (self-hosted) or for
GitLab.com (hosted by GitLab) on our [Customer Portal](https://customers.gitlab.com/)
with a credit card.
### How do I renew my license?
......@@ -23,68 +23,68 @@ with a credit card.
### What does "users over license" mean?
If you've added more users to your GitLab EE instance during the past period
than you were licensed for, we need to add these additional users to your
subscription.
If you've added more users to your GitLab EE instance during the past period
than you were licensed for, we need to add these additional users to your
subscription.
Without adding these users during the renewal process, your license key will
Without adding these users during the renewal process, your license key will
not work.
You can find the number of *users over license* by going to the `/admin`
section of your GitLab instance (e.g. `https://example.gitlab.com/admin`). This
can also be found by clicking the *admin wrench* in the navbar of your instance
You can find the number of *users over license* by going to the `/admin`
section of your GitLab instance (e.g. `https://example.gitlab.com/admin`). This
can also be found by clicking the *admin wrench* in the navbar of your instance
when logged in as an admin.
In the top right section of the admin dashboard, you should see the number to
In the top right section of the admin dashboard, you should see the number to
enter when asked this during the renewal process.
### Who gets counted in the subscription?
Every person with a GitLab account on the instance is a user and is counted
in the subscription. Only _active_ users count towards total user count.
Every person with a GitLab account on the instance is a user and is counted
in the subscription. Only _active_ users count towards total user count.
Blocked users do not count, nor do Guest users in an Ultimate license.
For more detail, administrators can find user counts under the
**Admin wrench** > **Users**. The Active Users tab indicates the users currently
For more detail, administrators can find user counts under the
**Admin wrench** > **Users**. The Active Users tab indicates the users currently
counted.
### Can I get a trial?
It is possible to obtain a free evaluation license of our enterprise edition for
a 30 day period for up to 100 users. Please visit our
[free trial page](https://about.gitlab.com/free-trial/) to sign up.
a 30 day period for up to 100 users. Please visit our
[free trial page](/free-trial/) to sign up.
When you decide to purchase a subscription, you will be issued a new license
key. Should you not take out a subscription, your key will expire at the end
When you decide to purchase a subscription, you will be issued a new license
key. Should you not take out a subscription, your key will expire at the end
of your evaluation period.
### Can I use my paid seats on a new set of users?
The seats for your license are generic and are not specific to a user. GitLab does
not use a named license model.
not use a named license model.
The seats you buy can be distributed however you choose. If a user leaves your
organization, you can remove or block that user to free the seat. This seat can
The seats you buy can be distributed however you choose. If a user leaves your
organization, you can remove or block that user to free the seat. This seat can
then be used by another user.
If the additional user is added before the previous seat is blocked, note that
If the additional user is added before the previous seat is blocked, note that
this may result in a user over license if your maximum users has been reached.
### Can I add more users to my subscription?
Yes. You can add users to your subscription any time during the subscription period.
Yes. You can add users to your subscription any time during the subscription period.
You can log in to your account via the
[GitLab Customer Portal](https://customers.gitlab.com) and add more seats or via our
[Contact Us](https://about.gitlab.com/contact/) page.
[GitLab Customer Portal](https://customers.gitlab.com) and add more seats or via our
[Contact Us](/company/contact/) page.
In either case,
the cost will be prorated from the date of quote/purchase through the end end of
the subscription period. You may also add users and pay for the users over
the cost will be prorated from the date of quote/purchase through the end end of
the subscription period. You may also add users and pay for the users over
license at renewal.
If you're using GitLab.com:
* Simply add more users to the GitLab.com group you've assigned your plan to.
* Simply add more users to the GitLab.com group you've assigned your plan to.
New users added to your group's plan will be automatically charged a pro-rated amount.
If you've subscribed to a self-hosted plan:
......@@ -122,10 +122,10 @@ downgrade to GitLab Community Edition, which is free to use.
On GitLab.com, you can purchase a plan either for your personal account or for a group.
* Group Plans (recommended) apply to all projects stored under a particular group on GitLab.com
* Personal Plans applies to all personal projects that are stored under your username.
### How do I purchase a Group Plan on GitLab.com?
You can use GitLab's Customer Portal at https://customers.gitlab.com. Note that
You can use GitLab's Customer Portal at https://customers.gitlab.com. Note that
you must create the group before purchasing the plan.
1. Create a group on GitLab.com
......@@ -140,12 +140,12 @@ Please submit your request to support@gitlab.com.
### Do you support resellers?
We don't currently support reseller purchasing via the portal. If you are a
reseller looking to purchase GitLab on behalf of your client, please get in
touch with us using the [Contact Us sales form](https://about.gitlab.com/sales/).
If you include your billing contact name and email, your physical billing
address, and the end customer's name, email address and shipping address, we
will send you (not your customer) a resellers quote which you can execute
either with a credit card or an EFT.
We don't currently support reseller purchasing via the portal. If you are a
reseller looking to purchase GitLab on behalf of your client, please get in
touch with us using the [Contact sales form](/sales/).
If you include your billing contact name and email, your physical billing
address, and the end customer's name, email address and shipping address, we
will send you (not your customer) a resellers quote which you can execute
either with a credit card or an EFT.
You can find details on our reseller program at https://about.gitlab.com/resellers/program.
......@@ -4,7 +4,7 @@ date: March 26, 2014
author: Jacob Vosmaer
categories: releases
---
Today we announce the release of [GitLab Enterprise Edition](/gitlab-ee/) 6.7.0.
Today we announce the release of [GitLab Enterprise Edition](/gitlab-ee/) 6.7.0.
GitLab is an open source code hosting and project managament application.
In addition to the [improvements in GitLab Community Edition 6.7](/2014/03/21/gitlab-6-dot-7-released/), GitLab Enterprise Edition 6.7.0 contains the following improvements.
......@@ -19,7 +19,7 @@ In GitLab EE 6.7 we have added the following rules:
[![screenshot](/images/6_7_ee/git_hooks.png)](/images/6_7_ee/git_hooks.png)
Please [contact us](https://www.gitlab.com/contact/) if you have a need for different hooks.
Please [contact us](/company/contact/) if you have a need for different hooks.
### LDAP Improvements
......
......@@ -17,4 +17,4 @@ In the coming months GitLab will add more features to GitHost, for example, it w
"I'm happy to find a great home for GitHost under the expertise of the GitLab B.V. team." says GitHost founder, Josh Frye.
Please [contact GitLab](/contact/) if you have any questions.
Please [contact GitLab](/company/contact/) if you have any questions.
......@@ -11,7 +11,7 @@ We held our first webcast last week, and we’re so delighted you came along. We
It was excellent to see so many questions from the audience.
It gave us ideas for future webcasts too, so keep the feedback coming!
Sign up to our [newsletter](/contact/#newsletter) to find out about the next one.
Sign up to our [newsletter](/company/contact/#newsletter) to find out about the next one.
<!-- more -->
......
......@@ -14,7 +14,7 @@ This was a really feature-packed release.
This highlighted some of the new features in the context of collaboration.
If you're brand new to GitLab this is a quick introduction to how it works.
Sign up to our [newsletter](/contact/#newsletter)
Sign up to our [newsletter](/company/contact/#newsletter)
to find out about the next screencast!
<!-- more -->
......
......@@ -13,12 +13,12 @@ early, improving discoverability, and keeping your momentum going.
[Job](http://twitter.com/jobvo) showed how he starts his day, checking his todo list,
providing feedback on issues, line-by-line code review, and getting to work on his
own commits.
own commits.
This demo is based on [GitLab Flow](http://doc.gitlab.com/ee/workflow/gitlab_flow.html)
which is lightweight and scales easily for even large teams.
which is lightweight and scales easily for even large teams.
Watch the recording below.
Sign up to our [newsletter](/contact/#newsletter)
Sign up to our [newsletter](/company/contact/#newsletter)
so you don't miss our webcasts!
<!-- more -->
......@@ -49,7 +49,7 @@ In our next webcast on March 24th, we'll take a look at the new features in GitL
- Time: 5pm (17:00) UTC; 12pm EST; 9am PST
- [Register here][webcast1]
In the following webcast, we'll focus entirely on GitLab CI.
In the following webcast, we'll focus entirely on GitLab CI.
- Date: Thursday, April 14, 2016
- Time: 5pm (17:00) UTC; 12pm EST; 9am PST
......
......@@ -51,7 +51,7 @@ integration in GitLab. Join the GitLab CI team for this introduction!
Can't make it? Register anyway, and we'll send you a link to watch it later.
[newsletter]: /contact/#newsletter
[newsletter]: /company/contact/#newsletter
[webcast]: http://page.gitlab.com/apr-2016-gitlab-intro-ci-webcast.html
[Douwe]: https://twitter.com/DouweM
[releasenotes]: /2016/03/22/gitlab-8-6-released/
......@@ -69,5 +69,5 @@ See you there!
[blog-ios]: /2016/03/10/setting-up-gitlab-ci-for-ios-projects/
[blog-runner]: /2016/03/01/gitlab-runner-with-docker/
[ci-docs]: http://doc.gitlab.com/ce/ci/
[newsletter]: /contact/#newsletter
[newsletter]: /company/contact/#newsletter
[webcast]: http://page.gitlab.com/apr-2016-gitlab-intro-ci-webcast.html
......@@ -7,18 +7,18 @@ categories: company
image_title: '/images/unsplash/stars.png'
---
In this webcast, the GitLab CI team walked us through GitLab's built-in Continuous Integration.
The team also gave two demos to allow you to see CI in action.
In this webcast, the GitLab CI team walked us through GitLab's built-in Continuous Integration.
The team also gave two demos to allow you to see CI in action.
Here's a quick look at what was covered in the webcast.
Here's a quick look at what was covered in the webcast.
- GitLab CI overview
- How GitLab CI works
- Live demos:
- GitLab CI overview
- How GitLab CI works
- Live demos:
* Configuring CI for testing

* Configuring a Specific Runner
- Review your work in CI
- Roadmap
* Configuring a Specific Runner
- Review your work in CI
- Roadmap
<!-- more -->
......@@ -41,6 +41,6 @@ We've posted some great tutorials recently, check them out if you've missed them
- [Setting up GitLab CI for iOS projects](/2016/03/01/gitlab-runner-with-docker/)
## Stay tuned for future webcasts
## Stay tuned for future webcasts
Subscribe to our [newsletter](/contact/#newsletter) to make sure you don't miss any of our live webcasts.
\ No newline at end of file
Subscribe to our [newsletter](/company/contact/#newsletter) to make sure you don't miss any of our live webcasts.
\ No newline at end of file
......@@ -16,6 +16,6 @@ immediately. Please forward this alert to the appropriate people at your
organization and have them subscribe to [Security Notices].
[our blog]: /blog
[Security Notices]: /contact/
[Security Notices]: /company/contact/
<!-- more -->
......@@ -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
......
......@@ -175,7 +175,7 @@ and understanding. We will continue to be vigilant about security issues
within GitLab.
If you have not already, please sign up on for future [security
notices](/contact/) on this page.
notices](/company/contact/) on this page.
## Join us on July 27th for our joint webcast with Yubico
......
......@@ -80,7 +80,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/#security-notices).
## Enterprise Edition
......
......@@ -54,7 +54,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/#security-notices).
## Enterprise Edition
......
......@@ -121,7 +121,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/#security-notices).
## Enterprise Edition
......
......@@ -16,6 +16,6 @@ immediately. Please forward this alert to the appropriate people at your
organization and have them subscribe to [Security Notices].
[our blog]: /blog
[Security Notices]: /contact/
[Security Notices]: /company/contact/#security-notices
<!-- more -->
......@@ -17,6 +17,6 @@ immediately. Please forward this alert to the appropriate people at your
organization and have them subscribe to [Security Notices].
[our blog]: /blog
[Security Notices]: /contact/
[Security Notices]: /company/contact/#security-notices
<!-- more -->
......@@ -16,6 +16,6 @@ immediately. Please forward this alert to the appropriate people at your
organization and have them subscribe to [Security Notices].
[our blog]: /blog
[Security Notices]: /contact/
[Security Notices]: /company/contact/#security-notices
<!-- more -->
......@@ -16,6 +16,6 @@ immediately. Please forward this alert to the appropriate people at your
organization and have them subscribe to [Security Notices].
[our blog]: /blog
[Security Notices]: /contact/
[Security Notices]: /company/contact/#security-notices
<!-- more -->
......@@ -20,6 +20,6 @@ release time used for previous critical security releases. This change will be
explained in the release blog post.
[our blog]: /blog
[Security Notices]: /contact/
[Security Notices]: /company/contact/#security-notices
<!-- more -->
......@@ -16,6 +16,6 @@ immediately. Please forward this alert to the appropriate people at your
organization and have them subscribe to [Security Notices].
[our blog]: /blog
[Security Notices]: /contact/
[Security Notices]: /company/contact/#security-notices
<!-- more -->
......@@ -15,6 +15,6 @@ immediately. Please forward this alert to the appropriate people at your
organization and have them subscribe to [Security Notices].
[our blog]: /blog
[Security Notices]: /contact/
[Security Notices]: /company/contact/#security-notices
<!-- more -->
......@@ -10,26 +10,26 @@ tags: security
We are focused on improving our security posture at GitLab and are always working to evolve our security processes. Part of that evolution is the incorporation of stronger cryptographic standards into our environment, and the deprecation of those that have been rendered out-dated or proven to be prone-to-attacks. In an effort to continue to raise that bar, we are announcing our plan to discontinue support for Transport Layer Security (TLS) 1.0 and 1.1 on GitLab.com and in our GitLab API by December 15, 2018. To that end, we have published this [public issue](https://gitlab.com/gitlab-com/security/issues/202) that will be used to track progress of this initiative and provide updates to the GitLab community.
Currently, GitLab.com supports TLS 1.0 and TLS 1.1. There have been many serious security issues reported with TLS 1.0 and TLS 1.1, including but not limited to [Heartbleed](http://heartbleed.com/).
Currently, GitLab.com supports TLS 1.0 and TLS 1.1. There have been many serious security issues reported with TLS 1.0 and TLS 1.1, including but not limited to [Heartbleed](http://heartbleed.com/).
In addition, from a security compliance standpoint, the Payment Card Industry (PCI) DSS 3.1 standard mandates the migration away from these weaker cryptographic standards. This mandate is to exclude Secure Sockets Layer (SSL) 3.0, TLS 1.0, and some ciphers supported by TLS 1.1 from protocols supporting strong cryptography.
In addition, from a security compliance standpoint, the Payment Card Industry (PCI) DSS 3.1 standard mandates the migration away from these weaker cryptographic standards. This mandate is to exclude Secure Sockets Layer (SSL) 3.0, TLS 1.0, and some ciphers supported by TLS 1.1 from protocols supporting strong cryptography.
Our intent in making this announcement and creating the [public issue](https://gitlab.com/gitlab-com/security/issues/202) is to minimize any potential operational disruptions to GitLab.com customers while deprecating TLS 1.0 and TLS 1.1. This post is the first of three that we will publish during this interim period prior to disabling support for TLS 1.0 and 1.1 on December 15th, 2018.
As always, we will continue to monitor TLS 1.0 and 1.1 vulnerabilities and will adapt our timeline as required to mitigate protocol-level issues if they arise. In addition to the monthly blog posts on the status of this initiative, updates to timelines will be posted to our Twitter feed and tracked in [public issues](https://gitlab.com/gitlab-com/security/issues/202). Additionally, GitLab.com users who have opted to receive [security alert emails](/preference-center/) from GitLab will receive status updates regarding the this deprecation process.
As always, we will continue to monitor TLS 1.0 and 1.1 vulnerabilities and will adapt our timeline as required to mitigate protocol-level issues if they arise. In addition to the monthly blog posts on the status of this initiative, updates to timelines will be posted to our Twitter feed and tracked in [public issues](https://gitlab.com/gitlab-com/security/issues/202). Additionally, GitLab.com users who have opted to receive [security alert emails](/company/preference-center/) from GitLab will receive status updates regarding the this deprecation process.
If you have any questions, please reach out to the Security team by emailing security@gitlab.com
## Identified client incompatibilities
The majority of traffic should be unaffected by the deprecation of support for versions 1.0 and 1.1. Currently, the nof requests to GitLab.com are using up-to-date clients with support for TLS1.2. Whereas there are a few remaining clients that we believe will be affected (see below) most of these can be updated to work with TLS 1.2.
The majority of traffic should be unaffected by the deprecation of support for versions 1.0 and 1.1. Currently, the nof requests to GitLab.com are using up-to-date clients with support for TLS1.2. Whereas there are a few remaining clients that we believe will be affected (see below) most of these can be updated to work with TLS 1.2.
### Git-Credential-Manager-for-Windows prior to 1.14.0
Versions prior to 1.14.0 of Git-Credential-Manager-for-Windows do not support TLSv1.2. This can be addressed by updating to v1.14.0.
### Git on Red Hat 5, < 6.8, and < 7.2
Users running Red Hat 5 are advised to upgrade to a newer version of the operating system as Red Hat does not have a point release planned for 5 that supports TLS 1.2. Git clients shipped with Red Hat 6 and 7 did not support TLSv1.2, which can be remediated by updating to versions 6.8 and 7.2 respectively.
Users running Red Hat 5 are advised to upgrade to a newer version of the operating system as Red Hat does not have a point release planned for 5 that supports TLS 1.2. Git clients shipped with Red Hat 6 and 7 did not support TLSv1.2, which can be remediated by updating to versions 6.8 and 7.2 respectively.
### JGit / Java releases < JDK 8
Versions of the JDK 6 and prior do not support TLSv1.2. We advise users of JDK <= 6 to upgrade to a newer version of the JDK.
### Visual Studio
The latest version of Visual Studio 2017 supports TLSv1.2. Users not running the latest version are advised to upgrade.
\ No newline at end of file
The latest version of Visual Studio 2017 supports TLSv1.2. Users not running the latest version are advised to upgrade.
\ No newline at end of file
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment