Add the new site

source/atom.xml.builder

+xml.instruct!
+xml.feed "xmlns" => "http://www.w3.org/2005/Atom" do
+  site_url = "https://about.gitlab.com/blog/"
+  xml.title "GitLab"
+  xml.id URI.join(site_url, blog.options.prefix.to_s)
+  xml.link "href" => URI.join(site_url, blog.options.prefix.to_s)
+  xml.updated(blog.articles.first.date.to_time.iso8601) unless blog.articles.empty?
+  xml.author { xml.name "Blog Author" }
+
+  blog.articles[0..20].each do |article|
+    xml.entry do
+      xml.title article.title
+      xml.link "rel" => "alternate", "href" => URI.join(site_url, article.url)
+      xml.id URI.join(site_url, article.url)
+      xml.published article.date.to_time.iso8601
+      xml.updated File.mtime(article.source_file).iso8601
+      xml.author { xml.name article.data.author }
+      xml.content article.body, "type" => "html"
+    end
+  end
+end

source/aws/index.html.haml

+---
+layout: default
+title: GitLab CE AWS AMI
+suppress_header: true
+purple_bg: true
+extra_css:
+  - aws.css
+current_version: gitlab-aws-image
+---
+
+.aws-header
+  %h1 GitLab CE AWS AMI
+  %h2 GitLab Community Edition on AWS with our machine image
+  .btn-group
+    %button.btn.btn-default.dropdown-toggle.btn-lg{"data-toggle" => "dropdown", onclick: "ga('send', 'event', 'dropdown','select','aws region select open');", type: "button"}
+      Select AWS region
+      %span.caret
+    %ul.dropdown-menu{role: "menu"}
+      - data.aws.each do |region|
+        %li
+          %a{href: "##{region.id}", onclick: "ga('send', 'event', 'link','click','download ce');"}
+            = region.name
+
+  #tabs
+    - data.aws.each do |region|
+      .tab{id: region.id}
+        .aws-install
+          .aws-install-step
+            %p
+              Search for this AMI (
+              = current_page.data.current_version
+              ) under Community AMIs
+            %p
+              = region.name
+            %p
+              The latest version of GitLab CE will be fetched on first boot.
+          .aws-install-step
+            %p
+              Launch a
+              %a{href: "https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/requirements.md"} c4.large instance
+              with open ports for ssh, http and https.
+              %br/
+              SSH into the instance with ubuntu@your-instance, edit the
+              %br/
+              %code /etc/gitlab/gitlab.rb
+              file to your needs, and run
+            %p sudo gitlab-ctl reconfigure
+          .aws-install-step
+            %p
+              Visit the public IP in a browser and sign in as the default user
+            %p
+              username: root
+              %br/
+              password: 5iveL!fe
+        = partial "includes/downloads/other"

source/blog/archives.html.haml

+---
+layout: default
+title: Blog archives
+---
+
+.blog-index.blog-entry
+  %ul.post-list
+    - blog.articles.each do |post|
+      %li
+        = link_to post.url do
+          = post.title
+        - if post.date
+          %time
+            = post.date.to_time.strftime '%b %e, %Y'

source/blog/index.html.haml

+---
+title: Blog
+comments: false
+suppress_header: true
+---
+
+.blog-index.blog-entry
+  = partial "includes/newsletter-signup.html"
+  - blog.articles[0...3].each do |article|
+    %article.blog-article
+      = partial "includes/blog/snippet", locals: {post: article}
+  %h2
+    10 most recent posts
+  %ul.post-list
+    - blog.articles[0..10].each do |post|
+      %li.post-list-item
+        %a{href: post.url}
+          = post.title
+        - if post.date
+          %time
+            = post.date.to_time.strftime '%b %e, %Y'
+  %p
+    \→
+    %a{href: "/blog/archives.html"} Browse the archives

source/case-studies/360i-transitions-to-gitlab/index.html.md

+---
+layout: post
+title: 360i transitions to GitLab
+date: March 04, 2014
+author: Marc Radulescu
+---
+
+### 360i decides to move away from SVN
+360i recently caught the spotlight for being the most innovative and one of the most successful digital media companies in the US. They focus on digitally centric programs for their customers, with campaigns for renowned brands such as Oreo, Toyota, Hanes and Ben & Jerry's. Their continuously innovative ideas are made possible, in part, by a software infrastructure maintained using GitLab.
+
+Initially, 360i was using SVN for their code revision control, but they recently decided to look for alternatives. At first, the developers’ main goal was to move away from the SVN legacy system because of its limited collaboration options and big storage demands. Once they began using GitLab, however, they found that not only is the underlying Git a better system, but GitLab’s collaboration tools and open-source code are bringing added value to the company.
+
+Keith Harris, associate director and the person in charge with software architecture at 360i, was having trouble with the legacy SVN code revisioning setup on two major accounts: first, it was easy for developers to accidentally break the code when committing, and
+second, the storage requirements were getting heftier and heftier.
+
+### GitLab is the chosen alternative
+When Keith started looking for alternatives to SVN, he had to balance internal team preferences with management requirements. The team had always wanted to move to Git, but they also wanted a user-friendly interface to help their workflows. From a managerial standpoint, having an on-premises installation was mandatory so as to respect third-party agreements. Keith himself was a supporter of open-source software.
+
+Bringing together the wishes of all parties involved, Keith decided to start testing GitLab, to see if it was easy enough for him to maintain and for the developers to use. He soon gained confidence in the stability of his GitLab installation, so he is running it on the bleeding edge now.
+
+### The developers become intrigued with GitLab’s source code
+The open-source nature of GitLab provided an incentive for Keith to start digging into the code and see if there were any improvements to be made. One such improvement, showing permissions as a grid, he shared with the community and was afterwards merged by Dmitriy to be included in GitLab v6.0. “The source code is clean and easy to read”, said Keith, who even started learning a little bit of Ruby to get more from GitLab. Soon, those developers who were involved with GitLab began to share Keith’s enthusiasm and were browsing the source code as well.
+
+After the testing phase finished, GitLab was rolled out in production and the workflow was changed, so that all new projects would be handled via GitLab, with SVN only supporting the old projects, awaiting migration.
+
+### Implementing GitLab leads to additional benefits
+Initially, the team only expected to see an improvement in the efficiency of their work. However, the collaboration between developers was a major and unexpected gain for the team. The issue tracker and user-friendly interface allowed developers to quickly identify and fix bugs and to write better code. The integrated wiki made documentation easier. User permissions introduced more clarity in the workflow.
+
+The implementation also opens long-term opportunities. GitLab is versatile and user-friendly enough to make Keith wonder whether he can involve more of the company with the setup. Some of the tools he is managing, which are used by other departments, could at one point be replaced with a customized GitLab version.
+
+### Learning points
+The experience of introducing GitLab at 360i leads to several key learning points:
+ - the on-premises installation is a big advantage for companies that need to keep sensitive information in-house;
+ - keeping to centralized version control systems has two drawbacks: not only does it create frustration in the team, but it also makes it harder for the company to keep and attract new talent;
+ - GitLab makes developers happy on two counts: first, it makes it easy for them to collaborate in writing code, and second, it also allows them to dig into the source code, learn best practices, and perform customizations.

source/community/index.html.haml

+---
+layout: default
+title: Community
+suppress_header: true
+purple_bg: true
+extra_css:
+  - community.css
+---
+.community.wrapper
+  .container
+    .row
+      .col-sm-6.col-md-4
+        %a{href: "https://gitlab.com/gitlab-org/gitlab-ce/tree/master#README"}
+          = image_tag "/images/icons/development.png", alt: "Source Code", id: "source-code"
+          %h2 Source code
+          %p
+            The GitLab Community Edition source code
+      .col-sm-6.col-md-4
+        %a{href: "/core-team"}
+          = image_tag "/images/icons/team.png", alt: "Core Team", id: "core-team"
+          %h2 Core Team
+          %p People behind the open-source project.
+      .col-sm-6.col-md-4
+        %a{href: "http://contributors.gitlab.com/"}
+          = image_tag "/images/icons/development.png", alt: "Contributors", id: "contributors"
+          %h2 Contributors
+          %p Contributors to the open-source project.
+      .col-sm-6.col-md-4
+        %a{href: "/documentation"}
+          = image_tag "/images/icons/documentation.png", alt: "Documentation", id: "documentation"
+          %h2 Documentation
+          %p All GitLab projects in one place.
+      .col-sm-6.col-md-4
+        %a{href: "/getting-help"}
+          = image_tag "/images/icons/help.png", alt: "Getting help", id: "help"
+          %h2 Getting Help
+          %p How to get help and stay informed.
+      .col-sm-6.col-md-4
+        %a{href: "/contributing"}
+          = image_tag "/images/icons/contributing.png", alt: "Contributing", id: "contributing"
+          %h2 Contributing
+          %p Information on how to contribute to the projects.
+      .col-sm-6.col-md-4
+        %a{href: "/applications"}
+          = image_tag "/images/icons/apps.png", alt: "Applications", id: "applications"
+          %h2 Applications
+          %p List of applications which support GitLab.
+      .col-sm-6.col-md-4
+        %a{href: "/mvp"}
+          = image_tag "/images/icons/mvp.png", alt: "Hall of fame", id: "mvp"
+          %h2 Hall of Fame
+          %p The most valuable persons in past releases.
+      .col-sm-6.col-md-4
+        %a{href: "https://gitlab.mybrightsites.com/"}
+          = image_tag "/images/icons/swag_shop.png", alt: "Hall of fame", id: "mvp"
+          %h2 GitLab Swag Shop
+          %p Show off your love for GitLab.
+      .clearfix.visible-sm-block

source/community/sponsorship/index.html.markdown

+---
+layout: markdown_page
+title: "GitLab Sponsorship"
+comments: false
+sharing: true
+suppress_header: true
+---
+![Community Sponsorship](/images/community/gitlab-growth.jpg)
+
+# Community Sponsorship
+
+GitLab would like to reach out and grow the community.
+
+Each year GitLab sponsors a number of large events in Europe and North America and we send our team to speak or teach workshops in the most farflung parts of the globe. In 2016 we are sponsoring larger initatives such as [Ruby Together](https://rubytogether.org/), but would like to expand our reach into the community through a more localized sponsorship program.
+
+### How we can help
+
+1.  Financial assistance, in some cases.
+2.  Venue, food, drinks and some flashy GitLab swag for GitLab meet-ups.
+3.  Coaching, mentors and speakers for events.
+4.  Assistance in promotion of your GitLab-focused event.
+
+[Apply for sponsorship](https://docs.google.com/forms/d/1FUm7DOc85yjplFj4zAIo3pqlGlbJR4c6AnHDHVv0k7Y/viewform)
+
+### Our highest priorities
+
+All applications will be reviewed by our team. Our highest priority in selecting events to support is to reach the greatest number of people and grow the open source GitLab community.
+
+1.  Events or initiatives which foster diversity, especially in underserved regions and communities.
+2.  Events or initiatives which help mentor young people in finding a path to software development fluency.
+3.  Events where our users meet, such as GitLab meetups.
+
+We would like to sponsor events related to issues and solutions that GitLab users face every day, such as DevOps, open source and collaboration. If you think you have an event where people would like to get to know more about GitLab and our community, please do contact us. We certainly haven't thought of everything.
+
+### A special grant for Diversity events
+
+In February 2016, [we announced a $500 USD grant](https://about.gitlab.com/2016/02/02/gitlab-diversity-sponsorship/) for ALL events which promote diversity in technology.
+Yep, all events which help increase diversity in technology fields.
+You will automatically receive the grant if you meet the criteria.
+We're focusing on regions outside of New York and the Bay Area because these
+areas are already well-served by existing programs.
+
+What are the criteria?
+
+*   An event which aims to increase participation from underrepresented groups in its local region.
+*   An event outside of NYC or Bay Area.
+
+Why is fostering diversity important?
+
+As if the moral imperative and ethical rationale was not enough,
+there are also practical advantages to fostering diversity.
+These events help increase the potential pool of talent to work at GitLab.
+Research has also proven that more diversity is better for business in almost
+every aspect. ([McKinsey, 2015](http://www.mckinsey.com/insights/organization/why_diversity_matters))
+
+### A grant for open science
+
+We are also offering a special grant for the integration of GitLab into the Open Science Framework (OSF). Please read how you can help: [OSF grant.](https://about.gitlab.com/2015/09/03/a-grant-to-help-us-integrate-gitlab-with-open-source-osf/)

source/community/writers/index.html.markdown

+---
+layout: markdown_page
+title: "Write for GitLab"
+comments: false
+sharing: true
+suppress_header: true
+---
+![Write for GitLab](/images/community/computers-table-banner.jpg)
+
+# Write for GitLab
+
+We’re opening our blog up to contributions from the community.
+
+When you get published on our site you can earn $50 to $200 for technical articles. If you’re accepted, you’ll get feedback on your writing, and be guided through making the best resources. Find out how to get started!
+
+All great contributions come from developers “scratching their own itch.” It’s likely you can share some advice to help someone along the way. You can contribute the technical content you wish was available.
+
+### How it works
+
+1.  Submit topics and a writing sample to us.
+2.  Get approved. Sign contracts.
+3.  Start writing, get feedback and revise.
+4.  Publish.
+5.  Get paid.
+
+First you’ll submit a writing sample and tell us about your areas of expertise. After you get approved, we’ll contact you to initiate the writing process. You’ll get detailed feedback on your writing as we push the article to publication. Once it’s published you’ll get paid.
+
+In terms of pricing, we looked to the industry to see what were the going rates. Your feedback is welcome. Here are our rough guidelines for rates. However, we keep an [open list of topics](https://gitlab.com/gitlab-com/blog-posts/issues?milestone_id=&scope=all&sort=created_desc&state=opened&utf8=%E2%9C%93&assignee_id=0&author_id=&milestone_title=&label_name=&weight=) we have bounties on. That can help you identify our most high-priority topics.
+
+- Brief "Quick tips" or feature highlights of less than 800 words. - $50
+- Short tutorials of 800-1500 words. - $100
+- In-depth tutorials or opinion pieces of 1,500+ words. - $200
+
+### What we're looking for
+
+We’re inviting community contribution so we can expand the range of tutorials and advice about creating, collaborating and deploying with GitLab.
+
+It's important that the content is:
+
+- Accurate
+- Complete
+- Original
+
+We'll be able to develop a more complete style guide as we grow out the program. Meanwhile we will rely on referencing [the Digital Ocean style guide, which inspired our community writers program](https://www.digitalocean.com/community/tutorials/how-to-write-an-article-for-the-digitalocean-community).
+
+To find out what topics we're looking for, review [the blog post backlog](https://gitlab.com/gitlab-com/blog-posts/issues?milestone_id=&scope=all&sort=created_desc&state=opened&utf8=%E2%9C%93&assignee_id=0&author_id=&milestone_title=&label_name=&weight=) and see if there are any existing requests for topics that inspire you.
+
+Review our [Blog Post Style Guide](https://gitlab.com/gitlab-com/blog-posts/blob/master/STYLEGUIDE.md)
+
+### Example topic areas
+
+- Comparison posts; Git v W; GitLab v X; GitLab CI v Y. GitLab EE v Z.
+Migrating from X to Git and/or GitLab.
+- Working with GitLab, feature highlights and tutorials.
+- Ways of boosting efficiency.
+- Extending capability with integrations.
+- Improving communication in code-collaboration.
+- Managing open source projects.
+- Testing X with GitLab CI
+
+Got an idea?
+
+[Submit your proposal!](http://ow.ly/WWMAg)
+
+### Find out more
+
+- [Our blog](http://about.gitlab.com)
+- [Blog post backlog](http://ow.ly/WWA2n)
+- [Submit your proposal](http://ow.ly/WWMAg)
+- [Blog Style Guide](https://gitlab.com/gitlab-com/blog-posts/blob/master/STYLEGUIDE.md)

source/company/index.html.haml

+---
+layout: default
+title: Company
+suppress_header: true
+purple_bg: true
+extra_css:
+  - company.css
+---
+.company.wrapper
+  .container
+    .row
+      .col-sm-6.col-md-4
+        %a{href: "/blog"}
+          = image_tag "/images/icons/blog.png"
+          %h2 Blog
+          %p The latest news.
+      .col-sm-6.col-md-4
+        %a{href: "/press"}
+          = image_tag "/images/icons/press.png"
+          %h2 Press
+          %p Information for journalists.
+      .col-sm-6.col-md-4
+        %a{href: "/about"}
+          = image_tag "/images/icons/about_us.png"
+          %h2 About Us
+          %p The vision of GitLab B.V..
+      .col-sm-6.col-md-4
+        %a{href: "/team"}
+          = image_tag "/images/icons/team_alt.png"
+          %h2 Team
+          %p Meet our team.
+      .col-sm-6.col-md-4
+        %a{href: "/jobs"}
+          = image_tag "/images/icons/jobs.png"
+          %h2 Jobs
+          %p Join our team.
+      .col-sm-6.col-md-4
+        %a{href: "/terms"}
+          = image_tag "/images/icons/terms.png"
+          %h2 Terms
+          %p Terms, conditions and policies.
+      .clearfix.visible-sm-block
+      .col-sm-6.col-md-4
+        %a{href: "/contact"}
+          = image_tag "/images/icons/contact_us.png"
+          %h2 Contact Us
+          %p How to get in touch.

source/comparison/index.html.haml

+---
+layout: default
+title: GitLab compared to other tools
+suppress_header: true
+purple_bg: true
+extra_css:
+  - comparison.css
+---
+.row
+  .hidden-xs.hidden-sm.col-md-3
+    .navigation-wrapper
+      .navigation-reasons
+        %ul
+          %li
+            %a{href: "#gitlab-ce-vs-ee"} GitLab CE vs. GitLab EE
+          %li
+            %a{href: "#gitlab-vs-github"} GitLab vs. GitHub
+          %li
+            %a{href: "#gitlab-ee-vs-github-enterprise"} GitLab EE vs. GitHub Enterprise
+          %li
+            %a{href: "#gitlab-com-vs-github-com"} GitLab.com vs. GitHub.com
+          %li
+            %a{href: "#gitlab-vs-bitbucket-server"} GitLab CE/EE vs. Bitbucket Server
+          %li
+            %a{href: "#gitlab-vs-bitbucket-org"} GitLab.com vs. Bitbucket.org
+          %li
+            %a{href: "#gitlab-vs-saas"} GitLab CE/EE vs. SaaS
+          %li
+            %a{href: "#gitlab-vs-svn"} GitLab vs. SVN
+  .col-xs-12.col-sm-12.col-md-9
+    .wrapper
+      .heading
+        %h1 GitLab compared to other tools
+        %p.note-on-content
+          Since GitLab loyalists wrote them, the comparisons here might be biased.
+          Nonetheless we try hard to ensure the comparisons are fair and factual.
+          If you find something that is invalid, biased or out of date in the comparisons,
+          please open a
+          %a{href: "https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests"} merge request for this website
+          to correct it.
+          As on all the pages on this website you can find a link to this page in the repository in the footer. We can help with migration services as part of a custom GitLab EE plan. Please
+          %a{href: "https://about.gitlab.com/sales/"} contact sales
+          if you would like to learn more.
+      .title-container
+        .hr-title
+        %h3#gitlab-ce-vs-ee.title GitLab CE vs. GitLab EE
+        .hr-title
+      .list-of-reasons-container
+        %ol
+          %h4
+            To learn more about how GitLab Community Edition compares to GitLab Enterprise Edition, take a look at
+            = succeed "." do
+              %a{href: "https://about.gitlab.com/features/#compare"} the comparison table on our features page
+      .title-container
+        .hr-title
+        %h3#gitlab-vs-github.title GitLab vs. GitHub
+        .hr-title
+      .list-of-reasons-container
+        %ol
+          %li#multiple-authentication-levels
+            %p Multiple authentication Levels
+            %p Set permissions according to people's role, rather than either read or write access to a repository. Don't share the source code with people that only need access to the issue tracker.
+            %p
+              %a{href: "http://doc.gitlab.com/ce/permissions/permissions.html"} See the various authentication levels
+          %li#group-level-milestones
+            %p Group-level milestones
+            %p View all the issues for the milestone you’re currently working on across multiple projects.
+            %p
+              %a{href: "https://gitlab.com/groups/gitlab-org/milestones/8-2?title=8.2"} Example milestone for GitLab 8.2 (need to be logged in)
+          %li#attachments-in-issues
+            %p Attachments in issues
+            %p In GitLab you can attach any file to any issue or comment.
+          %li#innersourcing
+            %p Innersourcing
+            %p Internal projects in GitLab allow you to promote innersourcing of your internal repositories.
+            %p
+              %a{href: "https://about.gitlab.com/2014/09/05/innersourcing-using-the-open-source-workflow-to-improve-collaboration-within-an-organization/"} Find out more about innersourcing
+          %li#wip-protection
+            %p Work-in-Progress Protection
+            %p
+              Simply add 'WIP' to the title of a merge request to prevent anyone from merging
+              it. This gives you all the code review power of merge requests,
+              while protecting unfinished work.
+            %p
+              %a{href: "http://doc.gitlab.com/ce/workflow/wip_merge_requests.html"} WIP Merge documentation
+          %li#large-open-source-projects
+            %p Large open source projects
+            %p
+              GitLab is meant to be the best place for any software project.  The team
+              behind GitLab is addressing issues that maintainers and contributors to large
+              open source projects are facing, to make it easier to do both.
+            %p
+              %a{href: "https://about.gitlab.com/2016/01/15/making-gitlab-better-for-large-open-source-projects/"} Making GitLab better for large open source projects
+          %li#powerful-issue-tracker
+            %p Powerful Issue Tracker
+            %p Quickly set the status, assignee or milestone for multiple issues at the same time or easily filter them on any properties. See milestones and issues across projects.
+          %li#commit-search
+            %p Search through Commits
+            %p
+              GitLab not only allows you to search through code, but also
+              searches through your commit messages.
+          %li#article
+            %p Don't take our word for it.
+            %p
+              Agilob contributed a
+              = succeed "." do
+                %a{href: "https://www.b.agilob.net/choose-gitlab-for-your-next-project/"} great article about why you should choose GitLab for your next open source project
+          .title-container
+            .hr-title
+            %h3#gitlab-ee-vs-github-enterprise.title GitLab EE vs. GitHub Enterprise
+            .hr-title
+          .list-of-reasons-container
+            %ol
+            %li#Cost
+              %p Cost
+              %p
+                GitLab has the most competitive pricing model in the market and a fraction
+                of the cost of our competition. Our remote-first philosophy allow us to pass on the cost savings to our clients.
+            %li
+              %p All features mentioned in GitLab.com versus GitHub.com
+            %li#gitlab-handles-huge-repositories-well
+              %p GitLab handles huge repositories well
+              %p
+                Big repository? Huge (>5GB) binary files? No problem. GitLab is built to
+                handle very large repositories, and Git Annex and LFS are both supported.
+              %p
+                %a{href: "https://about.gitlab.com/2015/02/17/gitlab-annex-solves-the-problem-of-versioning-large-binaries-with-git/"} Using Git Annex with GitLab
+            %li#rebase-before-merge-in-the-web-ui-to-prevent-merge-commits
+              %p Rebase before merge in the web UI to prevent merge commits
+              %p Before merging one branch in the other, GitLab can rebase it automatically.
+              %p
+                %a{href: "https://about.gitlab.com/2014/12/22/gitlab-7-6-and-ci-5-3-released/"} See how to prevent merge commits
+            %li#access-to-the-server
+              %p Access to the server
+              %p You have complete control of the server/instance, so you can install additional software (intrusion detection, performance monitoring, etc.) and view log files on the server itself.
+              %p
+                %a{href: "http://doc.gitlab.com/ce/logs/logs.html"} Learn more about logging
+            %li#runs-on-metal
+              %p Runs on metal
+              %p You can run GitLab fully on metal. No need for pre-supplied VMs. Run GitLab on your infrastructure, however you like.
+            %li#more-users-on-a-single-server
+              %p Run more users on a single server
+              %p A single machine server handles thousands of users and repositories
+            %li#multiple-active-servers-and-other-ha-setups
+              %p HA setups
+              %p GitLab offers multiple HA solutions, making it possible to failover easily.
+              %p
+                %a{href: "https://about.gitlab.com/high-availability/"} More information about active servers
+            %li#run-your-own-software-on-your-instance
+              %p Run your own software on your instance
+              %p You are free to run your own software on the instance that GitLab is running on. Have your own intrusion detection system? No problem.
+            %li#use-your-configuration-management-software
+              %p Use your configuration management software
+              %p
+                Use configuration management software of your choice to manage GitLab.
+                Puppet, Chef, Ansible—it all works.
+              %p
+                %a{href: "https://about.gitlab.com/installation/"} Read about configuration management here
+            %li#use-standard-unix-tools-for-maintenance-and-monitoring
+              %p Use standard Unix tools for maintenance and monitoring
+              %p
+                Use the tools you know for monitoring and maintenance, whether they're
+                standard or your own. GitLab doesn't restrict you.
+            %li#built-in-continuous-integration-tool
+              %p Built-in Continuous Integration tool
+              %p Easy-to-set up, performant, stable and elegant continuous integration with every GitLab installation.
+              %p
+                %a{href: "http://doc.gitlab.com/ci/"} Learn about the benefits of our CI tool
+            %li#powerful-ad-ldap-integration
+              %p Powerful AD / LDAP integration
+              %p Sync groups, manage SSH-keys, manage permissions, authentication and more. You can manage an entire GitLab instance through the LDAP / AD integration.
+              %p
+                %a{href: "http://doc.gitlab.com/ee/integration/ldap.html"} More information about AD / LDAP integration
+            %li#approve-merge-requests
+              %p Multiple approvals in code review
+              %p
+                To ensure strict code review, you can require a specific number of approvals
+                on a merge request by different users before being able to merge it.
+              %p
+                %a{href: "http://doc.gitlab.com/ee/workflow/merge_request_approvals.html"} Approvals Documentation
+            %li#ease-of-migration
+              %p Ease of Migration
+              %p Easily migrate all repos and merge request data from your previous provider.
+            %li#security-and-policy-enforcement
+              %p Security and Policy enforcement
+              %p Git Hooks and Audit logs and enhanced LDAP integration give you and the added security to meet the increasing requirements of compliance teams.
+            %li#issue-weights
+              %p Issue Weights
+              %p
+                Manage issues using Agile practices by setting the weight of an issue.
+              %p
+                %a{href: "http://doc.gitlab.com/ee/workflow/issue_weight.html"} Issue Weights Documentation
+            %li#mr-issue-templates
+              %p Merge Request  Issue Templates
+              %p Create a template for issues and merge requests in your project to ensure all information is entered correctly and to make it easy to standardise.
+              %p
+                %a{href: "http://doc.gitlab.com/ee/customization/issue_and_merge_request_template.html"} Templates for Issues and Merge Requests Documentation
+            %li#most-installed-on-premises-git-solutions
+              %p Use the most installed on-premises Git solution
+              %p
+                GitLab is used by over 100,000 organizations worldwide,
+                on their own servers.
+        .title-container
+          .hr-title
+          %h3#gitlab-com-vs-github-com.title GitLab.com vs. GitHub.com
+          .hr-title
+        .list-of-reasons-container
+          %ol
+            %li
+              %p Everything mentioned in GitLab versus GitHub
+            %li#unlimited-public-and-private-repositories-for-free
+              %p Unlimited public  private repositories and unlimited collaborators for free.
+            %li#gitlab-ee-features-on-com
+              %p GitLab.com runs GitLab Enterprise Edition with all its features.
+            %li#free-ci
+              %p
+                GitLab.com has free
+                %a{href: "/gitlab-ci"} GitLab CI
+                if you bring your own runner or use the shared ones.
+        .title-container
+          .hr-title
+          %h3#gitlab-vs-bitbucket-server.title GitLab CE/EE vs. Bitbucket Server
+          .hr-title
+        .list-of-reasons-container
+          %ol
+            %li#built-in-continuous-integration-tool
+              %p Built-in Continuous Integration tool
+              %p Easy-to-set up, performant, stable and elegant continuous integration with every GitLab installation.
+              %p
+                %a{href: "http://doc.gitlab.com/ci/"} Learn about the benefits of our CI tool
+            %li#all-in-one
+              %p More value with everything you need in one solution
+              %p To replace GitLab, you'd need a combination of Bitbucket server, JIRA, Confluence, and Bamboo.
+            %li#nicer-interface
+              %p Great user interface
+              %p GitLab has a really nice user interface that your team will love, and also enjoy working with.
+            %li#integrated-issue-tracking
+              %p Integrated issue tracking
+              %p GitLab includes an issue tracker which you can link to any merge request.
+              %p
+                %a{href: "https://gitlab.com/gitlab-org/gitlab-ce/issues"} Issue Tracker
+            %li#no-activity-feed
+              %p Better activity feed and visualization
+              %p Collaborative activity feed to help everyone understand what is happening in a project and graphical view of the commit history.
+              %p
+                %a{href: "https://gitlab.com/gitlab-org/gitlab-ce/activity"} See Our Activity Feed
+            %li#powerful-search
+              %p Full, powerful search
+              %p
+                Search through all your code, issues, wikis, commits,
+                groups and projects. Built into GitLab.
+        .title-container
+          .hr-title
+          %h3#gitlab-vs-bitbucket-org.title GitLab.com vs. Bitbucket.org
+          .hr-title
+        .list-of-reasons-container
+          %ol
+            %li
+              %p Everything mentioned in GitLab CE/EE versus BitBucket Server
+            %li#unlimited-collaborators
+              %p Unlimited collaborators
+              %p With GitLab.com, you don't have to start paying when you have more than 5 collaborators across all your private repositories.
+        .title-container
+          .hr-title
+          %h3#gitlab-vs-saas.title GitLab CE/EE vs. SaaS
+          .hr-title
+        .list-of-reasons-container
+          %ol
+            %li#containment
+              %p Containment
+              %p Containing your company's IP behind the company's firewall gives you protection from unauthorized access. Learn from the lessons of Code Space:
+              %p
+                %a{href: "http://www.infoworld.com/article/2608076/data-center/murder-in-the-amazon-cloud.html"} Lessons from Code Space
+            %li#integrations
+              %p Integrations
+              %p Integrating with Authentication and Authorization (LDAP / AD), issue tracking, CI, deployment and other tools such as ALM, PLM, Agile and Automation tools.
+            %li#control
+              %p Control
+              %p Take control of maintenance downtime, don't be at the mercy of your hosting provider. Control how and where your code is backed up and stored.
+            %li#choice-and-flexibility
+              %p Choice and Flexibility
+              %p GitLab CE/EE can be installed on physical servers, virtualized servers (dedicated or shared), purpose-built appliances and virtualized appliances. These aren’t available with hosted solutions. Likewise, most on-premises servers can be deployed on a variety of operating systems and there’s more choice of on-premises solutions in general.
+            %li#retrieval
+              %p Retrieval
+              %p Getting your IP back from cloud vendors that store data in proprietary formats can be a costly and lengthy process. No such trouble with GitLab CE/EE.
+            %li#in-good-company
+              %p In good company
+              %p GitLab is the most adopted on-premises solution for developer collaboration, deployed at over 100,000 organizations worldwide.
+        .title-container
+          .hr-title
+          %h3#gitlab-vs-svn.title GitLab vs. SVN
+          .hr-title
+        .list-of-reasons-container
+          %ol
+            %li#distributed
+              %p Distributed
+              %p Git, on which GitLab is built, is fully distributed. Every user has a complete copy of the repository, allowing for much faster access to history, easier branching and an overall better experience.
+            %li#access-control
+              %p Access Control
+              %p For someone to commit to a local respository, no access has to be given in Git. At the same time, the owner of the canonical repository has the ability to restrict pushes to the repository or certain branches.
+            %li#powerful-branching
+              %p Powerful Branching
+              %p A branch in Git contains the entire history that preceeds it. It's also created or moved towards instantly and easily shared.
+            %li#speed
+              %p Speed
+              %p Git is really fast. Performing a diff, viewing history, committing and merging changes, obtaining any revision and any form of branching is much faster in Git than SVN.
+            %li#size-requirements
+              %p Size Requirements
+              %p A single repository in Git is typically a number of times smaller than the same repository in SVN.

source/consultancy/confirmation.html.haml

+---
+layout: default
+title: Confirmation
+---
+#content
+  .container.text-left
+    .row
+      .col-sm-9.col-md-9
+        .entry
+          .row
+            .col-sm-12.col-md-12
+              %p
+              %h3 Thanks for filling out the GitLab.com consultancy form. We will soon get in contact with you via your e-mail supplied in the form.
+              / Google Code for Consultancy order Conversion Page
+              :javascript
+                var google_conversion_id = 999150614;
+                var google_conversion_language = "en";
+                var google_conversion_format = "1";
+                var google_conversion_color = "ffffff";
+                var google_conversion_label = "1VBOCMqcyAUQlqi33AM";
+                var google_conversion_value = 0;
+              %script{src: "//www.googleadservices.com/pagead/conversion.js", type: "text/javascript"}
+                :cdata
+              %noscript
+                \<div style="display:inline;">
+                \<img height="1" width="1" style="border-style:none;" alt="" src="//www.googleadservices.com/pagead/conversion/999150614/?value=0&amp;label=1VBOCMqcyAUQlqi33AM&amp;guid=ON&amp;script=0"/>
+                \</div>
+              %p

source/consultancy/index.html.haml

+---
+layout: default
+title: Consultancy
+suppress_header: true
+extra_css:
+  - consultancy.css
+---
+.wrapper
+  .hire-us
+    .container
+      %h1#tagline
+        Need help installing, upgrading, or migrating to GitLab?
+        %br/
+        %small We can help with migration services or simply upgrading your current instance.
+        %br/
+        %small Please note that emergency help is for subscribers only.
+      %a{href: "#consultancy-form"}
+        %button#hire-us.btn.btn-default.btn-lg{type: "button"} Get a Quote
+  #consultancy-form.container
+    .row
+      .col-sm-9.col-md-9
+        .centered-form
+          %script{src: "//app-ab13.marketo.com/js/forms2/js/forms2.min.js"}
+          %form#mktoForm_1061
+          :javascript
+            MktoForms2.loadForm("//app-ab13.marketo.com", "194-VVC-221", 1077, function(form) {
+              form.onSuccess(function(values, followUpUrl) {
+
+                form.getFormElem().hide();
+                document.getElementById('confirmform').style.visibility = 'visible';
+
+                ga('send', 'pageview');
+                ga('send', 'event', 'form', 'submit', 'newsletter signup');
+                return false;
+              });
+            });
+          #confirmform{style: "visibility:hidden;"}
+            %p
+              Thanks for subscribing!

source/contact/index.html.haml

+---
+layout: default
+title: Contact
+suppress_header: true
+purple_bg: true
+extra_css:
+  - contact.css
+---
+.contact
+  .container
+    .row
+      .col-sm-4.col-md-4
+        %a{href: "/getting-help"}
+          = image_tag "/images/icons/about_us.png", alt: "Getting help"
+        %h2
+          %a{href: "/getting-help"} Getting Help
+        %p
+          We have several resources available such as documentation, FAQs,
+          forums, and Issue Trackers to help you with GitLab.
+      .col-sm-4.col-md-4
+        %a{href: "/sales"}
+          = image_tag "/images/icons/contact_us.png", alt: "Contact Us"
+        %h2
+          %a{href: "/sales"} Contact Sales
+        %p
+          Contact our sales team for any questions about GitLab Enterprise
+          Edition. If you have any marketing or PR inquiries, please email
+          = succeed "." do
+            %a{href: "mailto:community@gitlab.com"} community@gitlab.com
+
+      .col-sm-4.col-md-4
+        %a{href: "https://twitter.com/gitlab"}
+          = image_tag "/images/icons/twitter.png", alt: "Twitter"
+        %h2
+          %a{href: "https://twitter.com/gitlab"}
+            Twitter
+        %a.twitter-follow-button{href: "https://twitter.com/gitlab", data: {show: {count: false}}}
+          Follow @gitlab
+        :javascript
+          !function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');
+        %p
+          Follow us on Twitter for the most detailed and up-to-date information about GitLab.
+    .row
+      .col-sm-4.col-md-4
+        = image_tag "/images/icons/news.png", alt: "Newsletter"
+        %h2 Newsletter
+        %script{src: "//app-ab13.marketo.com/js/forms2/js/forms2.min.js"}
+        %form#mktoForm_1073
+        :javascript
+          MktoForms2.loadForm("//app-ab13.marketo.com", "194-VVC-221", 1073, function(form) {
+            form.onSuccess(function(values, followUpUrl) {
+              form.getFormElem().hide();
+              document.getElementById('confirmformnewlsetter').style.visibility = 'visible';
+
+              ga('send', 'pageview');
+              ga('send', 'event', 'form', 'submit', 'newsletter subscription');
+              return false;
+            });
+          });
+        #confirmformnewlsetter{style: "visibility:hidden;"}
+          %p
+            Thanks for subscribing!
+        %p.newsletter-afterword
+          If you subscribe, you will receive our twice-monthly newsletter.
+      .col-sm-4.col-md-4
+        %a{href: "/visiting"}
+          = image_tag "/images/icons/office.png", alt: "Office"
+        %h2
+          %a{href: "/visiting"} Visit Our Office
+        %p
+          Information about visiting our office in San Francisco, California.
+      .col-sm-4.col-md-4
+        %a{href: "/disclosure"}
+          = image_tag "/images/icons/security.png", alt: "Security"
+        %h2
+          %a{href: "/disclosure"} Security
+        %p
+          If you want to test the security of GitLab or if you think you have
+          found a problem please see our
+          %a{href: "/disclosure"}
+            Responsible Disclosure Policy
+
+    .row
+      .col-sm-4.col-md-4
+        = image_tag "/images/icons/security_newsletter.png", alt: "Security newsletter"
+        %h2 Security Notices
+        %form#mktoForm_1102
+        :javascript
+          MktoForms2.loadForm("//app-ab13.marketo.com", "194-VVC-221", 1102, function(form) {
+            form.onSuccess(function(values, followUpUrl) {
+
+              form.getFormElem().hide();
+              document.getElementById('confirmform').style.visibility = 'visible';
+
+              ga('send', 'pageview');
+              ga('send', 'event', 'form', 'submit', 'security updates newsletter');
+              return false;
+            });
+          });
+        #confirmform{style: "visibility:hidden;"}
+          %p
+            Thanks for subscribing!
+        %p.newsletter-afterword
+          If you subscribe, you will receive notifications about security
+          updates.
+      .col-sm-4.col-md-4
+        %a{href: "https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/CONTRIBUTING.md"}
+          = image_tag "/images/icons/website.png", alt: "Website"
+        %h2
+          %a{href: "https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/CONTRIBUTING.md"} Website
+        %p
+          This website is created from a public repository. If you see a
+          potential improvement please
+          %a{href: "https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/CONTRIBUTING.md"} contribute to this website

source/contributing/index.html.haml

+---
+layout: default
+title: Contributing
+suppress_header: true
+extra_css:
+  - contributing.css
+---
+.wrapper
+  .contributing-container
+    .contributing-overlay
+      .contributing-content
+        %h1 Contributing to GitLab
+#content
+  .container-contributing
+    .row
+      .col-sm-6
+        %a{href: "https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md"}
+          .link-box.single
+            %h4 Contributing Guidelines
+            If you want to contribute to GitLab, make sure to read and follow the contributing guidelines.
+      .col-sm-6
+        %a{href: "https://gitlab.com/gitlab-org/gitlab-ce/blob/master/PROCESS.md"}
+          .link-box
+            %h4 Contributing Process
+            Contributors and maintainers should know what to expect from each other in the contribution process.
+            This is described here.
+    .row
+      .col-sm-6
+        %a{href: "https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#feature-proposals"}
+          .link-box
+            %h4 Feedback and Feature Proposals
+            Do you have any feedback, a suggestion or want to hear what others have to say? Share in a feature proposal.
+      .col-sm-6
+        %a{href: "/development/"}
+          .link-box.single
+            %h4 Sponsor the development of new features
+            If you want us to implement a certain feature, you can sponsor us to do so.
+    .row
+      .col-sm-6
+        %a{href: "http://feedback.gitlab.com/forums/176466-general/status/796455"}
+          .link-box
+            %h4 Accepting Merge/Pull Requests
+            You can find out if we are accepting merge requests for certain suggestion features here.

source/core-team/index.html.haml

+---
+layout: default
+title: "GitLab core team"
+suppress_header: true
+extra_css:
+  - core.css
+---
+.wrapper
+  .core-container
+    .core-overlay
+      .core-content
+        %h1 Core Team
+#content
+  .container
+    .teams.row
+      .col-sm-3.col-md-3
+        .core-team-image
+          = image_tag "/images/team/dmitriy.jpg", class: "img-responsive"
+        %ul.core-team-social
+          %li
+            %a{href: "http://dzaporozhets.me/"}
+              .website.no-margin
+          %li
+            %a{href: "https://twitter.com/dzaporozhets"}
+              .twitter.no-margin
+          %li
+            %a{href: "http://ua.linkedin.com/in/dzaporozhets"}
+              .linkedin.no-margin
+          %li
+            %a{href: "https://gitlab.com/u/dzaporozhets"}
+              .gitlab.no-margin
+          %li
+            %a{href: "https://github.com/randx"}
+              .github.no-margin
+      .col-sm-9.col-md-9
+        %h2.title Dmitriy Zaporozhets
+        %p Dmitriy started GitLab in September 2011 and has released it every month on the 22nd since then. He wanted to make a great and free project management system that he could use every day. He loved to work on GitLab so much that in January of 2013 he began to work on GitLab fulltime. When he has time he loves to code a major new GitLab feature in two days. He loves a good Martini and a merge request that can be accepted without comments.
+        %h3.title Specialities
+        %ul
+          %li
+            %a{href: "https://gitlab.com/gitlab-org/gitlab-ce/"} GitLab CE
+            Lead
+    .row
+      %hr.hor-line/
+    .teams.row
+      .col-sm-3.col-md-3
+        .core-team-image
+          = image_tag "/images/team/marin.jpeg", class: "img-responsive"
+        %ul.core-team-social
+          %li
+            %a{href: "https://twitter.com/maxlazio"}
+              .twitter.no-margin
+          %li
+            %a{href: "http://rs.linkedin.com/pub/marin-jankovski/21/a/a64"}
+              .linkedin.no-margin
+          %li
+            %a{href: "https://gitlab.com/u/marin"}
+              .gitlab.no-margin
+          %li
+            %a{href: "https://github.com/maxlazio"}
+              .github.no-margin
+      .col-sm-9.col-md-9
+        %h2.title Marin Jankovski
+        %p Marin loves to develop in Rails but has also grown an interest in operations, specifically Amazon Web Services and Opscode Chef. When video conferencing with him you get a cat running accross the room as a bonus. He is notorious for starting early in the morning just after breakfast and not having lunch until his workday is over. You would expect him to be hungry and grumpy the last few hours but as long as his internet connection is up he is always friendly and upbeat. He loves travelling and talking. A lot of talking. A lot.
+        %h3.title Specialities
+        %ul
+          %li
+            %a{href: "https://gitlab.com/gitlab-org/cookbook-gitlab"} GitLab Cookbook
+            Lead
+          %li
+            %a{href: "https://gitlab.com/gitlab-org/omnibus-gitlab"} Omnibus-gitlab
+            Lead
+          %li
+            GitLab Flavored Markdown (GFM) support
+    .row
+      %hr.hor-line/
+    .teams.row
+      .col-sm-3.col-md-3
+        .core-team-image
+          = image_tag "/images/team/robert.jpeg", class: "img-responsive"
+        %ul.core-team-social
+          %li
+            %a{href: "https://twitter.com/Razer6"}
+              .twitter.no-margin
+          %li
+            %a{href: "https://gitlab.com/u/razer6"}
+              .gitlab.no-margin
+          %li
+            %a{href: "https://github.com/Razer6"}
+              .github.no-margin
+      .col-sm-9.col-md-9
+        %h2.title Robert Schilling
+        %p Robert is a developer who loves science and technology. He currently studies telematics with focus on digital signal processing at Graz University of Technology.  In his spare time he enjoys mountain biking, skiing and photography. When not in front of his computer, Robert can often be found with a glass of good single malt whisky or beer in his hand discussing sports and open source software.
+        %h3.title Specialities
+        %ul
+          %li
+            issue triage lead
+    .row
+      %hr.hor-line/
+    .teams.row
+      .col-sm-3.col-md-3
+        .core-team-image
+          = image_tag "/images/team/jacob.jpeg", class: "img-responsive"
+        %ul.core-team-social
+          %li
+            %a{href: "https://twitter.com/jacobvosmaer"}
+              .twitter.no-margin
+          %li
+            %a{href: "https://www.linkedin.com/profile/view?id=15991252"}
+              .linkedin.no-margin
+          %li
+            %a{href: "https://gitlab.com/u/jacobvosmaer"}
+              .gitlab.no-margin
+          %li
+            %a{href: "https://github.com/jacobvosmaer"}
+              .github.no-margin
+      .col-sm-9.col-md-9
+        %h2.title Jacob Vosmaer
+        %p Jacob is a doctor in logic. He likes to understand and explain complex technical systems. That helps with his job as a senior service engineer at GitLab.com. In his spare time he likes to read Unix books and has a second career as tango DJ in Amsterdam.
+        %h3.title Specialities
+        %ul
+          %li
+            omnibus-gitlab
+            (
+            %a{href: "https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/318#note_296648"} awarded
+            a golden gear medal for bravery and acts of merit serving in the trenches of GitLab Omnibus
+            )
+            %br/
+            = image_tag "/images/golden_gear_medal/golden_gear_medal_175x350.png"
+          %li
+            unix security
+          %li
+            LDAP
+    .row
+      %hr.hor-line/
+    .teams.row
+      .col-sm-3.col-md-3
+        .core-team-image
+          = image_tag "/images/team/sytse.jpeg", class: "img-responsive"
+        %ul.core-team-social
+          %li
+            %a{href: "http://www.sytse.com/"}
+              .website.no-margin
+          %li
+            %a{href: "https://twitter.com/sytses"}
+              .twitter.no-margin
+          %li
+            %a{href: "http://nl.linkedin.com/in/sijbrandij"}
+              .linkedin.no-margin
+          %li
+            %a{href: "https://gitlab.com/u/sytses"}
+              .gitlab.no-margin
+          %li
+            %a{href: "https://github.com/dosire"}
+              .github.no-margin
+      .col-sm-9.col-md-9
+        %h2.title Sytse Sijbrandij
+        %p Sytse saw the first ruby code in 2007 and loved it so much he dove head first into programming. Before that he was engaged in business administration roles and combining that with software development is his passion. He is always looking to make a template out of something or to automate a process. His team members suspect he has todo list and reminders for everything, including breakfast and getting his hair cut. He loves a good beer and organizing a trip to a conference.
+        %h3.title Specialities
+        %ul
+          %li
+            readme and documentation
+          %li
+            interface text
+    .row
+      %hr.hor-line/
+    .teams.row
+      .col-sm-3.col-md-3
+        .core-team-image
+          = image_tag "/images/team/jeroen.jpg", class: "img-responsive"
+        %ul.core-team-social
+          %li
+            %a{href: "https://twitter.com/jvanbaarsen"}
+              .twitter.no-margin
+          %li
+            %a{href: "http://nl.linkedin.com/in/jvanbaarsen"}
+              .linkedin.no-margin
+          %li
+            %a{href: "https://gitlab.com/u/jeroenvanbaarsen"}
+              .gitlab.no-margin
+          %li
+            %a{href: "https://github.com/jvanbaarsen"}
+              .github.no-margin
+      .col-sm-9.col-md-9
+        %h2.title Jeroen van Baarsen
+        = image_tag "/images/merge_marshal/mm_badge_st.png"
+    .row
+      %hr.hor-line/
+    .teams.row
+      .col-sm-3.col-md-3
+        .core-team-image
+          = image_tag "/images/team/drew.jpg", class: "img-responsive"
+        %ul.core-team-social
+          %li
+            %a{href: "https://twitter.com/drewblessing"}
+              .twitter.no-margin
+          %li
+            %a{href: "http://www.linkedin.com/pub/drew-blessing/21/908/b64/"}
+              .linkedin.no-margin
+          %li
+            %a{href: "https://gitlab.com/u/drewb"}
+              .gitlab.no-margin
+          %li
+            %a{href: "https://github.com/dblessing"}
+              .github.no-margin
+      .col-sm-9.col-md-9
+        %h2.title Drew Blessing
+        = image_tag "/images/merge_marshal/mm_badge_st.png"
+    .row
+      %hr.hor-line/
+    .teams.row
+      .col-sm-3.col-md-3
+        .core-team-image
+          = image_tag "/images/team/axil.jpg", class: "img-responsive"
+        %ul.core-team-social
+          %li
+            %a{href: "http://axilleas.me/"}
+              .website.no-margin
+          %li
+            %a{href: "https://twitter.com/_axil"}
+              .twitter.no-margin
+          %li
+            %a{href: "https://gitlab.com/u/axil"}
+              .gitlab.no-margin
+          %li
+            %a{href: "https://github.com/axilleas"}
+              .github.no-margin
+      .col-sm-9.col-md-9
+        %h2.title Achilleas Pipinellis
+        %p
+          Achilleas is an open source enthusiast that tries to get involved in as many projects as possible.
+          His linux distro of choice is Archlinux, although since 2013 he's enjoying making packages for Fedora. You'll often listen him
+          quoting from his favorite movie "The Big Lebowski". When he is not in front of his laptop (a Thinkpad X220 of course!)
+          he practises Aikido, reads Bukowski and enjoys a good meal he cooked all by himself.
+        %h3.title Specialities
+        %ul
+          %li
+            %a{href: "https://gitlab.com/gitlab-org/gitlab-recipes/"} GitLab Recipes
+            Lead
+    .row
+      %hr.hor-line/
+    .teams.row
+      .col-sm-3.col-md-3
+        .core-team-image
+          = image_tag "/images/team/hannes.jpg", class: "img-responsive"
+        %ul.core-team-social
+          %li
+            %a{href: "https://gitlab.com/u/haynes"}
+              .gitlab.no-margin
+          %li
+            %a{href: "https://github.com/123Haynes"}
+              .github.no-margin
+      .col-sm-9.col-md-9
+        %h2.title Hannes Rosenögger
+        %p
+          Hannes is a developer who loves open source.
+          His motto is: "If something is broken that you need and you are able to fix it, don't just talk about it. Fix it!"
+          In his spare time he enjoys swimming, badminton and relaxing with his friends.
+          When he is not in front of his computer, he can often be found on various camping places where he helps out the scouts of his hometown.
+    .row
+      %hr.hor-line/
+    .teams.row
+      .col-sm-3.col-md-3
+        .core-team-image
+          = image_tag "/images/team/kamil.jpg", class: "img-responsive"
+        %ul.core-team-social
+          %li
+            %a{href: "https://ayufan.eu/"}
+              .website.no-margin
+          %li
+            %a{href: "https://twitter.com/ayufanpl"}
+              .twitter.no-margin
+          %li
+            %a{href: "https://www.linkedin.com/in/kamiltrzcinski"}
+              .linkedin.no-margin
+          %li
+            %a{href: "https://gitlab.com/u/ayufan"}
+              .gitlab.no-margin
+          %li
+            %a{href: "https://github.com/ayufan"}
+              .github.no-margin
+      .col-sm-9.col-md-9
+        %h2.title Kamil Trzciński
+        %p
+          Kamil is a low-level programming enthusiast with years of experience in building apps for all platforms. He is also a security, virtualization and graphics expert with a variety of programming languages in his toolkit together with deep operating systems architecture knowledge. He's focusing lately on security principles of mobile platforms and the "container revolution". In his spare time he likes to run, cycle and play good games, although not all at the same time.
+        %h3.title Specialities
+        %ul
+          %li
+            %a{href: "https://gitlab.com/gitlab-org/gitlab-ci/"} GitLab CI
+            Lead
+    .row
+      %hr.hor-line/
+    .teams.row
+      .col-sm-3.col-md-3
+        .core-team-image
+          = image_tag "/images/team/stan.jpg", class: "img-responsive"
+        %ul.core-team-social
+          %li
+            %a{href: "https://www.linkedin.com/in/stanhu00"}
+              .linkedin.no-margin
+          %li
+            %a{href: "https://gitlab.com/u/stanhu"}
+              .gitlab.no-margin
+          %li
+            %a{href: "https://github.com/stanhu"}
+              .github.no-margin
+      .col-sm-9.col-md-9
+        %h2.title Stan Hu
+        %p
+          Stan started working on GitLab because he just wanted to see more Slack notifications, but his
+          interest in the project snowballed after that. Stan has spent close to 20 years writing software at almost every level of the stack, from
+          Linux kernel code to Web applications. Having retired from running marathons, he now spends his free time preparing for triathlons and photographing
+          events.
+    .row
+      %hr.hor-line/
+    .teams.row
+      .col-sm-3.col-md-3
+        .core-team-image
+          = image_tag "/images/team/newton.png", class: "img-responsive"
+        %ul.core-team-social
+          %li
+            %a{href: "http://jamesnewton.com"}
+              .website.no-margin
+          %li
+            %a{href: "https://twitter.com/jameswritescode"}
+              .twitter.no-margin
+          %li
+            %a{href: "https://www.linkedin.com/in/jameswritescode"}
+              .linkedin.no-margin
+          %li
+            %a{href: "https://gitlab.com/u/newton"}
+              .gitlab.no-margin
+          %li
+            %a{href: "https://github.com/jameswritescode"}
+              .github.no-margin
+      .col-sm-9.col-md-9
+        %h2.title James Newton
+        %p James is a software developer in Orlando, FL, US.
+        %p He started following GitLab development in 2012 looking for a better git management interface. Needless to say, it was love at first sight. Since then he's has been supporting GitLab users in the freenode IRC channel.
+    .row
+      %hr.hor-line/
+    .teams.row
+      .col-sm-3.col-md-3
+        .core-team-image
+          = image_tag "/images/team/picture_liza.jpg", class: "img-responsive"
+        %ul.core-team-social
+          %li
+            %a{href: "https://twitter.com/creamzzzy"}
+              .twitter.no-margin
+          %li
+            %a{href: "https://gitlab.com/u/creamzy"}
+              .gitlab.no-margin
+      .col-sm-9.col-md-9
+        %h2.title Liza Belyaeva
+        %p Liza is a UX Designer in Hamburg, Germany.
+        %p Liza comes from a maths background, bringing her passion for order and consistency to the design world. With more than seven years of experience in both corporate environments and the startup world she is really excited about delivering meaningful and useful experiences to people in need. Through open source software and a vegan lifestyle she hopes to change this world for the better.
+    .row
+      %p Many core team members did a lot of fixes, improvements and refactoring. The above list indicates some of their specialties but it is not complete.
+      %p
+        GitLab core team members who are no longer active but whose work is very much appreciated can be found on the
+        = succeed "." do
+          %a{href: "/alumni"} core team alumni page
+      %p
+        The GitLab core-team is not bound to any single (not-)for-profit organization.
+        This arrangement is similar to those of the Ruby, Ruby on Rails, Linux and PostgreSQL projects.
+        There is no formal process, team members discuss topics on the
+        %a{href: "https://groups.google.com/forum/#!forum/gitlab-core"} private gitlab-core mailing list
+        and Slack channel.
+        You can get invited for the core team after
+        %a{href: "https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md"} contributing
+        to GitLab for a sustained period of time.
+        You can contribute by coding but also by giving feedback on merge requests, triaging on the issue tracker or helping out on the mailinglist.
+        Core contributors are invited after a proposal from a core-team member that gets two positive responses on the core-team mailing list and no negative ones.

source/culture/index.html.md

+---
+layout: markdown_page
+title: "GitLab Culture"
+---
+
+## Summits
+
+Approximately every 6-9 months, we gather in person to see how tall everyone is (hard to see with video conferencing), and to
+get to know each other better by working and 'playing' together. Here are some
+ [impressions from the Summit in Amsterdam, October 2015](https://about.gitlab.com/2015/11/30/gitlab-summit-2015/).
+
+
+## Internal Feedback
+
+By sending out our Feedback Form (find the link to the "open" form by accessing
+[this "closed" document](https://docs.google.com/document/d/12ZAACGeS2_nz6AFXqf78x9iv2LB_hyX9fcT4s9nJF4M/edit) )
+we gather feedback from the team members anonymously. We then share the main highlights
+and concerns / wishes / things people wonder about with the entire team by discussing
+them during our [Team Call](https://about.gitlab.com/handbook/#team-call) and posting
+all topics that came up along with their responses here (with the exception of
+  [topics](https://about.gitlab.com/handbook/#general-guidelines) that by nature
+  are not shared outside of the company). _The responses may be altered from the original wording in an effort to maintain anonymity, while also maintaining the same spirit and message of the response._
+
+### Feedback from January 2016, and responses
+
+#### "What do you wish we had / What are you wondering about"
+
+1. "Contractor or employee? Worried about job security as a contractor."
+   * We value all team members equally, regardless of the legal arrangement that
+   you have with GitLab. Due to legal restrictions and the difficulty of having
+   people be employees outside of the US or NL (where we have a legal entity), a
+   large portion of the team are contractors (21 out of 46). At GitLab, as everywhere
+   else, job security relies mostly on how you are performing as a team member,
+   and how the company performs as a whole. By the way, the contracts that we use
+   are all viewable on https://about.gitlab.com/handbook/contracts/
+1. "More patience and consideration with ideas from newer people, things are sometimes
+quickly rejected as 'won't work' or 'not interested' without much explanation."
+   * It is difficult to comment on what may have been specific circumstances,
+   but if you have felt that your idea was rejected too quickly or without explanation,
+   then please know that this was not intended to be unkind or harsh. There are
+   many ideas and for the sake of efficiency we give minimal reasoning in responding.
+   This is also due to the nature of asynchronous communication where it is hard
+   to tell if an answer is extensive enough to satisfy the question. If you feel
+   that an idea is being rejected rather quickly, you **can** and **should**
+   request more explanation. This might lead to a fruitful discussion and a reconsideration.
+ 1. "Wish we had more time"/ "Wonder if sometimes we go too fast and should go slower
+ to focus on quality and testing more"
+    * Please make sure you take enough
+    [time off](https://about.gitlab.com/handbook/#paid-time-off) to recharge!
+    Having a rapid release cycle contributes to increasing quality over time being able to iterate faster. For
+    particular concerns in an individual issue, please raise your concerns in the
+    issue. Because GitLab has gotten very popular the absolute amount of bugs might be increasing.
+    But to individual users it feels like we've "[been squashing bugs and releasing
+    features rapidly while also decreasing the number of regressions introduced and
+    improving their test suit across the board](https://news.ycombinator.com/item?id=11039966)".
+    Obviously quality is and will always be a top concern, especially code quality
+    since that enables better testing, faster fixes, and more contributions.
+1. "Better supervision in the first two months"
+   * Always be sure to reach out to your manager if you feel that you need more guidance. Your peers are a Slack message away.
+1. "Maybe a more competitive salary"
+   * From the [handbook](https://about.gitlab.com/handbook/#general-guidelines): "If you are unhappy with anything (your duties, your colleague, your boss, your salary, your location, your computer) please let your boss, or the CEO, know as soon as you realize it. We want to solve problems while they are small."
+1. "A step between review/QA and deployment."
+   * Review happens through merge requests, and QA happens as part of the release process. We can't think of anything else at the moment that would not introduce gates that cause delay and inefficiency.
+1. "Off-site meetings during the year and/or team-specific summits, like a hackathon"
+   * We had a Summit in Oct'15, and are having one in May'16. We aim to have these every 6-9 months. We are thinking about organizing a hackathon during the [Summit](https://gitlab.com/summits/Austin-Summit-2016-project/blob/master/Proposed_Activities.md); please upvote if you want it to happen!
+1. "We share a lot about our software 'side'; can we share more about our other 'sides' (like how marketing does marketing) in a "team blog"? This would help in hiring awesome people!"
+   * We love blog posts and sharing all of GitLab's 'sides'. Please channel your inner need to write a blog post (or part of it!) on our [blog](https://gitlab.com/gitlab-com/blog-posts/issues) repo.
+1. "Additional training for dev people, maybe? Specific suggestions for topics include agile coding, code quality, and there is a suggestion for Robert "Uncle Bob " Marcin (https://sites.google.com/site/unclebobconsultingllc/) for code quality
+  * After some research within the team there was a greater interest in a "birds of a feather" gathering than formal training. We're looking to do this during our Summit trip to Austin.
+1. "What features are we planning? I hear about price changes and optional features?"
+  * See [issue about pricing](https://dev.gitlab.org/gitlab/organization/issues/522) and see /direction and GitLab Option List Doc for optional features.
+1. "How are we doing? How does the Board see it? Can we keep up the growth and the Sales?"
+  * Khosla is really happy so far. Keeping up growth depends on demand generation
+1. "If we are sometimes too open and too transparent in a way that hurts us?"
+  * So far the only negative thing is that we suspect that competitors release their stuff early to preempt us, we think it is great that they are adjusting their schedule to ours!
+1. "Creating/using a standard for interviewing candidates."
+  * Good idea, a lot of us use standard interview questions https://about.gitlab.com/handbook/hiring/#interview-questions but merge requests are welcome.
+1.  "More formality in development process."
+  * What form of formality? We welcome changes that don't reduce our productivity. Potentially we could start using issue weights more to gauge the load.
+
+#### "What do you like about working here?"
+
+1. A lot of love for the team
+   * Keywords people used to describe their fellow team members are: 'talented,
+   caring, teamwork, approachable, honest, frank, smart, brilliant, skilled,
+   team spirit'.
+1. Great product
+   * Four people mentioned it specifically, and this one sums it up nicely: "Working
+   on a product that I actually love to use". Respondents also mentioned the fast pace of development.
+1. Open Source
+   * Respondents value being involved in Open Source, with phrases such as: 'proving that open source is awesome and working with the rest of the community, working on open source while getting paid for it is a dream job!'
+1. Freedom and opportunity
+   * We are a remote-first company and our team members like: 'being remote-first, working from home, having personal independence, the freedom to choose what to work on, the freedom that you don't get in a corporate office environment, flexibility to get things done, slim process, slack oriented'
+   * People also mentioned the opportunity to learn, and the massive opportunity that the project and the company has.
+1. Team dynamic
+   * Several people mentioned that they really like the team dynamic, specifically: 'the support that you need is there, you have the ability to take on multiple hats and responsibilities, everyone and everything is open to constant improvement, ability to collaborate even though we're remote, we're remote but still have a great sense of "team", love the cross discipline collaboration that goes on every day'
+
+### Feedback from the GitLab team - September 2015
+
+Summarized in this presentation about ["Stuff the GitLab team likes and does not
+like"](https://docs.google.com/a/gitlab.com/presentation/d/1h9P8Vf_6fzPbLCCahvwtIF5j_cH54zsv9iRSseVZzl0/edit?usp=sharing),
+here is what the team said in September of 2015.
+
+#### What we love about working at GitLab
+
+Freedom, flexibility, enthusiasm, passion, great, smart, engaging,
+enjoy teaching, feels like a family, great dynamic, supportive,
+approachable execs, supportive, transparency, speed of innovation, remote working,
+company sponsored training, great Summit in Amsterdam.
+
+_and also_
+
+Great product, ability to create new processes,
+company growth, no burocracy, no high pressure, opportunity, our growth,
+the challenge of maintaining quality of people, product, brand etc,
+laser focus on improving collaboration through social coding, market adoption,
+our work is public so we can talk about it, and our ability to create new processes.
+
+#### What we wish we had or what we want to be doing & What we’re doing about it
+
+1. More team members.
+   * We’re hiring
+1. Bigger feature gap between CE and EE.
+   * Current plan is to have one EE feature added per release, so over time the difference will grow.
+1. More summits.
+   * Current plan is to have a summit every 6-9 months.
+1. Better onboarding.
+   * We're working on this with GitLabUniversity (GLU) content, continuous improvements to documentation and the handbook
+1. Customer success events, starting in the Bay Area.
+   * Cool idea, start an issue and make it happen!
+1. Coaching on Agile and Lean approaches for Engineering team.
+   * Great idea, we'll look into it. Suggestions are welcome.
+1. A scale with happiness of last work week for feedback.
+   * We've working this into our feedback from in a different setting for now.
+1. Global presence of Service Engineers, and dedicated trainer and training materials.
+   * We're working on this through hiring. Also, we have high hopes of GLU, ongoing content creation, etc. to help out here.
+
+#### What we’re wondering about & the answers to our thoughts
+
+1. Stock options: terms, conditions
+   * Does the handbook answer your questions? (https://about.gitlab.com/handbook/stock-options). Please feel free to ask Paul.
+1. What the company will look like 3, 6, 12 months from now? (community-ish, enterprise-ish)
+   * The community and people using GitLab will keep growing. 12 months from now
+  we'll answer all questions from the community on all platforms (from forum to
+  Stack Overflow), we'll have a proper swag shop and have more developer oriented
+  content (blog posts, video's).
+   * Enterprise wise we'll have double the features we have now, a twice as large sales
+team, and many add-ons. Feel free to ask something more specific if you need more
+detail. And of course try to shape it as you think it should look.
+1. How committed are we to building EE features and having significant releases  each month?
+   * Very committed. At least one tentpole EE feature every month. Next 3 releases contain 2 or 3 each! https://about.gitlab.com/direction/
+1. Sales team hiring plan
+   * We're hiring but it is not a priority until everyone is up to speed and trained. But we expect that to happen soon, and the marketing machine will come up to speed soon, after which hiring becomes a priority.

source/development/index.html.haml

+---
+layout: default
+title: Development
+suppress_header: true
+extra_css:
+  - development.css
+---
+.wrapper
+  .development-picture-container
+    .development-overlay
+      .development-content
+        %h1 Development
+        %ul
+          %li If you are missing some functionality in GitLab you can sponsor the development of it.
+          %li After you send in the form below we will check if the feature is acceptable to include in GitLab. If so we will first email back with a minimum cost estimate. This is to make sure the expectations of the work that is involved are realistic.
+          %li If the minimum estimate matches your expectations we will work on a detailed estimate. If you accept the detailed estimate we will give you an estimated release date and start the work.
+          %li
+            We will inform you when the feature is ready and
+            %a{href: "https://gitlab.com/gitlab-org/gitlab-ce/blob/a88225b7689ab87b49908db23e1bebf1c7ea09d3/CHANGELOG#L8"} note your sponsorship in the Changelog
+            (unless you ask us not to, no problem). From then on your feature is a part of GitLab and will probably be maintained without any additional cost to you.
+  .centered-form.development-form
+    %script{src: "//app-ab13.marketo.com/js/forms2/js/forms2.min.js"}
+    %form#mktoForm_1063
+    :javascript
+      MktoForms2.loadForm("//app-ab13.marketo.com", "194-VVC-221", 1063, function(form) {
+          form.onSuccess(function(values, followUpUrl) {
+
+            form.getFormElem().hide();
+            document.getElementById('confirmform').style.visibility = 'visible';
+
+            ga('send', 'pageview');
+            ga('send', 'event', 'form', 'submit', 'development request');
+            return false;
+          });
+      });
+    #confirmform{style: "visibility:hidden;"}
+      %p Submission received!

source/direction/template.html.md.erb

+---
+layout: markdown_page
+title: "GitLab Direction"
+---
+
+This page describes the direction and roadmap for GitLab.
+It is organized from the short to the long term.
+
+## Your contributions
+
+GitLab's direction is determined by the code that is sent by our [contributors](http://contributors.gitlab.com/).
+We continually merge code to be released in the next version.
+Contributing is the best way to get a feature you want included.
+On [our issue tracker for CE](https://gitlab.com/gitlab-org/gitlab-ce/issues)
+and [EE](https://gitlab.com/gitlab-org/gitlab-ee/issues),
+many requests are made for features and changes to GitLab.
+The ones with the
+[status accepting merge requests](https://gitlab.com/gitlab-org/gitlab-ce/issues?milestone_id=&scope=all&sort=created_desc&state=opened&utf8=%E2%9C%93&assignee_id=&author_id=&milestone_title=&label_name=Accepting+Merge+Requests&weight=)
+are pre-approved.
+Of course before any code is merged it still has to meet the
+[contribution acceptance criteria](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#contribution-acceptance-criteria).
+
+## What our customers want
+
+At GitLab the company we try to make what our users and we need (many of us are or used to be developers).
+If a customer requests a feature, it carries extra weight.
+Due to our short release cycle we can ship simple feature requests (for example an API extension) within one to two months.
+
+## Previous releases
+
+On our [release list page](https://about.gitlab.com/release-list/) you can find an overview of the most important features of recent releases and a links to the release blog posts.
+
+## Next releases
+
+GitLab releases a new version every single month on the 22nd.
+Note that we often move things around, do things that are not listed and don't do things that are listed.
+This page is always in draft, some of the things on it might not every be in GitLab.
+EE options are indicated with 'EE option' in the issue title, this is our best estimate of what will be options, it is not definitive.
+Also the list below not include any contributions from outside GitLab the company.
+The bullets list the tentpole features; the most important features of upcoming releases.
+The CE and EE to the right of the version number link to all planned issues for that version.
+
+<%= direction %>
+
+## Wishlist <a name="wishlist"></a>
+
+Below are features we'd really like to see in GitLab.
+This list is not prioritized. We invite everyone to join the discussion by clicking the wishlist item that is of interest to you.
+Feel free to comment, vote up or down any issue or just follow the conversation.  For GitLab sales, please add a link to the account in Salesforce.com that has expressed interest in a wishlist feature.
+We very much welcome contributions that implement any of these things.
+
+### Major Wins
+
+- [Translations](https://gitlab.com/gitlab-org/gitlab-ce/issues/4012)
+- [Nested Groups](https://gitlab.com/gitlab-org/gitlab-ce/issues/2772)
+- [Resolve merge conflicts in the web interface](https://gitlab.com/gitlab-org/gitlab-ce/issues/3567)
+- [Multithreaded application server](https://gitlab.com/gitlab-org/gitlab-ce/issues/3592)
+- [Realtime editing of the issue/MR description field](https://gitlab.com/gitlab-org/gitlab-ce/issues/4199)
+- [Handle incoming emails with support questions in issues](https://gitlab.com/gitlab-org/gitlab-ee/issues/149)
+- [Cherry-pick MR into any branch in the web interface](https://gitlab.com/gitlab-org/gitlab-ce/issues/12785)
+- [Allow pusing to multiple servers](https://gitlab.com/gitlab-org/gitlab-ee/issues/276)
+
+### Usability
+
+- [See all forked projects of one project](https://gitlab.com/gitlab-org/gitlab-ce/issues/2406)
+- [Email actions](https://gitlab.com/gitlab-org/gitlab-ce/issues/4273)
+- [Improved emails on push](https://gitlab.com/gitlab-org/gitlab-ee/issues/146)
+- [Autocomplete all users](https://gitlab.com/gitlab-org/gitlab-ce/issues/3872)
+- [Ship octotree as part of GitLab](https://gitlab.com/gitlab-org/gitlab-ce/issues/13723)
+
+### Code Review
+
+- [See current HEAD in outdated discussion](https://gitlab.com/gitlab-org/gitlab-ce/issues/3502)
+- [Allow cross server merge requests](https://gitlab.com/gitlab-org/gitlab-ce/issues/4013)
+- [Ability to checkout the result of MR available before merging](https://gitlab.com/gitlab-org/gitlab-ce/issues/2765)
+- [Transactional MR comments](https://gitlab.com/gitlab-org/gitlab-ce/issues/3364)
+
+### Issue tracker
+
+- [Filter by more than one label](https://gitlab.com/gitlab-org/gitlab-ce/issues/989)
+- [Time tracking](https://gitlab.com/gitlab-org/gitlab-ee/issues/78)
+- [Labels should be visible in Milestone view](https://gitlab.com/gitlab-org/gitlab-ce/issues/3276)
+
+### Productivity
+
+- [Change notification setting](https://gitlab.com/gitlab-org/gitlab-ce/issues/3778)
+- [Add more default views](https://gitlab.com/gitlab-com/www-gitlab-com/edit/master/source/direction/index.md)
+
+### Version Control for Everything
+
+- [Distributed code-reviews and issues](https://gitlab.com/gitlab-org/gitlab-ce/issues/4084)
+- [Render PSD files](https://gitlab.com/gitlab-org/gitlab-ce/issues/13189)
+- [Snippets backed by a git repository to enable cloning and revisions](https://gitlab.com/gitlab-org/gitlab-ce/issues/13426)
+- [Binary file lock (EE option)](https://gitlab.com/gitlab-org/gitlab-ce/issues/7889)
+
+### Performance
+
+- [Handle errors before they give a 500](https://gitlab.com/gitlab-org/gitlab-ce/issues/4665)
+- [Get rid of the large authorized keys (SSH) file](https://gitlab.com/gitlab-org/gitlab-git-http-server/issues/2#note_1983654)
+- [Participants table](https://gitlab.com/gitlab-org/gitlab-ce/issues/3965)
+- [Reduce memory leaks](https://gitlab.com/gitlab-org/gitlab-ce/issues/3700)
+
+### CI
+
+- [Runner Autoscale](https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/318)
+- [Document dependent builds / pipeline triggers](https://gitlab.com/gitlab-org/gitlab-ce/issues/3432)
+- [Deploy your branch button](https://gitlab.com/gitlab-org/gitlab-ce/issues/3286)
+- [Automatically give code quality metrics in the merge request](https://gitlab.com/gitlab-org/gitlab-ce/issues/4044)
+- [Automatic Docker image cleanup](https://gitlab.com/ayufan/gitlab-runner-docker-cleanup/issues/1)
+- [Show code coverage in diffs with colored horizontal bar](https://gitlab.com/gitlab-org/gitlab-ce/issues/4073)
+- [A/B testing of branches with GitLab Pages (EE option)](https://gitlab.com/gitlab-org/gitlab-ee/issues/117)
+- [Code coverage graphs and adding more metrics (EE option)](https://gitlab.com/gitlab-org/gitlab-ce/issues/13409)
+- Pre-testing of merged results (EE option)
+- Feature deploy (measure KPI and use feature toggles) (EE option)
+- Automatic environment per merge request (EE option)
+- Automatic A/B testing of branches (EE option)
+- Configuration management integration (Chef, Puppet, Ansible, Salt) (EE option)
+
+### Access control
+
+- Directory access management (EE option)
+- Turnstile security that is self learning and location dependent (EE option)
+- Automated vulnerability scanner (EE option)
+
+### Tracebility
+
+- Watermarking of binaries that are downloaded (EE option)
+- Build traceability (trace binary to source) (EE option)
+- New code license detection (scans the internet) (EE option)
+
+### Analytics
+
+- Advanced compliance reporting on access rights (EE option)
+- Advanced analytics features (EE option)
+
+### Reporting
+
+- Aggregated time reports (time spent per project, etc.) (EE option)
+- Management dashboard (time spend per phase, cycle time and velocity) (EE option)
+
+### Scope <a name="scope"></a>
+
+To realize [our vision](#vision) we plan to ship the following stack of tools:
+
+1. **Chat** conversation => Mattermost, [Rocket.Chat](http://rocket.chat/) if they can make it [work with PostgreSQL](https://github.com/RocketChat/Rocket.Chat/issues/533)
+1. **Issue** creation => GitLab Issues
+1. **Scrum** board to plan => [Huboard](https://huboard.com/) for which there is a [bounty](https://github.com/huboard/huboard/issues/276)
+1. **Development** => [Browser IDE](https://gitlab.com/gitlab-org/gitlab-ce/issues/12759)
+1. **Version control** => GitLab Repo
+1. **Continuous integration** => GitLab CI
+1. **Code review** => GitLab Merge Requests
+1. **Deploy** to production => [GitLab Deploy](https://gitlab.com/gitlab-org/gitlab-ce/issues/3286)
+1. **Chatops** to check => [Hubot](https://hubot.github.com/) which has a [Merge Request](https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/564) or [Lita](https://www.lita.io/)
+1. **Wiki** to document => GitLab Wiki
+
+We're still deciding if application performance monitoring is in our scope, for example with Grafana and InfluxDB.
+
+We plan to ship all of the above in our Omnibus package.
+
+Things that are outside our scope are:
+
+1. **PaaS** although we do want to use [GitLab Deploy](https://gitlab.com/gitlab-org/gitlab-ce/issues/3286) to deploy to CloudFoundry, OpenStack, OpenShift, Kubernetes, Mesos DCOS, Docker Swarm, Atlas/Terraform, [Nomad](https://nomadproject.io/), [Deis](http://deis.io/), [Convox](http://www.convox.com/), [Flynn](https://flynn.io/), [Tutum](https://www.tutum.co/), [GiantSwarm](https://giantswarm.io/), [Rancher](https://github.com/rancher/rancher/blob/master/README.md)
+1. **Configuration management** although we do want to upload cookbooks, manifests, playbooks, and modules for respectively Chef, Puppet, Ansible, and Salt.
+1. **Log monitoring** (ELK stack, Graylog, Splunk)
+1. **Infrastructure monitoring** (CheckMK, Nagios, Sensu)
+1. **Error monitoring** (Sentry, Airbrake, Bugsnag)
+1. **Network** (Openflow, VMware NSX, Cisco ACI)
+1. **Incident notification** (Pagerduty, Pingdom)
+1. **Network security** (Nmap, rkhunter, Metasploit, Snort, OpenVAS, OSSEC)
+
+### We would love to partner with
+
+- Scrum boards: We already support [some of them](https://about.gitlab.com/applications/#scrum-boards) but would love for [Waffle.io](https://waffle.io/), and [Zenhub.io](https://www.zenhub.io/) to support GitLab too.
+- [CodeClimate](https://gitlab.com/gitlab-org/gitlab-ce/issues/4044)
+- [Oracle database support (EE)](https://gitlab.com/gitlab-org/gitlab-ee/issues/96)
+- Browser IDE's to ship GitLab with them and to have button to open them from GitLab: Koding, Nitrous.io, [Cloud9](https://c9.io/blog/cloud9-template-days/), CodeAnywhere, Codio, and CodeEnvy
+
+## Vision <a name="vision"></a>
+
+From development teams to marketing organizations, everyone needs to collaborate on
+digital content. Content should be open to suggestions by a wide number of
+potential contributors. Open contribution can be achieved by using a mergeable
+file format and distributed version control. The vision of GitLab is to **allow
+everyone to collaborate on all digital content** so people can cooperate
+effectively and achieve better results, faster.
+
+Ideas flow though many stages before they are realized: chat, issue, sprint,
+IDE, commit, CI, review, acceptance, deployment, documentation. Stitching all these stages
+together can be done in many different ways. You can have a marketplace of
+proprietary apps from different suppliers or use a suite of products developed
+in isolation. We believe that an **opinionated and integrated set of tools based
+on convention over configuration** offers superior user experience. The
+advantage can be quoted from the [Wikipedia page for convention over
+configuration](https://en.wikipedia.org/wiki/Convention_over_configuration):
+"decrease the number of decisions that developers need to make, gaining
+simplicity, and not necessarily losing flexibility". In GitLab you only have to
+specify unconventional aspects of your workflow, the rest will be a smooth
+experience. That smooth experience should go from informal chat, to creating an
+issue, coding it in an IDE, committing the code, running CI tests, doing a code
+review, and deploying in different environments.
+
+We admire other convention over configuration tools like [Ruby on
+Rails](http://rubyonrails.org/) (that doctrine of which perfectly describe the [value of integrated systems](http://rubyonrails.org/doctrine#integrated-systems), [Ember](http://emberjs.com/), and
+[Heroku](https://www.heroku.com/), and strive to offer the same advantages for a
+continuous delivery of software.
+
+The integrated exeprience doesn't mean we'll never
+do a marketplace, in fact this is the way [GitLab.com will be free
+forever](https://about.gitlab.com/gitlab-com/#why-gitlab-com-will-be-free-forever).
+But we believe that an [integrated set of tools provides a better user experience that a modular approach](https://stratechery.com/2013/clayton-christensen-got-wrong/).
+The open source nature of GitLab ensures that that we can combine great open source products and that everyone can contribute to a feature set that is [more complete than other tools](https://about.gitlab.com/comparison/).
+We'll focus on making all the parts work well together to create a better user experience.
+
+Because GitLab is open source the enhancements can become part of
+the codebase instead of being external. This ensures the automated tests for all
+functionality are continually run, ensuring that additions always work. It also
+ensures GitLab can continue to evolve with it's additions instead of being bound
+to an API that is hard to change and that resists refactoring. This
+ensures we have many years of quality code and great monthly releases ahead of
+us.

source/disclosure/index.html.md

+---
+layout: markdown_page
+title: Responsible Disclosure Policy
+---
+
+Please email security@gitlab.com to report any security vulnerabilities. Please
+refrain from requesting compensation for reporting vulnerabilities. We will
+acknowledge receipt of your vulnerability report and send you regular updates
+about our progress. If you want we will [publicly acknowledge](https://about.gitlab.com/vulnerability-acknowledgements/)
+ your responsible disclosure. You may also send us your report via [HackerOne](https://hackerone.com/gitlab).  
+
+
+You are not allowed to search for vulnerabilities on GitLab.com itself. GitLab
+is open source software, you can install a copy yourself and test against that.
+If you want to perform testing that might break things please contact us to
+arrange access to a staging server.
+
+
+If you want to encrypt your disclosure email please email us to ask for our PGP key.

source/dmca/index.html.md

+---
+layout: markdown_page
+title: DMCA Policy
+---
+
+If you feel your intellectual property rights are being violated by a GitLab.com user, please email support@gitlab.com stating the user (can be found in the url), a description of and a url to the content you believe is yours, and proof of your intellectual property.
+
+We will review your claim and take whatever action we deem appropriate, including removal of the challenged content from the website.