Commit 22061ebb authored by Emily's avatar Emily
Browse files

Merge branch 'master' into 'patch-449'

# Conflicts:
#   data/events.yml
parents 88ff2c65 69a8d85a
Pipeline #12505961 passed with stages
in 11 minutes and 24 seconds
......@@ -342,13 +342,13 @@
social_tags: LISA17
event_url: https://www.usenix.org/conference/lisa17
- topic: Django Girls Koforidua
- topic: Django Girls Florianópolis
type: Diversity
date: November 10, 2017
date_ends: November 10, 2017
location: Linda Dor Plaza in Koforidua. Ghana
date: November 11, 2017
date_ends: November 11, 2017
location: Brazil - SC - Florianópolis - Technology College SENAI - Saco Grande SC-401 3730
social_tags: GitLabDiversity
event_url: https://djangogirls.org/koforidua/
event_url: https://djangogirls.org/florianopolis/
- topic: Rails Girls POA 2017
type: Diversity
......@@ -367,6 +367,14 @@
location: Las Vegas, NV USA
social_tags: AWSreinvent
event_url: https://reinvent.awsevents.com/
- topic: Django Girls Milano
type: Diversity
date: December 2, 2017
date_ends: December 2, 2017
location: Milano, Italy
social_tags: GitLabDiversity
event_url: https://twitter.com/djangogirlsIT
 
- topic: North Bay Python
type: Diversity
......
......@@ -3,42 +3,64 @@ solutions:
# The first solutions are phases of the software development life-cycle
# To add more, check the documentation:
# https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/doc/features.md#create-or-update-the-solutions-pages-under-solutions
idea:
display_name: "Idea"
description: "Conversational Development is fueled with open, seamless chat. With deep Mattermost integration, GitLab helps you go from idea to production in the quickest possible way."
body: ""
define:
display_name: "Define"
description: "Tracking requirements and tasks is core to the software development lifecycle."
body: ""
related:
- "plan"
- "idea"
# https://en.wikipedia.org/wiki/DevOps_toolchain
# Contained in Plan
#idea:
#display_name: "Idea"
#description: "Conversational Development is fueled with open, seamless chat. With deep Mattermost integration, GitLab helps you go from idea to production in the quickest possible way."
#body: ""
#define:
#display_name: "Define"
#description: "Tracking requirements and tasks is core to the software development lifecycle."
#body: ""
#related:
#- "plan"
#- "idea"
plan:
display_name: "Plan"
description: "Regardless of your process, GitLab provides powerful planning
tools to keep everyone synchronized."
body: ""
related:
- "idea"
- "create"
create:
display_name: "Create"
description: "Create, view, and manage code and project data through powerful branching tools."
body: ""
related:
- "idea"
review:
display_name: "Review"
description: "Powerful code review and workflow tools help you ship quality software, faster."
- "plan"
- "verify"
# Replaced with verify
#review:
#display_name: "Review"
#description: "Powerful code review and workflow tools help you ship quality software, faster."
#body: ""
#related:
#- "plan"
verify:
display_name: "Verify"
description: ""
body: ""
related:
- "plan"
- "create"
packaging:
display_name: "Packaging"
description: ""
body: ""
release:
display_name: "Release"
description: "GitLab's integrated CI & CD allows you to ship code quickly, be it on one -or one thousand servers."
body: ""
related:
- "monitor"
- "configure"
configure:
display_name: "Configure"
description: ""
body: ""
related:
- "configure"
monitor:
display_name: "Monitor"
description: "Automatically monitor metrics so you know how any change in code
......
......@@ -1165,7 +1165,7 @@
- name: Alex Hanselka
locality: Austin, TX
country: USA
role: <a href="https://about.gitlab.com/jobs/production-engineer/">Junior Production Engineer</a>
role: <a href="https://about.gitlab.com/jobs/production-engineer/">Production Engineer</a>
reports_to: Director of Infrastructure
picture: alex.jpg
twitter: purrdeta
......
......@@ -169,7 +169,7 @@ members:
* UTC: <span id="apac-UTC"></span>
* <span id="apac-abbr"></span>: <span id="apac-USER"></span>
1. Everyone at GitLab is invited to the team call.
1. There is an additional makeup team call on Fridays where anyone who missed their weekend update can share what they have been up to. Optionally, team members can share an update if they feel so inclined. Please add your name to the list for that day.
1. There is an additional makeup team call on Fridays where anyone who missed their weekend update can share what they have been up to. Optionally, team members can share an update if they feel so inclined. Please add your name to the list for that day.
1. We also have a team call for GitLabbers in the APAC region to share their weekend update. This call will also be recorded so the rest of the team can see what their colleagues have been up to! Everyone is encouraged to join this call as well, but it is not mandatory.
1. Every last Friday of the month we have an AMA to talk about anything our team is thinking about.
1. We use [Zoom](https://zoom.us) for the call since Google Hangouts is capped at 15 people (please be sure to mute your microphone). The link is in the calendar invite and also listed at the top of the team agenda Google Doc called _Team Agenda_.
......@@ -267,6 +267,7 @@ doesn't unnecessarily appear on other people's calendars.
1. We use Unix style (lf) line endings, not Windows style (crlf), please ensure `*.md text eol=lf` is set in the repository's `.gitattributes` and run `git config --global core.autocrlf input` on your client.
1. Do not create links like "here" or "click here". All links should have relevant anchor text that describes what they link to, such as: "GitLab CI source installation documentation".
1. Always use [ISO dates](https://en.wikipedia.org/wiki/ISO_8601#Calendar_dates) in all writing and legal documents since other formats [lead to online confusion](http://xkcd.com/1179/), so use `yyyy-mm-dd`, for example 2015-04-13, and never 04-13-2015, 13-04-2015, nor 2015/04/13.
1. For engineering (for example production postmortems) we use UTC as the timezone. For all other uses we use Pacific time since we are a San Francisco based company. Please refer to time as '9:00 Pacific' and not PST since that is ambiguous during daylight savings.
1. If you have multiple points in a comment or email, please number them to make replies easier.
1. When you reference an issue, merge request, comment, commit, page, doc, etc. and you have the URL available please paste that in.
1. In making URLs, always prefer hyphens to underscores, and always use lowercase.
......
......@@ -9,42 +9,41 @@ title: "Solutions Architect Onboarding"
 
**Week 1**
 
**Regular Onboarding Duties**
https://about.gitlab.com/handbook/general-onboarding/
**Regular Onboarding Duties**
[General Onboarding](https://about.gitlab.com/handbook/general-onboarding/)
**Week 2 Technical Onboarding**
Download Git https://docs.gitlab.com/ce/gitlab-basics/start-using-git.html
[Download Git](https://docs.gitlab.com/ce/gitlab-basics/start-using-git.html)
Stage 1: Become familiar with git and GitLab basics
 
Cover the Beginner and Intermediate sections (and a few Advanced) in the GitLab University (https://university.gitlab.com/):
Under the topic of Git
* About Version Control (https://docs.google.com/presentation/d/16sX7hUrCZyOFbpvnrAFrg6tVO5_yT98IgdAqOmXwBho/edit#slide=id.gd69537a19_0_14)
* Try Git (https://www.codeschool.com/account/courses/try-git)
* Under the topic of GitLab Basics
* All the GitLab Basics (http://docs.gitlab.com/ce/gitlab-basics/README.html) that you don't feel comfortable with. If you get stuck, see the linked videos under GLB in GitLab University
* GitLab Flow (https://www.youtube.com/watch?v=UGotqAUACZA)
* Take a look at how the different GitLab versions compare (https://about.gitlab.com/features/#compare)
* Any of these that you don't feel comfortable with in the user training (https://gitlab.com/gitlab-org/University/tree/master/training) we use for our customers.
Cover the Beginner and Intermediate sections (and a few Advanced) in [GitLab University](https://university.gitlab.com/):
Under the topic of Git:
* [About Version Control](https://docs.google.com/presentation/d/16sX7hUrCZyOFbpvnrAFrg6tVO5_yT98IgdAqOmXwBho/edit#slide=id.gd69537a19_0_14)
* [Try Git](https://www.codeschool.com/account/courses/try-git)
* Under the topic of GitLab Basics:
* All the [GitLab Basics](http://docs.gitlab.com/ce/gitlab-basics/README.html) that you don't feel comfortable with. If you get stuck, see the linked videos under GLB in GitLab University
* [GitLab Flow](https://www.youtube.com/watch?v=UGotqAUACZA)
* Take a look at how the different [GitLab versions compare](https://about.gitlab.com/features/#compare)
* Any of these that you don't feel comfortable with in the [user training](https://gitlab.com/gitlab-org/University/tree/master/training) we use for our customers.
- `env_setup.md`
-`feature_branching.md`
- `feature_branching.md`
- `explore_gitlab.md`
-`stash.md`
- `stash.md`
- `git_log.md`
* For the rest of the topics in `user training`, just do a quick read over the file names so you start remembering where to find them.
* Get familiar with the services GitLab offers
- The differences between [CE and EE](https://about.gitlab.com/pricing/)
- GitHost (https://about.gitlab.com/gitlab-hosted/)
- Read through the GitHost documentation (https://dev.gitlab.org/gitlab/GitHost/blob/master/doc/README.md)
- [GitHost](https://about.gitlab.com/gitlab-hosted/)
- Read through the [GitHost documentation](https://dev.gitlab.org/gitlab/GitHost/blob/master/doc/README.md)
 
Perform each of the following Installation Methods (https://about.gitlab.com/installation/) on your preferred test environment you chose above:
Perform each of the following [Installation Methods](https://about.gitlab.com/installation/) on your preferred test environment you chose above:
* Install via [Omnibus](https://gitlab.com/gitlab-org/omnibus-gitlab/)
* Populate with some test data: User account, Project, Issue
* Backup using our Backup rake task
(http://docs.gitlab.com/ce/raketasks/backup_restore.html#create-a-backup-of-the-gitlab-system)
* Backup using our [Backup rake task](http://docs.gitlab.com/ce/raketasks/backup_restore.html#create-a-backup-of-the-gitlab-system)
* Install via [Docker](https://gitlab.com/gitlab-org/gitlab-ce/tree/master/docker)
* Restore backup to your Docker VM using our Restore rake task (http://docs.gitlab.com/ce/raketasks/backup_restore.html#restore-a-previously-created-backup)
* Restore backup to your Docker VM using our [Restore rake task](http://docs.gitlab.com/ce/raketasks/backup_restore.html#restore-a-previously-created-backup)
 
Getting to know GitLab Support
* Pair with a support team member
......@@ -58,29 +57,28 @@ Complete Zendesk Agent training (allow 40 minutes for completion)
- You'll receive an email with information on accessing the Zendesk course
- Proceed to complete the **"Agents: Zendesk Fundamentals Online"** course
- Review additional Zendesk resources
- UI Overview (https://support.zendesk.com/hc/en-us/articles/203661806-Introduction-to-the-Zendesk-agent-
interface)
- Updating Tickets (https://support.zendesk.com/hc/en-us/articles/212530318-Updating-and-solving-tickets)
- Working w/ Tickets (https://support.zendesk.com/hc/en-us/articles/203690856-Working-with-tickets) *Read: avoiding agent collision.*
* Dive into our ZenDesk support process by reading how to handle tickets (https://about.gitlab.com/handbook/support/onboarding/#handling-tickets)
* Learn about the tiered support system (https://about.gitlab.com/handbook/support/#tiered-support)
* Read about Escalation (https://about.gitlab.com/handbook/support/onboarding/#create-issues)
* Take a look at the GitLab.com Team page (https://about.gitlab.com/team/) to find the resident experts in their fields
* Understand what's in the pipeline and proposed features at GitLab: Direction Page (https://about.gitlab.com/direction/)
* Practice searching issues and filtering using labels (https://gitlab.com/gitlab-org/gitlab-ce/labels) to find existing feature proposals and bugs
- [UI Overview](https://support.zendesk.com/hc/en-us/articles/203661806-Introduction-to-the-Zendesk-agent-interface)
- [Updating Tickets](https://support.zendesk.com/hc/en-us/articles/212530318-Updating-and-solving-tickets)
- [Working with Tickets](https://support.zendesk.com/hc/en-us/articles/203690856-Working-with-tickets) *Read: avoiding agent collision.*
* Dive into our ZenDesk support process by reading [how to handle tickets](https://about.gitlab.com/handbook/support/onboarding/#handling-tickets)
* Learn about the [tiered support system](https://about.gitlab.com/handbook/support/#tiered-support)
* Read about [Escalation](https://about.gitlab.com/handbook/support/onboarding/#create-issues)
* Take a look at the GitLab.com [Team page](https://about.gitlab.com/team/) to find the resident experts in their fields
* Understand what's in the pipeline and proposed features at GitLab's [Direction Page](https://about.gitlab.com/direction/)
* Practice searching issues and filtering using [labels](https://gitlab.com/gitlab-org/gitlab-ce/labels) to find existing feature proposals and bugs
* If raising a new issue always provide a relevant label and a link to the relevant ticket in Zendesk
* Take a look at the existing issue templates (https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#issue-tracker) to see what is expected
* Environment Information and maintenance checks (http://docs.gitlab.com/ce/raketasks/maintenance.html)
* GitLab check (http://docs.gitlab.com/ce/raketasks/check.html)
* Take a look at the existing [issue templates](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#issue-tracker) to see what is expected
* Environment Information and [maintenance checks](http://docs.gitlab.com/ce/raketasks/maintenance.html)
* [GitLab check](http://docs.gitlab.com/ce/raketasks/check.html)
* Omnibus commands
* Status (https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/maintenance/README.md#get-service-status)
* Starting and stopping services (https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/maintenance/README.md#starting-and-stopping)
* [Status](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/maintenance/README.md#get-service-status)
* [Starting and stopping services](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/maintenance/README.md#starting-and-stopping)
 
* Starting a rails console (https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/maintenance/README.md#invoking-rake-tasks)
* Get to know the GitLab API (https://docs.gitlab.com/ee/api/README.html), its capabilities and shortcomings
* Learn how to migrate from SVN to Git (https://docs.gitlab.com/ee/workflow/importing/migrating_from_svn.html)
* Set up GitLab CI (https://docs.gitlab.com/ee/ci/quick_start/README.html)
* Starting a [rails console](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/maintenance/README.md#invoking-rake-tasks)
* Get to know the [GitLab API](https://docs.gitlab.com/ee/api/README.html), its capabilities and shortcomings
* Learn how to [migrate from SVN to Git](https://docs.gitlab.com/ee/workflow/importing/migrating_from_svn.html)
* Set up [GitLab CI](https://docs.gitlab.com/ee/ci/quick_start/README.html)
 
**Self assessments**
* [General SCM/Git knowledge and DevOps](https://goo.gl/forms/BjNezQx487d7uFpz2)
......@@ -89,13 +87,13 @@ Complete Zendesk Agent training (allow 40 minutes for completion)
 
**Week 3-4**
 
* GitLab Workflow (https://about.gitlab.com/2016/10/25/gitlab-workflow-an-overview/)
* Latest Version released features (https://about.gitlab.com/2017/06/07/gitlab-9-dot-2-dot-5-security-release/#)
* GitLab Products (https://about.gitlab.com/products/)
* Future Releases (https://about.gitlab.com/direction/#future-releases)
* Know EE features for upgrade from CE (https://about.gitlab.com/comparison/gitlab-ce-vs-gitlab-ee.html#dropdown)
* EE Starter to EE Premium (https://about.gitlab.com/comparison/gitlab-ees-vs-gitlab-eep.html)
* Who's who in Product (https://about.gitlab.com/handbook/product/)
* [GitLab Workflow](https://about.gitlab.com/2016/10/25/gitlab-workflow-an-overview/)
* [Latest Version released features](https://about.gitlab.com/2017/06/07/gitlab-9-dot-2-dot-5-security-release/#)
* [GitLab Products](https://about.gitlab.com/products/)
* [Future Releases](https://about.gitlab.com/direction/#future-releases)
* [Know EE features for upgrade from CE](https://about.gitlab.com/comparison/gitlab-ce-vs-gitlab-ee.html#dropdown)
* [EE Starter to EE Premium](https://about.gitlab.com/comparison/gitlab-ees-vs-gitlab-eep.html)
* [Who's who in Product](https://about.gitlab.com/handbook/product/)
* Study the [Sales Handbook](https://about.gitlab.com/handbook/sales/)
......@@ -104,7 +102,7 @@ Complete Zendesk Agent training (allow 40 minutes for completion)
* [Idea to Production Demo](https://about.gitlab.com/handbook/product/i2p-demo/)
 
* [GitLab EE product qualification questions](https://about.gitlab.com/handbook/EE-Product-Qualification-Questions/)
* [Understanding of Gitlab HA and Gitlab GEO] (https://about.gitlab.com/high-availability/)
* [Understanding of Gitlab HA and Gitlab GEO](https://about.gitlab.com/high-availability/)
In the Sales Folder, familiarize yourself with:
......@@ -116,18 +114,18 @@ Our [Sales Agenda](https://docs.google.com/document/d/1l1ecVjKAJY67Zk28CYFiepHAF
 
**Week 5-6**
 
**Understanding the Competition**
(Competition (https://about.gitlab.com/comparison/))
**Understanding the Competition**
[Competition](https://about.gitlab.com/comparison/)
* Github
* Bitbucket
* Other
 
**Understand Integrations**
* Jira (https://docs.gitlab.com/ee/user/project/integrations/jira.html)
* Jenkins (https://docs.gitlab.com/ee/integration/jenkins.html)
* [Jira](https://docs.gitlab.com/ee/user/project/integrations/jira.html)
* [Jenkins](https://docs.gitlab.com/ee/integration/jenkins.html)
 
**Migrations from other Version Control Systems**
* SVN (https://git-scm.com/book/en/v1/Git-and-Other-Systems-Git-and-Subversion)
* [SVN](https://git-scm.com/book/en/v1/Git-and-Other-Systems-Git-and-Subversion)
 
**Integrating with GitLab**
 
......@@ -141,7 +139,7 @@ If you want to integrate with GitLab there are three possible paths you can take
 
* Project Services - Project services give you the option to build your product into GitLab itself. This is the most advanced and complex method of integration but is by far the richest. It requires you to add your integration to GitLab's code base as a standard contribution. You can see the list of project services available, and look into this example. If you're thinking of creating a project service, the steps to follow are similar to any contribution to the GitLab codebase.
 
* Authentication via LDAP/OAuth (https://docs.gitlab.com/ee/integration/oauth_provider.html)
* Authentication via [LDAP/OAuth](https://docs.gitlab.com/ee/integration/oauth_provider.html)
 
**Self assessments**
* [Data migration & integrations](https://goo.gl/forms/Ld2mg6LjmcGgGqkj1)
......@@ -156,7 +154,7 @@ If you want to integrate with GitLab there are three possible paths you can take
* [Health Checks](https://docs.google.com/document/d/1aHA3W2FsHUApnz2XVtJoyhpcGYy6bgOHoRi4ArXnF0o/edit)
 
**Demo Scenarios**
You will be required to demo to team all demo scenarios specific to customer/prospect requirements in mock style showing business value (https://docs.google.com/document/d/1kSVUNM4u6KI8M9FxoyiUbHEHAHIi34iiY25NhMxLucc/edit)
You will be required to demo to team all demo scenarios specific to customer/prospect requirements in mock style showing [business value](https://docs.google.com/document/d/1kSVUNM4u6KI8M9FxoyiUbHEHAHIi34iiY25NhMxLucc/edit)
 
Final certification
 
......
......@@ -102,4 +102,4 @@ These are still to be decided, some suggestions below.
 
1. Ingestion/ETL: Fivetran, Alooma, [Segment and Looker](https://looker.com/blog/segment-and-looker), [StitchData](https://www.stitchdata.com/) (open source), Snaplogic
1. Warehouse: BigQuery
1. Display/analytics: Looker, Redash, [Superset](https://github.com/airbnb/superset) (Apache open source), Tableau, or Metabase (open source)
1. Display/analytics: Looker, Redash, [Superset](https://github.com/airbnb/superset) (Apache open source), Tableau, or [Metabase](https://github.com/metabase/metabase) (open source)
......@@ -65,6 +65,7 @@ in the future to unblock?
## Director team
 
1. Ability to align the day-to-day execution to the top objectives of the company.
2. Work peer-to-peer and sponsor heathly conflict amongst the team to resolve issues quickly, escalating only when all options are exhausted
 
## Executive team
 
......
......@@ -31,6 +31,7 @@ Sid and Dmitriy teamed up and introduced [GitLab Enterprise Edition] with the fe
In 2014 GitLab was officially incorporated as a limited liability corporation.
GitLab released a new version every month on the 22nd, just as every year before and after.
The first release of the year at January 22nd: GitLab 6.5. At the end of 2014, December 2014, GitLab 7.6 was released.
In the end of that year we submitted [our application to Y Combinator](https://about.gitlab.com/2016/09/30/gitlabs-application-for-y-combinator-winter-2015/).
 
### _2015: Y Combinator_
 
......
......@@ -257,7 +257,7 @@ Summary: With a great team make a popular next generation product that grows rev
* CRO: Decrease Time to close (New Business - Sales Assisted) by 10%
* Sales Ops: Launch MEDDPIC. Fields 100% filled out for all stage 3+ deals
* CRO: 165% net retention in [Q4 renewal value](https://na34.salesforce.com/00O61000001uN0a)
* Sales Ops: 95% of subscriptions under $1200 moved to auto-renew
* Sales Ops: 95% of subscriptions under $1200 moved to auto-renew
* CS: 25% of large/strategic accounts on EES trialing EEP with how we expand game plan documented in SFDC
* CFO: Efficiency
* Legal: Publish sales training guide on key legal terms common in deals
......@@ -277,16 +277,21 @@ Summary: With a great team make a popular next generation product that grows rev
* Geo: Geo GA
* CI/CD: Improve support for Java development lifecycle. 1 more project done.
* CI/CD: Improve existing features with additional value. 1 feature extended.
* Build: Cloud native deployment on Kubernetes. Deliver [another GitLab component container & chart](https://gitlab.com/charts/charts.gitlab.io/issues/14), used in production.
* Build: Easier GitLab installation. Ship at least two [Omnibus improvements](https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2833). Ship [AWS Quickstart](https://gitlab.com/gitlab-org/gitlab-aws-quickstart/issues/6).
* Build: Generally available [Omnibus HA](https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2831) & [Kubernetes](https://gitlab.com/charts/charts.gitlab.io/issues/68) deployments.
* Build: Cloud native deployment on Kubernetes. Release [the cloud native GitLab chart](https://gitlab.com/charts/charts.gitlab.io/issues/14) in beta.
* Build: Easier GitLab installation. Submit [the GitLab AWS Quickstart](https://gitlab.com/gitlab-org/gitlab-aws-quickstart/issues/6) for review. Improve [Omnibus configuration output](https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2533).
* Build: GitLab with high availability. Make [GitLab HA with Omnibus](https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2831) GA.
* Prometheus: Make GitLab easier to monitor. [GA Prometheus monitoring of the GitLab server](https://gitlab.com/gitlab-org/gitlab-ce/issues/38568), deprecate InfluxDB.
* Prometheus: Shift performance monitoring earlier in the pipeline, [detecting regressions prior to merge](https://gitlab.com/gitlab-org/gitlab-ee/issues/3173). Deliver one feature.
* Prometheus: Complete the feedback loop by [comparing Canary and Stable performance](https://gitlab.com/gitlab-org/gitlab-ee/issues/2594).
* CTO: [Scan source code for security issues](https://gitlab.com/gitlab-org/gitlab-ce/issues/38413 ). Make it work for 3 popular frameworks.
* CTO: [Less effort to merge CE into EE](https://gitlab.com/gitlab-org/gitlab-ee/issues/2952#note_41016654). 10 times less efforts to merge CE to EE
* CTO: Investigate our options around chat functionality. Come up with a plan to have chat per project/group/instance.
* CEO: Partnerships
* Increase adoption of Kubernetes through integration.
* CI/CD: Configure review apps and deployment for projects in less than 5 steps.
* Prometheus: Enable [Prometheus monitoring of Kubernetes clusters]((https://gitlab.com/gitlab-org/gitlab-ce/issues/28916)) with a single click.
* Platform: Help partners and customers adopt GitLab. Ship authentication and integration requirements.
* Platform: Ship the GNOME requirements. 5 requirements shipped.
* CI/CD: Increase adoption of Kubernetes through integration. Configure review apps and deployment for projects in less than 5 steps.
* At least 3 GNOME projects migrated to GitLab as part of evaluation
* [AWS QuickStart guide](https://gitlab.com/gitlab-org/gitlab-ce/issues/29199) published
* CEO: Preparing GitLab.com to be mission-critical. Availability stable at 99.9%; test URL's and new features all meet Speed Index < 2s.
......
......@@ -15,4 +15,4 @@ Read the pages below to learn more about GitLab:
1. [Values](https://about.gitlab.com/handbook/values/)
1. [Culture](https://about.gitlab.com/culture/)
1. [OKRs](https://about.gitlab.com/okrs/)
1. [2/3 market share](https://about.gitlab.com/2017/06/29/whats-next-for-gitlab-ci/)
1. [Is it any good?](https://about.gitlab.com/is-it-any-good/)
---
layout: default
title: Idea
title: Create
suppress_header: true
extra_css:
- features-v2.css
- release-posts.css
---
 
= partial "includes/solutions/solution-page", locals: { solution: data.solutions.solutions.idea, solution_name: "idea" }
= partial "includes/solutions/solution-page", locals: { solution: data.solutions.solutions.configure, solution_name: "configure" }
---
layout: default
title: Review
title: Packaging
suppress_header: true
extra_css:
- features-v2.css
- release-posts.css
---
 
= partial "includes/solutions/solution-page", locals: { solution: data.solutions.solutions.review, solution_name: "review" }
= partial "includes/solutions/solution-page", locals: { solution: data.solutions.solutions.packaging, solution_name: "packaging" }
---
layout: default
title: Define
title: Verify
suppress_header: true
extra_css:
- features-v2.css
- release-posts.css
---
 
= partial "includes/solutions/solution-page", locals: { solution: data.solutions.solutions.define, solution_name: "define" }
= partial "includes/solutions/solution-page", locals: { solution: data.solutions.solutions.verify, solution_name: "verify" }
Supports Markdown
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