Skip to content
Snippets Groups Projects
Commit 0d9d20aa authored by Robert Speicher's avatar Robert Speicher
Browse files

Add the new site :sparkles:

parent 1dd646f1
No related branches found
No related tags found
No related merge requests found
Pipeline #
Expand all Hide whitespace changes
Inline Side-by-side
Showing
with 1797 additions and 0 deletions
data/platforms.yml 0 → 100644
+ 85
− 0
View file @ 0d9d20aa
- name: ubuntu1204
long_name: Ubuntu 12.04
download_command: curl -sS https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | sudo bash
install_commands: |
sudo apt-get install gitlab-ce
install_commands_manual: |
curl -LJO https://packages.gitlab.com/gitlab/gitlab-ce/packages/ubuntu/precise/gitlab-ce-XXX.deb/download
dpkg -i gitlab-ce-XXX.deb
dependency_commands: |
sudo apt-get install curl openssh-server ca-certificates postfix
- name: ubuntu1404
long_name: Ubuntu 14.04 (recommended, for 15.04 select and download the package manually)
download_command: curl -sS https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | sudo bash
install_commands: |
sudo apt-get install gitlab-ce
install_commands_manual: |
curl -LJO https://packages.gitlab.com/gitlab/gitlab-ce/packages/ubuntu/trusty/gitlab-ce-XXX.deb/download
dpkg -i gitlab-ce-XXX.deb
dependency_commands: |
sudo apt-get install curl openssh-server ca-certificates postfix
- name: debian7
long_name: Debian 7
download_command: curl -sS https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | sudo bash
install_commands: |
sudo apt-get install gitlab-ce
install_commands_manual: |
curl -LJO https://packages.gitlab.com/gitlab/gitlab-ce/packages/debian/wheezy/gitlab-ce-XXX.deb/download
dpkg -i gitlab-ce-XXX.deb
dependency_commands: |
sudo apt-get install curl openssh-server ca-certificates postfix
- name: debian8
long_name: Debian 8
download_command: curl -sS https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | sudo bash
install_commands: |
sudo apt-get install gitlab-ce
install_commands_manual: |
curl -LJO https://packages.gitlab.com/gitlab/gitlab-ce/packages/debian/jessie/gitlab-ce-XXX.deb/download
dpkg -i gitlab-ce-XXX.deb
dependency_commands: |
sudo apt-get install curl openssh-server ca-certificates postfix
- name: centos6
long_name: CentOS 6 (and RedHat/Oracle/Scientific Linux 6)
download_command: curl -sS https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.rpm.sh | sudo bash
install_commands: |
sudo yum install gitlab-ce
install_commands_manual: |
curl -LJO https://packages.gitlab.com/gitlab/gitlab-ce/packages/el/6/gitlab-ce-XXX.rpm/download
rpm -i gitlab-ce-XXX.rpm
dependency_commands: |
sudo yum install curl openssh-server openssh-clients postfix cronie
sudo service postfix start
sudo chkconfig postfix on
firewall_open: sudo lokkit -s http -s ssh
- name: centos7
long_name: CentOS 7 (and RedHat/Oracle/Scientific Linux 7)
download_command: curl -sS https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.rpm.sh | sudo bash
install_commands: |
sudo yum install gitlab-ce
install_commands_manual: |
curl -LJO https://packages.gitlab.com/gitlab/gitlab-ce/packages/el/7/gitlab-ce-XXX.rpm/download
rpm -i gitlab-ce-XXX.rpm
dependency_commands: |
sudo yum install curl policycoreutils openssh-server openssh-clients
sudo systemctl enable sshd
sudo systemctl start sshd
sudo yum install postfix
sudo systemctl enable postfix
sudo systemctl start postfix
firewall_open: |
sudo firewall-cmd --permanent --add-service=http
sudo systemctl reload firewalld
- name: raspberrypi2
long_name: Raspberry PI 2 on Raspbian
download_command: |
sudo curl -sS https://packages.gitlab.com/install/repositories/gitlab/raspberry-pi2/script.deb.sh | sudo bash
install_commands: |
sudo apt-get install gitlab-ce
install_commands_manual: |
curl -LJO https://packages.gitlab.com/gitlab/raspberry-pi2/packages/raspbian/(wheezy|jessie)/gitlab-ce-XXX.deb/download
dpkg -i gitlab-ce-XXX.deb
dependency_commands: |
sudo apt-get install curl openssh-server ca-certificates postfix apt-transport-https
curl https://packages.gitlab.com/gpg.key | sudo apt-key add -
data/platforms_ee.yml 0 → 100644
+ 61
− 0
View file @ 0d9d20aa
- name: ubuntu1204
long_name: Ubuntu 12.04
download_command: curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ee/script.deb.sh | sudo bash
install_commands: |
sudo apt-get install gitlab-ee
install_commands_manual: dpkg -i gitlab-ee-XXX.deb
dependency_commands: |
sudo apt-get install curl openssh-server ca-certificates postfix
- name: ubuntu1404
long_name: Ubuntu 14.04 (recommended, for 15.04 select and download the package manually)
download_command: curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ee/script.deb.sh | sudo bash
install_commands: |
sudo apt-get install gitlab-ee
install_commands_manual: dpkg -i gitlab-ee-XXX.deb
dependency_commands: |
sudo apt-get install curl openssh-server ca-certificates postfix
- name: debian7
long_name: Debian 7
download_command: curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ee/script.deb.sh | sudo bash
install_commands: |
sudo apt-get install gitlab-ee
install_commands_manual: dpkg -i gitlab-ee-XXX.deb
dependency_commands: |
sudo apt-get install curl openssh-server ca-certificates postfix
- name: debian8
long_name: Debian 8
download_command: curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ee/script.deb.sh | sudo bash
install_commands: |
sudo apt-get install gitlab-ee
install_commands_manual: dpkg -i gitlab-ee-XXX.deb
dependency_commands: |
sudo apt-get install curl openssh-server ca-certificates postfix
- name: centos6
long_name: CentOS 6 (and RedHat/Oracle/Scientific Linux 6)
download_command: curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ee/script.rpm.sh | sudo bash
install_commands: |
sudo yum install gitlab-ee
install_commands_manual: rpm -i gitlab-ee-XXX.rpm
dependency_commands: |
sudo yum install curl openssh-server postfix cronie
sudo service postfix start
sudo chkconfig postfix on
firewall_open: sudo lokkit -s http -s ssh
- name: centos7
long_name: CentOS 7 (and RedHat/Oracle/Scientific Linux 7)
download_command: curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ee/script.rpm.sh | sudo bash
install_commands: |
sudo yum install gitlab-ee
install_commands_manual: rpm -i gitlab-ee-XXX.rpm
dependency_commands: |
sudo yum install curl openssh-server
sudo systemctl enable sshd
sudo systemctl start sshd
sudo yum install postfix
sudo systemctl enable postfix
sudo systemctl start postfix
firewall_open: |
sudo firewall-cmd --permanent --add-service=http
sudo systemctl reload firewalld
data/promo.yml 0 → 100644
+ 2
− 0
View file @ 0d9d20aa
text: Join us for a live GitLab Tutorial on GitLab CI - April 14th!
link: //page.gitlab.com/apr-2016-gitlab-intro-ci-webcast.html
data/site.yml 0 → 100644
+ 3
− 0
View file @ 0d9d20aa
url: https://about.gitlab.com
title: GitLab
repo: https://gitlab.com/gitlab-com/www-gitlab-com/
data/suchaws.yml 0 → 100644
+ 27
− 0
View file @ 0d9d20aa
- name: US West (Oregon)
image: ami-1b46672b
id: uw1
- name: US East (N. Virginia)
image: ami-3cffac54
id: ue
- name: US West (N. California)
image: ami-d3df3a97
id: uw2
- name: EU (Ireland)
image: ami-df6ef9a8
id: eui
- name: EU (Frankfurt)
image: ami-f80331e5
id: euf
- name: Asia Pacific (Singapore)
image: ami-947c4bc6
id: aps
- name: Asia Pacific (Tokyo)
image: ami-897a9889
id: apt
- name: Asia Pacifc (Sydney)
image: ami-4f90e675
id: apsy
- name: South America (São Paulo)
image: ami-9d299780
id: sa
data/team.yml 0 → 100644
+ 783
− 0
View file @ 0d9d20aa
This diff is collapsed.
data/testimonials.yml 0 → 100644
+ 12
− 0
View file @ 0d9d20aa
- name: Business Insider
logo: /images/testimonials/bi.svg
quote: This 'well-kept' secret for programmers is suddenly popping up in the Fortune 500
link: http://www.businessinsider.com/gitlab-ceo-sytse-sid-sijbrandij-interview-2015-10
- name: The Next Web
logo: /images/testimonials/user_99.svg
quote: Code collaboration platform GitLab acquires rival Gitorious
link: http://thenextweb.com/insider/2015/03/03/gitlab-acquires-rival-gitorious-will-shut-june-1/
- name: Tech Crunch
logo: /images/testimonials/user_100.svg
quote: YC-Backed GitLab Is Like GitHub But For Enterprise
link: http://techcrunch.com/2015/03/03/the-great-git-debate/
doc/legal/corporate_contributor_license_agreement.md 0 → 100644
+ 25
− 0
View file @ 0d9d20aa
You accept and agree to the following terms and conditions for Your present and future Contributions submitted to GitLab.com. Except for the license granted herein to GitLab.com and recipients of software distributed by GitLab.com, You reserve all right, title, and interest in and to Your Contributions.
1. Definitions.
"You" (or "Your") shall mean the copyright owner or legal entity authorized by the copyright owner that is making this Agreement with GitLab.com. For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single Contributor. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"Contribution" shall mean the code, documentation or other original works of authorship expressly identified in Schedule B, as well as any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to GitLab.com for inclusion in, or documentation of, any of the products owned or managed by GitLab.com (the "Work"). For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to GitLab.com or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, GitLab.com for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution."
2. Grant of Copyright License. Subject to the terms and conditions of this Agreement, You hereby grant to GitLab.com and to recipients of software distributed by GitLab.com a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works.
3. Grant of Patent License. Subject to the terms and conditions of this Agreement, You hereby grant to GitLab.com and to recipients of software distributed by GitLab.com a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted. If any entity institutes patent litigation against You or any other entity (including a cross-claim or counterclaim in a lawsuit) alleging that your Contribution, or the Work to which you have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.
4. You represent that You are legally entitled to grant the above license. You represent further that each employee of the Corporation designated on Schedule A below (or in a subsequent written modification to that Schedule) is authorized to submit Contributions on behalf of the Corporation.
5. You represent that each of Your Contributions is Your original creation (see section 7 for submissions on behalf of others).
6. You are not expected to provide support for Your Contributions, except to the extent You desire to provide support. You may provide support for free, for a fee, or not at all. Unless required by applicable law or agreed to in writing, You provide Your Contributions on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.
7. Should You wish to submit work that is not Your original creation, You may submit it to GitLab.com separately from any Contribution, identifying the complete details of its source and of any license or other restriction (including, but not limited to, related patents, trademarks, and license agreements) of which you are personally aware, and conspicuously marking the work as "Submitted on behalf of a third-party: [named here]".
8. It is your responsibility to notify GitLab.com when any change is required to the list of designated employees authorized to submit Contributions on behalf of the Corporation, or to the Corporation's Point of Contact with GitLab.com.
---------------------------------------
This text is licensed under the [Creative Commons Attribution 3.0 License](http://creativecommons.org/licenses/by/3.0/) and the original source is the Google Open Source Programs Office.
doc/legal/individual_contributor_license_agreement.md 0 → 100644
+ 25
− 0
View file @ 0d9d20aa
You accept and agree to the following terms and conditions for Your present and future Contributions submitted to GitLab.com. Except for the license granted herein to GitLab.com and recipients of software distributed by GitLab.com, You reserve all right, title, and interest in and to Your Contributions.
1. Definitions.
"You" (or "Your") shall mean the copyright owner or legal entity authorized by the copyright owner that is making this Agreement with GitLab.com. For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single Contributor. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"Contribution" shall mean any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to GitLab.com for inclusion in, or documentation of, any of the products owned or managed by GitLab.com (the "Work"). For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to GitLab.com or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, GitLab.com for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution."
2. Grant of Copyright License. Subject to the terms and conditions of this Agreement, You hereby grant to GitLab.com and to recipients of software distributed by GitLab.com a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works.
3. Grant of Patent License. Subject to the terms and conditions of this Agreement, You hereby grant to GitLab.com and to recipients of software distributed by GitLab.com a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted. If any entity institutes patent litigation against You or any other entity (including a cross-claim or counterclaim in a lawsuit) alleging that your Contribution, or the Work to which you have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.
4. You represent that you are legally entitled to grant the above license. If your employer(s) has rights to intellectual property that you create that includes your Contributions, you represent that you have received permission to make Contributions on behalf of that employer, that your employer has waived such rights for your Contributions to GitLab.com, or that your employer has executed a separate Corporate CLA with GitLab.com.
5. You represent that each of Your Contributions is Your original creation (see section 7 for submissions on behalf of others). You represent that Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which you are personally aware and which are associated with any part of Your Contributions.
6. You are not expected to provide support for Your Contributions, except to the extent You desire to provide support. You may provide support for free, for a fee, or not at all. Unless required by applicable law or agreed to in writing, You provide Your Contributions on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON- INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.
7. Should You wish to submit work that is not Your original creation, You may submit it to GitLab.com separately from any Contribution, identifying the complete details of its source and of any license or other restriction (including, but not limited to, related patents, trademarks, and license agreements) of which you are personally aware, and conspicuously marking the work as "Submitted on behalf of a third-party: [[]named here]".
8. You agree to notify GitLab.com of any facts or circumstances of which you become aware that would make these representations inaccurate in any respect.
---------------------------------------
This text is licensed under the [Creative Commons Attribution 3.0 License](http://creativecommons.org/licenses/by/3.0/) and the original source is the Google Open Source Programs Office.
doc/patch_release_blog_template.html.md 0 → 100644
+ 41
− 0
View file @ 0d9d20aa
---
layout: post
title: "GitLab X.Y.Z Released"
date: YYYY-MM-DD
comments: true
author: GitLab
author_twitter: gitlab
---
Today we are releasing version X.Y.Z for GitLab Community Edition (CE) and
Enterprise Edition (EE).
It includes the following fixes:
- **CE/EE:**
- **EE:**
<!-- more -->
## Upgrade barometer
This version does not include any new migrations, and should not require any
downtime.
Please be aware that by default the Omnibus packages will stop, run migrations,
and start again, no matter how “big” or “small” the upgrade is. This behavior
can be changed by adding a [`/etc/gitlab/skip-auto-migrations`
file](http://doc.gitlab.com/omnibus/update/README.html).
## Updating
To update, check out our [update page](https://about.gitlab.com/update).
## Enterprise Edition
Interested in GitLab Enterprise Edition? Check out the [features exclusive to
EE](http://about.gitlab.com/features/#enterprise).
Access to GitLab Enterprise Edition is included with a [subscription](http://www.gitlab.com/subscription/).
No time to upgrade GitLab yourself? Subscribers receive upgrade and installation
services.
doc/recurly.md 0 → 100644
+ 15
− 0
View file @ 0d9d20aa
www.gitlab.com is a static site but we require two dynamic pages, for 2 subscriptions we have.
To [integrate recurly.js](https://docs.recurly.com/api/recurlyjs/integration) we are using [recurly ruby client library](https://docs.recurly.com/client-libraries/ruby).
To generate the dynamic pages we will be using a small sinatra app and this will allow us to generate the required signature and populate the forms.
In order to use the sinatra application for the first time, couple of things are needed:
1. Populate recurly/config.yml with correct recurly credentials
1. Copy the startup script to /etc/init.d/recurly from source/_support/recurly. Make sure it is executable.
1. Use the nginx config example from source/_support/nginx
1. Make sure that recurly/start_recurly.rb is accessible to user running nginx(chmod 755)
1. Create directory that will hold pid files, /opt/recurly/pids and make the pids owned by the user that will run it(www-data)
1. Start recurly process: `sudo /etc/init.d/recurly start`
1. Configure the recurly process to start at boot: `sudo update-rc.d recurly start 20 2 3 4 5 .`
[Daemonize gem](http://daemons.rubyforge.org/) will make sure that the sinatra app is always running because it starts the app if it is not running.
doc/redirect_blogposts_org_to_com.md 0 → 100644
+ 109
− 0
View file @ 0d9d20aa
Redirect from gitlab.org to www.gitlab.com/ is done in `/etc/nginx/conf.d/org_to_com_rewrite_rules.rules` and included in the main nginx conf on gitlab.org server.
The redirect rules are:
```
rewrite ^/gitlab-ce/?$ https://www.gitlab.com/gitlab-ce/ permanent;
rewrite ^/gitlab-ci/?$ https://www.gitlab.com/gitlab-ci/ permanent;
rewrite ^/community/?$ https://www.gitlab.com/community/ permanent;
rewrite ^/team/?$ https://www.gitlab.com/core-team/ permanent;
rewrite ^/donate/?$ https://www.gitlab.com/contributing/ permanent;
rewrite ^/alumni/?$ https://www.gitlab.com/alumni/ permanent;
rewrite ^/screenshots/?$ https://www.gitlab.com/gitlab-ce/ permanent;
rewrite ^/index.html https://www.gitlab.com/ permanent;
rewrite ^/demo.html http://demo.gitlab.com/ permanent;
```
In sites-available:
```
location / {
rewrite ^/$ https://www.gitlab.com/ redirect;
}
```
Redirect from blog.gitlab.org to www.gitlab.com/blog posts is done in `/etc/nginx/conf.d/blog_rewrite_rules.rule` and included in the main nginx conf on gitlab.org server.
The redirect code is:
```
rewrite ^/screenshots/?$ https://www.gitlab.com/gitlab-ce/ permanent;
rewrite ^/markdown-newline-behaviour/?$ https://www.gitlab.com/2014/02/21/markdown-newline-behaviour/ permanent;
rewrite ^/moved-to-dot-com/?$ https://www.gitlab.com/2014/03/07/moved-to-dot-com/ permanent;
rewrite ^/gitlab-6-dot-6-released/?$ https://www.gitlab.com/2014/02/21/gitlab-6-dot-6-released/ permanent;
rewrite ^/gitlab-book/?$ https://www.gitlab.com/2014/02/01/gitlab-book/ permanent;
rewrite ^/xss-vulnerability-in-gitlab/?$ https://www.gitlab.com/2014/01/30/xss-vulnerability-in-gitlab/ permanent;
rewrite ^/gitlab-ci-4-dot-2-released/?$ https://www.gitlab.com/2014/01/30/gitlab-ci-4-dot-2-released/ permanent;
rewrite ^/gitlab-ce-6-dot-5-released/?$ https://www.gitlab.com/2014/01/21/gitlab-ce-6-dot-5-released/ permanent;
rewrite ^/hosting-gitlab-on-gitlab/?$ https://www.gitlab.com/2014/01/07/hosting-gitlab-on-gitlab/ permanent;
rewrite ^/gitlab-ce-6-dot-4-released/?$ https://www.gitlab.com/2013/12/21/gitlab-ce-6-dot-4-released/ permanent;
rewrite ^/gitlab-ci-4-dot-1-released/?$ https://www.gitlab.com/2013/12/20/gitlab-ci-4-dot-1-released/ permanent;
rewrite ^/gitlab-ci-with-parallel-builds-and-deployments/?$ https://www.gitlab.com/2013/12/19/gitlab-ci-with-parallel-builds-and-deployments/ permanent;
rewrite ^/gitlab-ce-6-dot-3-dot-1-released/?$ https://www.gitlab.com/2013/12/05/gitlab-ce-6-dot-3-dot-1-released/ permanent;
rewrite ^/gitlab-ci-4-dot-0-released/?$ https://www.gitlab.com/2013/11/21/gitlab-ci-4-dot-0-released/ permanent;
rewrite ^/gitlab-ce-6-dot-3-released/?$ https://www.gitlab.com/2013/11/21/gitlab-ce-6-dot-3-released/ permanent;
rewrite ^/multiple-critical-vulnerabilities-in-gitlab/?$ https://www.gitlab.com/2013/11/14/multiple-critical-vulnerabilities-in-gitlab/ permanent;
rewrite ^/security-vulnerability-in-gitlab-shell/?$ https://www.gitlab.com/2013/11/08/security-vulnerability-in-gitlab-shell/ permanent;
rewrite ^/gitlab-ce-6-2-and-5-4-security-release/?$ https://www.gitlab.com/2013/11/04/gitlab-ce-6-2-and-5-4-security-release/ permanent;
rewrite ^/gitlab-ce-6-dot-2-released/?$ https://www.gitlab.com/2013/10/17/gitlab-ce-6-dot-2-released/ permanent;
rewrite ^/gitlab-community-edition-6-dot-1-released/?$ https://www.gitlab.com/2013/09/22/gitlab-community-edition-6-dot-1-released/ permanent;
rewrite ^/gitlab-6-dot-0-released/?$ https://www.gitlab.com/2013/08/20/gitlab-6-dot-0-released/ permanent;
rewrite ^/gitlab-5-dot-4-released/?$ https://www.gitlab.com/2013/07/22/gitlab-5-dot-4-released/ permanent;
rewrite ^/announcing-gitlab-enterprise-edition/?$ https://www.gitlab.com/2013/07/22/announcing-gitlab-enterprise-edition/ permanent;
rewrite ^/announcing-gitlab-ci-3.0/?$ https://www.gitlab.com/2013/07/09/announcing-gitlab-ci-3.0/ permanent;
rewrite ^/gitlab-5-dot-3-released/?$ https://www.gitlab.com/2013/06/20/gitlab-5-dot-3-released/ permanent;
rewrite ^/integrating-gitlab-ci-with-gitlab/?$ https://www.gitlab.com/2013/06/20/integrating-gitlab-ci-with-gitlab/ permanent;
rewrite ^/packaging-gitlab-for-fedora-a-gsoc-2013-project/?$ https://www.gitlab.com/2013/05/28/packaging-gitlab-for-fedora-a-gsoc-2013-project/ permanent;
rewrite ^/gitlab-5-dot-2-released/?$ https://www.gitlab.com/2013/05/22/gitlab-5-dot-2-released/ permanent;
rewrite ^/gitlab-5-dot-1-released/?$ https://www.gitlab.com/2013/04/22/gitlab-5-dot-1-released/ permanent;
rewrite ^/gitlab-ci-2-dot-2-released/?$ https://www.gitlab.com/2013/04/09/gitlab-ci-2-dot-2-released/ permanent;
rewrite ^/gitlab-5-dot-0-has-been-released/?$ https://www.gitlab.com/2013/03/22/gitlab-5-0-was-released/ permanent;
rewrite ^/gitlab-ci-version-2-dot-1-released/?$ https://www.gitlab.com/2013/03/13/gitlab-ci-version-2-dot-1-released/ permanent;
rewrite ^/donations/?$ https://www.gitlab.com/2013/03/01/donations/ permanent;
rewrite ^/gitlab-v4-dot-2-has-been-released/?$ https://www.gitlab.com/2013/02/21/gitlab-v4-dot-2-has-been-released/ permanent;
rewrite ^/gitlab-without-gitolite/?$ https://www.gitlab.com/2013/02/12/gitlab-without-gitolite/ permanent;
rewrite ^/gitlab-4-1-released/?$ https://www.gitlab.com/2013/01/22/gitlab-4-1-released/ permanent;
rewrite ^/gitlab-ci-2-0/?$ https://www.gitlab.com/2013/01/17/gitlab-ci-2-0/ permanent;
rewrite ^/gitlab-4-release/?$ https://www.gitlab.com/2012/12/23/gitlab-4-release/ permanent;
rewrite ^/gitlab-4-release-schedule/?$ https://www.gitlab.com/2012/12/20/gitlab-4-release-schedule/ permanent;
rewrite ^/gitlab-3-dot-1-release/?$ https://www.gitlab.com/2012/11/22/gitlab-3-dot-1-release/ permanent;
rewrite ^/continuous-integration-server-from-gitlab/?$ https://www.gitlab.com/2012/11/13/continuous-integration-server-from-gitlab/ permanent;
rewrite ^/gitlab-3-dot-0-released/?$ https://www.gitlab.com/2012/10/22/gitlab-3-dot-0-released/ permanent;
rewrite ^/gitlab-2-dot-9-released/?$ https://www.gitlab.com/2012/09/21/gitlab-2-dot-9-released/ permanent;
rewrite ^/news-from-the-front/?$ https://www.gitlab.com/2012/09/17/news-from-the-front/ permanent;
rewrite ^/gitlab-2-dot-8-released/?$ https://www.gitlab.com/2012/08/22/gitlab-2-dot-8-released/ permanent;
rewrite ^/gitlab-2-dot-7/?$ https://www.gitlab.com/2012/07/17/gitlab-2-dot-7/ permanent;
rewrite ^/gitlab-v2-6-released/?$ https://www.gitlab.com/2012/06/22/gitlab-v2-6-released/ permanent;
rewrite ^/gitlab-wallpaper/?$ https://www.gitlab.com/2012/06/20/gitlab-wallpaper/ permanent;
rewrite ^/merge-request-improved/?$ https://www.gitlab.com/2012/06/06/merge-request-improved/ permanent;
rewrite ^/network-graph-keyboard-navigation/?$ https://www.gitlab.com/2012/06/01/network-graph-keyboard-navigation/ permanent;
rewrite ^/gitlab-v2-5/?$ https://www.gitlab.com/2012/05/22/gitlab-v2-5/ permanent;
rewrite ^/few-screens-from-v2-5/?$ https://www.gitlab.com/2012/05/19/few-screens-from-v2-5/ permanent;
rewrite ^/gitlab-v2-4-released/?$ https://www.gitlab.com/2012/04/22/gitlab-v2-4-released/ permanent;
rewrite ^/weve-started-donation-campaign/?$ https://www.gitlab.com/2012/03/27/weve-started-donation-campaign/ permanent;
rewrite ^/gitlab-2-3-released/?$ https://www.gitlab.com/2012/03/22/gitlab-2-3-released/ permanent;
rewrite ^/migrating-to-mysql/?$ https://www.gitlab.com/2012/03/12/migrating-to-mysql/ permanent;
rewrite ^/diagnostic-tool/?$ https://www.gitlab.com/2012/03/09/diagnostic-tool/ permanent;
rewrite ^/some-screens-from-2-3pre/?$ https://www.gitlab.com/2012/03/07/some-screens-from-2-3pre/ permanent;
rewrite ^/gitlab-version-2-2/?$ https://www.gitlab.com/2012/02/22/gitlab-version-2-2/ permanent;
rewrite ^/gitlabhq-2-1-released/?$ https://www.gitlab.com/2012/01/22/gitlabhq-2-1-released/ permanent;
rewrite ^/design-changes/?$ https://www.gitlab.com/2012/01/13/design-changes/ permanent;
rewrite ^/2-1-pre/?$ https://www.gitlab.com/2012/01/05/2-1-pre/ permanent;
rewrite ^/gitlabhq-v2-0-moderno/?$ https://www.gitlab.com/2011/12/22/gitlabhq-v2-0-moderno/ permanent;
rewrite ^/useful-dashboard-first-try/?$ https://www.gitlab.com/2011/12/09/useful-dashboard-first-try/ permanent;
rewrite ^/new-access-privilegies/?$ https://www.gitlab.com/2011/12/07/new-access-privilegies/ permanent;
rewrite ^/new-commit-show-page/?$ https://www.gitlab.com/2011/12/01/new-commit-show-page/ permanent;
rewrite ^/merge-requests-v1/?$ https://www.gitlab.com/2011/11/28/merge-requests-v1/ permanent;
rewrite ^/issues-become-simplier/?$ https://www.gitlab.com/2011/11/27/issues-become-simplier/ permanent;
rewrite ^/dark-colors-for-code-review/?$ https://www.gitlab.com/2011/11/27/dark-colors-for-code-review/ permanent;
rewrite ^/issue-prototype/?$ https://www.gitlab.com/2011/11/25/issue-prototype/ permanent;
rewrite ^/whats-next/?$ https://www.gitlab.com/2011/11/23/whats-next/ permanent;
rewrite ^/pronto-released/?$ https://www.gitlab.com/2011/11/22/pronto-released/ permanent;
rewrite ^/features-for-pronto-v1-2-0/?$ https://www.gitlab.com/2011/11/17/features-for-pronto-v1-2-0/ permanent;
rewrite ^/new-feature-project-activities/?$ https://www.gitlab.com/2011/11/16/new-feature-project-activities/ permanent;
rewrite ^/new-feature-network-graph/?$ https://www.gitlab.com/2011/11/16/new-feature-network-graph/ permanent;
rewrite ^/install-guide-from-ryan-wersal/?$ https://www.gitlab.com/2011/11/08/install-guide-from-ryan-wersal/ permanent;
rewrite ^/new-design-is-coming/?$ https://www.gitlab.com/2011/11/07/new-design-is-coming/ permanent;
rewrite ^/gitlab-v1-1-vmware-image/?$ https://www.gitlab.com/2011/10/24/gitlab-v1-1-vmware-image/ permanent;
```
doc/release_blog_template.html.md 0 → 100644
+ 69
− 0
View file @ 0d9d20aa
---
layout: post
title: "GitLab X.X released with MAIN_CE_FEATURE and MAIN_EE_FEATURE"
date: YYYY-MM-22
comments: true
categories:
author: ADD_YOUR_FULL_NAME
author_twitter: TWITTER_USERNAME
image_title: /images/7_X/PICTURE.PNG
---
Intro and introduce main features here.
This month's Most Valuable Person ([MVP](https://about.gitlab.com/mvp/)) is ***MVP_USER*** ***CONTRIBUTION_OF_MVP_USER***.
Thanks ***MVP_USER_FIRST_NAME***!
<!--more-->
## feature 1
> [Documentation link](link)
## feature 2
> [Documentation link](link)
## Other changes
This release has more improvements, including security fixes. Please check out [the Changelog](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) to see the all named changes.
## Upgrade barometer
*** DESCRIBE HOW INVOLVED THE MIGRATIONS ARE. CAN USERS EXPECT MUCH DOWNTIME? ***
*** CHECK IF THERE ARE ANY MIGRATIONS THAT REMOVE OR CHANGE COLUMNS. ***
*** IF THERE ARE ONLY ADDITIONS OR NO MIGRATIONS CONFIRM THAT DEPLOY CAN BE WITHOUT DOWNTIME ****
*Note* We assume you are upgrading from the latest version. If not, then also consult the upgrade barometers of any intermediate versions you are skipping.
If you are upgrading from a GitLab version prior to 8.0 *and* you have CI enabled, you have to upgrade to GitLab 8.0 [first](https://about.gitlab.com/2015/09/22/gitlab-8-0-released/).
Please be aware that by default the Omnibus packages will stop, run migrations,
and start again, no matter how “big” or “small” the upgrade is. This behavior
can be changed by adding a [`/etc/gitlab/skip-auto-migrations`
file](http://doc.gitlab.com/omnibus/update/README.html).
- - -
## Installation
If you are setting up a new GitLab installation please see the
[download GitLab page](https://about.gitlab.com/installation/).
## Updating
Check out our [update page](https://about.gitlab.com/update/).
## Enterprise Edition
The mentioned EE only features and things like LDAP group support can be found in GitLab Enterprise Edition.
For a complete overview please have a look at the [feature list of GitLab EE]( https://about.gitlab.com/features/#enterprise).
Access to GitLab Enterprise Edition is included with a
[subscription]( https://about.gitlab.com/pricing/).
No time to upgrade GitLab yourself?
A subscription also entitles you to our upgrade and installation services.
- - -
generators/direction.rb 0 → 100644
+ 94
− 0
View file @ 0d9d20aa
require 'httparty'
PRIVATE_TOKEN = ENV["PRIVATE_TOKEN"]
class GitLabInstance
def initialize(endpoint, private_token, name)
@endpoint = "#{endpoint}/api/v3"
@private_token = private_token
@name = name
end
def call(path, params = "")
url = @endpoint + path + params
HTTParty.get(url, headers: { "PRIVATE-TOKEN" => @private_token })
end
def name
@name
end
def endpoint
@endpoint
end
end
class GitLabProject
def initialize(id, instance)
@id = id
@instance = instance
@name = instance.name
end
def milestones
result = @instance.call("/projects/#{@id}/milestones")
result = result.select { |ms| ms["state"] != "closed" }
result.sort_by { |ms| ms["title"] }
end
def milestone(milestone_id)
@instance.call("/projects/#{@id}/milestones/#{milestone_id}")
end
def milestone_direction_issues(milestone_id)
@instance.call("/projects/#{@id}/issues", "?milestone=#{milestone_id}&labels=direction")
end
def name
project["name"]
end
def web_url
project["web_url"]
end
def project
@project ||= @instance.call("/projects/#{@id}")
end
def endpoint
@instance.endpoint
end
end
def generate_direction
print "Generating direction..."
com = GitLabInstance.new('https://gitlab.com', PRIVATE_TOKEN, 'GitLab.com')
ce = GitLabProject.new('gitlab-org%2Fgitlab-ce',com)
ee = GitLabProject.new('gitlab-org%2Fgitlab-ee',com)
edition = [ce,ee]
direction_output = ''
edition.each do |project|
milestones = project.milestones
direction_output << "## #{project.name}\n\n"
milestones.each do |ms|
if ms["due_date"] && Date.parse(ms["due_date"]) > Date.today
issues = project.milestone_direction_issues(ms["title"])
direction_output << "### [#{ms["title"]}](#{project.web_url}/milestones/#{ms["iid"]}) \n\n"
issues.each do |issue|
direction_output << "- [#{issue["title"]}](#{project.web_url}/issues/#{issue["id"]})\n"
$stdout.flush
end
direction_output << "\n"
end
end
end
print "\n"
direction_output
end
generators/release_list.rb 0 → 100644
+ 68
− 0
View file @ 0d9d20aa
require 'oga'
require 'httparty'
VERSIONS = [
"8.6", "8.5", "8.4", "8.3","8.2","8.1","8.0","7.14","7.13","7.12","7.11","7.10",
"7.9","7.8"
]
class ReleaseList
def initialize
end
def content
print "Generating release list..."
base_url = 'https://about.gitlab.com'
dec = "##"
year = Time.new.year
month = Time.new.month
next_version = VERSIONS[0]
major_version = next_version.split(".").first
minor_version = next_version.split(".").last
output = ''
VERSIONS.each do |version|
$stdout.flush
major_version = version.split('.').first
minor_version = version.split('.').last
month.to_s.length < 2 ? zero = '0' : zero = ''
url = "#{base_url}/#{year}/#{zero}#{month}/22/gitlab-#{major_version}-#{minor_version}-released"
output << "#{dec} [GitLab #{major_version}.#{minor_version}](#{url}) \n\n"
page = Oga.parse_xml(HTTParty.get(url))
page.css('h2').each do |heading|
text = heading.children.first.text
unless do_not_list(text)
output << "- #{heading.children.first.text}"
output << "\n"
end
end
output << "\n"
if month == 1
month = 12
year = year - 1
else
month = month - 1
end
end
print "\n"
output
end
def do_not_list(input)
[ "Other changes",
"Upgrade barometer",
"Installation",
"Updating",
"Enterprise Edition"
].include? input
end
end
md_page.md 0 → 100644
+ 19
− 0
View file @ 0d9d20aa
# Create a new markdown page
If you want to create a new page and render it with markdown,
just do the following:
1. Create a new folder under `/source`.
1. Create `index.html.markdown` in your new folder.
1. Then just this template in the file:
```
---
layout: markdown_page
title: "Markdown Test Page"
---
YOUR MARKDOWN HERE
```
Your page will be rendered under `/yourfoldername`.
source/.gitattributes 0 → 100644
+ 2
− 0
View file @ 0d9d20aa
*.md text eol=lf
*.markdown text eol=lf
source/about/index.html.md 0 → 100644
+ 150
− 0
View file @ 0d9d20aa
---
layout: markdown_page
title: About Us
---
## GitLab Inc.
GitLab Inc. is a company based on the [GitLab open-source project](https://gitlab.com/gitlab-org/gitlab-ce/).
GitLab is an application to code, test, and deploy code together.
It provides Git repository management with fine grained access controls, code reviews, issue tracking, activity feeds, wikis, and continuous integration.
GitLab Inc. has 4 product offerings:
1. [GitLab Community Edition (CE)](https://about.gitlab.com/features/#community) - free, self hosted application, support from [Community](https://about.gitlab.com/getting-help/)
1. [GitLab Enterprise Edition (EE)](https://about.gitlab.com/pricing/) - paid, self hosted application, comes with additional features and support
1. [GitLab.com](https://about.gitlab.com/gitlab-com/) - free SaaS for public and private repositories, support can be purchased
1. [GitHost.io](https://about.gitlab.com/githost-io/) - a private single-tenant GitLab instance run by us
GitLab Inc. also offers:
1. [Git and GitLab Training](https://about.gitlab.com/training/)
1. [Consulting](https://about.gitlab.com/consultancy/)
1. [Custom Development work](https://about.gitlab.com/development/)
GitLab is a community project, over 1000 people worldwide have [contributed to GitLab]!
GitLab Inc. is an active participant in this community, trying to serve its needs and lead by example. For more information see 'Our stewardship of GitLab CE' further down this page.
## A brief history of GitLab
### _2011: Start of GitLab_
In 2011 Dmitriy was unsatisfied with the options for git repository management.
So together with Valery, he started to build GitLab as a solution for this.
[This commit] was the very start of GitLab.
### _2012: GitLab.com_
Sid saw GitLab for the first time.
He thought it was natural that a collaboration tool for programmers was open source.
Being a Ruby programmer he checked out the source code and was impressed with the code quality of GitLab.
He started GitLab.com as the first SaaS offering for GitLab.
In November 2012, Dmitriy also made the [first version of GitLab CI].
### _2013: "I want to work on GitLab full time"_
In 2013, Dmitriy tweeted that he wanted to work on GitLab full time.
Sid and Dmitriy teamed up and started bootstrapping GitLab as a company.
In the same year in August, we introduced [GitLab Enterprise Edition].
### _2014: GitLab was incorporated_
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.
### _2015: Y Combinator_
In the very start of 2015, almost the entire GitLab team flew over to Silicon
Valley to [participate in Y Combinator].
At this point, over 1000 people worldwide have [contributed to GitLab] and more
than 100,000 organizations are using GitLab.
## Vision
At GitLab we have one vision.
**Everyone can contribute** to all digital content.
For more information see the our [strategy](https://about.gitlab.com/strategy/).
## Logo
Our <a href="https://en.wikipedia.org/wiki/Japanese_raccoon_dog">Tanuki</a> logo
symbolizes this with a smart animal that works in a group to achieve a common goal.
Please see our [press page](https://about.gitlab.com/press/) to download the logo.
## Values
Please see the [values section in our handbook](https://about.gitlab.com/handbook/#values).
## Our stewardship of GitLab CE<a name="stewardship"></a><a name="our-stewardship-of-gitlab-ce"></a>
GitLab Inc. is a for profit company that balances the need to improve
GitLab Community Edition (CE) with the need to add features to GitLab
Enterprise Edition (EE) exclusively in order to generate more income.
We promise that:
1. We won't remove features from CE to make the same feature exclusive in EE
1. We won't introduce features into CE with a delay, if a feature is planned to land in both it will be released simultaneously in both
1. We will always release all tests that we have for a feature that is in CE
1. CE will have all the features that are essential to running a large 'forge' with public and private repositories
1. CE will not contain any artificial limits (repositories, users, size, etc.)
1. The majority of new features made by GitLab Inc. will be for both CE and EE
Apart from making new features GitLab Inc. does a lot of work that benefits both CE and EE:
1. [Responsible disclosure](https://about.gitlab.com/disclosure/) process and security fixes
1. [Release management](http://doc.gitlab.com/ce/release/README.html) including a monthly release of both CE and EE
1. Packaging GitLab in our [Omnibus packages](https://gitlab.com/gitlab-org/omnibus-gitlab)
1. Running a [packages server](https://packages.gitlab.com/gitlab/)
1. Dependency upgrades (Rails, gems, etc.)
1. Performance improvements
When we make new features we ask ourselves, is this feature much more relevant for organizations that have more than 100 developers?
If the answer is yes the feature is likely to be exclusive to EE.
We always make sure that CE can do all essential things and there are companies using CE with more than 10,000 developers.
When someone contributes a feature to CE that is already in EE we have a hard decision to make.
We hope that people focus on contributing features that are neither in CE nor EE.
This way both edits benefit from a new feature and GitLab Inc. don't have to make a hard decision.
The features we plan to build for EE are shared on our [direction page](https://about.gitlab.com/direction/) and we welcome people to contribute features to CE that are planned for future EE releases, if you pick one from the upcoming release please ask in the issue if someone is already working on it.
When someone does contribute a feature to CE that is already in EE we weigh a couple of factors in that decision:
1. What is the quality of the code?
1. Is it complete and does it meet the criteria of the [definition of done](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#definition-of-done)?
1. What is the use case for this, is it needed for organizations with less than 100 people?
1. Is it an original work or clearly based on the EE code?
In case we're not sure, we'll consult with the [core team](https://about.gitlab.com/core-team/) to reach a conclusion.
## Handbook
If you're interested, most of our internal procedures can be found in <a href="/handbook">publicly viewable handbooks</a>.
## Donations<a name="donations"></a>
Some people contact us because they would like to donate to GitLab.
If you have time to give please help spread the word about GitLab by mentioning us and/or <a href="https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md">contribute by creating and reviewing issues and merge requests</a>.
If you would like to give money please <a href="http://railsgirlssummerofcode.org/campaign/">donate to Rails Girls Summer of Code</a> in our name.
## Location
GitLab is a community project with people participating from all over the world.
GitLab Inc. has people in three continents to serve our customers better.
Most of our customers are in the United States.
Most of our team is distributed. We're proud to be [working remotely](https://about.gitlab.com/2014/07/03/how-gitlab-works-remotely/),
using GitLab Issues to coordinate. We have a [Remote Manifesto](https://about.gitlab.com/2015/04/08/the-remote-manifesto/),
our team members have shared their [experiences](https://about.gitlab.com/2015/06/17/highlights-to-my-first-remote-job/)
in our blog and did a Q&A for [Remote.co](https://remote.co/company/gitlab/). You can taste a bit of the GitLab team culture by visiting
our <a href="https://about.gitlab.com/culture/">culture page</a>.
[This commit]: https://gitlab.com/gitlab-org/gitlab-ce/commit/0f43e98ef8c2da8908b1107f75b67cda2572c2c4
[first version of GitLab CI]: https://gitlab.com/gitlab-org/gitlab-ci/commit/52cd500ee64a4a82b9ff6752ee85028cd419fcbe
[GitLab Enterprise Edition]: https://about.gitlab.com/2013/08/22/introducing-gitlab-6-0-enterprise-edition/
[participate in Y Combinator]: https://about.gitlab.com/2015/03/04/gitlab-is-part-of-the-y-combinator-family/
[contributed to GitLab]: http://contributors.gitlab.com/
source/alumni/index.html.haml 0 → 100644
+ 167
− 0
View file @ 0d9d20aa
---
layout: default
title: "Core team alumni"
date: 2013-07-03 18:34
comments: false
sharing: true
footer: true
---
#content
.container
%p GitLab core team members who are no longer active but whose work is very much appreciated.
.row-fluid
%hr.hor-line/
.row-fluid.teams
.span3
.row-fluid.padding
%img{src: "/images/team/valeriy.png"}/
.row-fluid
%ul.team
%li
%a{href: "http://ua.linkedin.com/pub/valeriy-sizov/41/284/249"}
.linkedin.no-margin
%li
%a{href: "https://github.com/vsizov"}
.github.no-margin
.span9
%h2.title Valeriy Sizov
%p Valeriy was one of the initial authors of GitLab together with Dmitriy Zaporozhets.
.row-fluid
%hr.hor-line/
.row-fluid.teams
.span3
.row-fluid.padding
%img{src: "https://secure.gravatar.com/avatar/fbd740180d2c3b4dbe8c3a23d4e30c83?s=420&d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-user-420.png"}/
.row-fluid
%ul.team
%li
%a{href: "http://gravityonmars.com/"}
.website.no-margin
%li
%a{href: "http://twitter.com/gravityonmars"}
.twitter.no-margin
%li
%a{href: "https://github.com/gravityonmars"}
.github.no-margin
.span9
%h2.title Ricardo Rauch
.row-fluid
%hr.hor-line/
.row-fluid.teams
.span3
.row-fluid.padding
%img{src: "https://secure.gravatar.com/avatar/73c8253932541a7b5cbc5d79493f2bea?s=420&d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-user-420.png"}/
.row-fluid
%ul.team
%li
%a{href: "http://tsigo.github.io/"}
.website.no-margin
%li
%a{href: "https://twitter.com/rspeicher"}
.twitter.no-margin
%li
%a{href: "https://github.com/tsigo"}
.github.no-margin
.span9
%h2.title Robert Speicher
.row-fluid
%hr.hor-line/
.row-fluid.teams
.span3
.row-fluid.padding
%img{src: "/images/team/yves.jpeg"}/
.row-fluid
%ul.team
%li
%a{href: "http://blog.senny.ch/"}
.website.no-margin
%li
%a{href: "https://twitter.com/fistofsenn"}
.twitter.no-margin
%li
%a{href: "https://github.com/senny"}
.github.no-margin
.span9
%h2.title Yves Senn
.row-fluid
%hr.hor-line/
.row-fluid.teams
.span3
.row-fluid.padding
%img{src: "/images/team/ariejan.jpeg"}/
.row-fluid
%ul.team
%li
%a{href: "http://ariejan.net/"}
.website.no-margin
%li
%a{href: "https://twitter.com/ariejan"}
.twitter.no-margin
%li
%a{href: "http://nl.linkedin.com/in/ariejan"}
.linkedin.no-margin
%li
%a{href: "https://github.com/ariejan"}
.github.no-margin
.span9
%h2.title Ariejan de Vroom
.row-fluid
%hr.hor-line/
.row-fluid.teams
.span3
.row-fluid.padding
%img{src: "/images/team/riyad.png"}/
.row-fluid
%ul.team
%li
%a{href: "http://blog.bilak.info/"}
.website.no-margin
%li
%a{href: "https://github.com/riyad"}
.github.no-margin
.span9
%h2.title Riyad Preukschas
.row
%hr.hor-line/
.row-fluid
%hr.hor-line/
.row-fluid.teams
.span3
.row-fluid.padding
%img{src: "/images/team/saito.png"}/
.row-fluid
%ul.team
%li
%a{href: "http://saito.im/"}
.website.no-margin
%li
%a{href: "https://github.com/SaitoWu"}
.github.no-margin
.span9
%h2.title Saito Wu
.row
%hr.hor-line/
.row-fluid
%hr.hor-line/
.row-fluid.teams
.teams.row
.span3
.row-fluid.padding
%img.img-responsive{src: "/images/team/nihad.jpg"}/
.row-fluid
%ul.team
%li
%a{href: "http://narkoz.github.io/"}
.website.no-margin
%li
%a{href: "https://github.com/NARKOZ"}
.github.no-margin
.span9
%h2.title Nihad Abbasov
.row
%hr.hor-line/
.row-fluid
%p
GitLab core team members who are active can be found on the
= succeed "." do
%a{href: "/core-team"} core team page
source/applications/index.html.haml 0 → 100644
+ 40
− 0
View file @ 0d9d20aa
---
layout: default
title: Applications Supporting GitLab
suppress_header: true
extra_css:
- applications.css
---
.wrapper
.application-container
.application-overlay
.application-content
%h1 Applications Supporting GitLab
.container
.container-text
%p
Every application that supports Git will work with GitLab.
Below are some of the applications we wanted to highlight.
You can use the
%a{href: "http://doc.gitlab.com/ce/api/"} GitLab API
to add support for GitLab.
Please file a
%a{href: "https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests?assignee_id=&label_name=&milestone_id=&scope=all&sort=newest&state=all"} merge request
to add a new application to the list.
- data.applications.each do |app_category|
%hr{id: app_category.id}
%h2
= app_category.title
.row
- app_category.applications.each do |application|
.col-md-4
.app
%h4
= application.title
%p
= application.content
- if application.links
- application.links.each do |link|
%a{href: link.url, title: link.title}
= link.title
%br
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