Commit 3cff2ff4 authored by Takuya Noguchi's avatar Takuya Noguchi 🇪🇸

Fix typos in blog posts

Signed-off-by: Takuya Noguchi's avatarTakuya Noguchi <takninnovationresearch@gmail.com>
parent 54d2c1d3
......@@ -19,7 +19,7 @@ categories: releases
Also some things should be improved:
<ul>
<li>New design is far from perfect. It should be polished</li>
<li>I dont like tree browse perfomance</li>
<li>I don't like tree browse performance</li>
<li>Activities page requires pagination like 'commits' or 'wall' page</li>
<li>Usability</li>
</ul>
......
---
title: Issues become simplier
title: Issues become simpler
wordpress_id: 103
wordpress_url: http://blog.gitlabhq.com/?p=103
date: 2011-11-27 15:34:27 +00:00
comments: false
categories: company
---
We decided to keep issue show page simplier.
We decided to keep issue show page simpler.
<a href="http://blog.gitlabhq.com/wp-content/uploads/2011/11/issues_11.png"><img src="http://blog.gitlabhq.com/wp-content/uploads/2011/11/issues_11.png" alt="" title="issues_1" width="602" class="aligncenter size-full wp-image-105" /></a>
---
title: New access privilegies
title: New access privilege
wordpress_id: 119
wordpress_url: http://blog.gitlabhq.com/?p=119
date: 2011-12-07 14:25:25 +00:00
......
......@@ -23,7 +23,7 @@ Lets look at changelog:
## Improvements:
1. Source Browse perfomance increased
1. Source Browse performance increased
2. Better configuration file
3. UI: full tabs, colored labels and much more
......
......@@ -37,7 +37,7 @@ We are developers and if miss something - we build it!
_Dmitriy Zaporozhets:_
> We are going to build a best software. GitLab 3 is not an end - it is only a begining
> We are going to build a best software. GitLab 3 is not an end - it is only a beginning.
### Release notes:
......@@ -51,7 +51,7 @@ Its time to share some information about release (_its not a full changelog belo
* Fixed critical bug with deleting/adding ssh keys
* Added unofficial Postgres support
* Project Groups(In case you want to group your projects)
* Perfomance of Files & Commits significantly improved
* Performance of Files & Commits significantly improved
* refactoring, code cleanup etc
......
......@@ -19,7 +19,7 @@ Also as a bonus we pushed a v1.0.1 version of [GitLab CI](/2012/11/13/continuous
## Few screens:
Event Filter
![Screens](/images/3_1/1.png)
GitLab CI intergration for Merge Requests
GitLab CI integration for Merge Requests
![Screens](/images/3_1/2.png)
Better image compare diff
![Screens](/images/3_1/3.png)
......
......@@ -50,7 +50,7 @@ This task starts every hour and check for scheduled builds.
__GitLab v4.1 will be released at Jan 22th.__
We replaced resque with sidekiq in GitLab too. Now push events are processed much faster.
Also we added a Public Area, fixed a lot of bugs and improved perfomance of application.
Also we added a Public Area, fixed a lot of bugs and improved performance of application.
See [CHANGELOG](https://github.com/gitlabhq/gitlabhq/blob/master/CHANGELOG) for full list of changes.
According to [gitlab_meta](http://rubygems.org/gems/gitlab_meta) gem amount of GitLab v4.0 installations reached 9k.
......
......@@ -27,7 +27,7 @@ To do this, we will need your help. If you like GitLab and want to help with the
### Replaced Resque with Sidekiq:
We replaced Resque with Sidekiq to proccess background jobs.
We replaced Resque with Sidekiq to process background jobs.
Sidekiq uses threads instead of forks so it is much more efficient with memory compared to Resque.
### Discussions:
......
......@@ -10,7 +10,7 @@ community: true
Hi everyone!
Today we released new version of GitLab CI.
We fixed some bugs, updated libraries to recent versions and made some ui imporvements.
We fixed some bugs, updated libraries to recent versions and made some ui improvements.
We strongly recommend to update since this release include security fixes from rails & devise.
Also it should save you additional 50-100MB RAM by replacing unicorn with puma.
......
......@@ -18,7 +18,7 @@ Today we release GitLab v5.1 live from [Railsberry](http://www.railsberry.com/)
3. Network graph becomes even cooler. Now with vertical orientation, commit messages and much more.
4. Improved performance and reduced memory consumption, among other things by switching the application server from Unicorn to Puma.
This release most valueable person (MVP) is Hiroyuki Sato for contributing the improved Network Graph, thanks Hiroyuki!
This release most valuable person (MVP) is Hiroyuki Sato for contributing the improved Network Graph, thanks Hiroyuki!
<!-- more -->
......
......@@ -22,7 +22,7 @@ In the Enterprise Edition we will add features that are useful to large organiza
The community edition is the heart of GitLab and will remain under development, gaining new functionality in the coming years. No features will ever removed from the Community Edition. For example, the LDAP user functionality will stay in the Community edition. In the enterprise edition functionality for larger organizations will be added. In GitLab EE 6.0 this will be the ability to synchronize GitLab groups with LDAP groups.
We discussed the release of the Enterprise Edition with the rest of the GitLab community and received [great input about the licensing](/2013/07/22/announcing-gitlab-enterprise-edition). The Enterprise Edition will be released under the MIT because we believe in open source and trust the GitLab community. GitLab.com will not put the source code online but everyone in posession of the source is free to do as they please. We kindly ask subscribers not to distribute GitLab EE if they think GitLab.com is doing a good job serving the GitLab community.
We discussed the release of the Enterprise Edition with the rest of the GitLab community and received [great input about the licensing](/2013/07/22/announcing-gitlab-enterprise-edition). The Enterprise Edition will be released under the MIT because we believe in open source and trust the GitLab community. GitLab.com will not put the source code online but everyone in possession of the source is free to do as they please. We kindly ask subscribers not to distribute GitLab EE if they think GitLab.com is doing a good job serving the GitLab community.
The price of GitLab EE will be $1.99 per user per month or $19.90 per user per year in 20 user increments. We think this is great value for money and enables both large and small organizations to enjoy the Enterprise Edition. GitLab Enterprise Edition offers features unmatched by competing software such as adding multiple groups to a collection of repos. At the same time GitLab EE is up to 10 times more affordable than other solutions.
......
......@@ -5,7 +5,7 @@ author: Marc Radulescu
categories: insights
---
360i, the [increasingly sucessful](http://adage.com/article/special-report-agency-alist-2014/360i-3-ad-age-s-2014-agency-a-list/291355/) digital media company from the US, agreed to spend some time with us and explain how they're transitioning to GitLab. You can read the case study [here](/case-studies/360i-transitions-to-gitlab/).
360i, the [increasingly successful](http://adage.com/article/special-report-agency-alist-2014/360i-3-ad-age-s-2014-agency-a-list/291355/) digital media company from the US, agreed to spend some time with us and explain how they're transitioning to GitLab. You can read the case study [here](/case-studies/360i-transitions-to-gitlab/).
While moving away from SVN, they chose GitLab because it was the most cost-effective in-house solution.
As it turns out, GitLab did more than just eliminate the frustrations of breaking code and of over-increasing storage space.
......
......@@ -5,7 +5,7 @@ categories: company
author: Sytse Sijbrandij
---
Today we rename our Software as a Service (SaaS) offering from GitLab Cloud to GitLab.com. We noticed people refered to it already as GitLab.com and we want to prevent confusion. If you want unlimited private repositories and collaborators please join the thousands of people already using [GitLab.com](/gitlab-com/).
Today we rename our Software as a Service (SaaS) offering from GitLab Cloud to GitLab.com. We noticed people referred to it already as GitLab.com and we want to prevent confusion. If you want unlimited private repositories and collaborators please join the thousands of people already using [GitLab.com](/gitlab-com/).
To refer to this company we'll start using the new official name: GitLab B.V. (which is Dutch for GitLab Inc.). Our website will stay here at [https://www.gitlab.com/](https://www.gitlab.com/) while the GitLab.com service can be reached at the domain apex [https://gitlab.com/](https://gitlab.com/).
......
......@@ -36,7 +36,7 @@ The former releases had some other problems as well:
* The runner didn't properly handle crashing build scripts (it considered the build seemed to continue running endlessly)
With this release, Runner creates a single temporary bash script which contains all the commands the build needs.
The script itself is then exectued as a child process in its own session (process group) by the runner.
The script itself is then executed as a child process in its own session (process group) by the runner.
This way we can ensure that killing the script also kills all its child processes.
__We would like to thank Corin Langosch for contributing these improvements.__
......
......@@ -34,8 +34,8 @@ By comparing the branches before creating the MR, a "nothing to merge" situation
Thanks to the contribution by Evgeniy Sokovikov, editing files via the web editor is now more convenient.
When editing a file you can now view the diff before commiting the changes.
If the file is a markdown file, you can preview the changes before commiting.
When editing a file you can now view the diff before committing the changes.
If the file is a markdown file, you can preview the changes before committing.
[![screenshot](/images/6_9/edit1.png)](/images/6_9/edit1.png)
......
......@@ -34,7 +34,7 @@ When your group has been created you are presented with the group dashboard feed
You can use the 'New project' button to add a project to the new group.
## Transfering an existing project into a group
## Transferring an existing project into a group
You can transfer an existing project into a group you own from the project settings page.
First scroll down to the 'Dangerous settings' and click 'Show them to me'.
......
......@@ -52,7 +52,7 @@ Because of its great value and easy scalability, you can open up your GitLab ins
Since software is eating the world the people that are involved with software projects are no longer only developers.
Stakeholders in projects need access to the issue tracker and end-users want access to the wiki.
With GitHub Enterprise the pricing causes some organizations to limit access to developers.
With the affordable pricing made possible by open source, GitLab Enterprise Edition allows collaboration accross function groups.
With the affordable pricing made possible by open source, GitLab Enterprise Edition allows collaboration across function groups.
# Conclusion
......
......@@ -249,12 +249,12 @@ the failover procedure during the time the new script was in production.
But, even though I was introducing new complexity and hence bugs into our
failover tooling, I did manage to learn and try out enough things to bring this
project to a succesful conclusion.
project to a successful conclusion.
## Enabling the DRBD replication
This part was relatively easy. I just had to grow the DRBD block device
'drbd0' so that it could accomodate the new stacked (inner) block device
'drbd0' so that it could accommodate the new stacked (inner) block device
'drbd10' without having to shrink our production filesystem. Because drbd0 was
backed by LVM and we had some space left this was a matter of invoking
`lvextend` and `drbdadm resize` on both our production nodes.
......
......@@ -7,7 +7,7 @@ categories: releases
In GitLab 7.8.x, smtp settings example file contained the line `openssl_verify_mode: 'none'`. This meant that mail server TLS certificate wasn't verified by GitLab.
Confusion came from assumption that `none` is the default value when TLS is enabled and that it behaved the same as when the setting is omited. In contact with Rails team member we've learned omiting `openssl_verify_mode` defaults to `peer`.
Confusion came from assumption that `none` is the default value when TLS is enabled and that it behaved the same as when the setting is omitted. In contact with Rails team member we've learned omitting `openssl_verify_mode` defaults to `peer`.
If you have installation from source, smtp enabled, TLS enabled and the above setting we advise you to change the setting to `openssl_verify_mode: 'peer'`.
......
......@@ -29,7 +29,7 @@ Edition 7.9.3 and older.
See below for update instructions.
## LDAP group syncronization problems (Enterprise Edition only)
## LDAP group synchronization problems (Enterprise Edition only)
We have recently discovered an incompatibility between the support for multiple
LDAP servers (added in GitLab EE 7.4) and the support for multiple identities
......
......@@ -108,7 +108,7 @@ That makes working with CI much easier and convenient for those of you that
work with forks.
Of course, we made sure this won't be possible if it infringes on permissions
you've set, so make sure to check the [documenation](http://doc.gitlab.com/ci/).
you've set, so make sure to check the [documentation](http://doc.gitlab.com/ci/).
## Invite new people into project by email
......
......@@ -24,7 +24,7 @@ What is source control? It’s a system that records and manages changes to proj
What is continuous integration? It’s the system of continuously incorporating the work advances with a shared mainline in a project. Git and GitLab together make continuous integration happen.
## Continuous deployment
What is continuous deployment? It means that whenever there is a change to the code, it is deployed or made live immediately. This is in contrast to continous integration, where code is continuously being merged in the mainline and is always ready to be deployed, rather than actually deployed.
What is continuous deployment? It means that whenever there is a change to the code, it is deployed or made live immediately. This is in contrast to continuous integration, where code is continuously being merged in the mainline and is always ready to be deployed, rather than actually deployed.
When people talk about CI and CD what they usually mean to say is that they are constantly and automatically testing their code against their tests using a tool such as GitLab CI and upon passing to a certain action. That action could be merging the code into a branch (master, production, etc), deploying it to a server or building a package / piece of software out of it.
Non-continuous integration would be everyone working on something and only integrating all the work as the very last step. Obviously, that results in many conflicts and issues, which is why CI is adopted widely nowadays.
......@@ -103,7 +103,7 @@ Support Package:
* GitLab EE runs on your servers.
### GitLab Continuous Integration (CI)
* Free, self hosted application that integrates with GitLab CE/EE. Also availble as SaaS at ci.gitlab.com.
* Free, self hosted application that integrates with GitLab CE/EE. Also available as SaaS at ci.gitlab.com.
* Easy to set up since it is included in Omnibus packages of GitLab or use it for free on ci.gitlab.com.
* Beautiful interface with a clear menu structure.
* Performant and stable, as tests run distributed on separate machines.
......
......@@ -12,7 +12,7 @@ We've updated the default/recommended SSL ciphers for all GitLab installations a
<!--more-->
After some reasearch and testing we've decided to change the SSL cipher suite served by the web server/load balancer.
After some research and testing we've decided to change the SSL cipher suite served by the web server/load balancer.
This decision was made after weighing on the trade-offs between having the stronger DH params and denying access to Java 6 based clients.
......
......@@ -27,7 +27,7 @@ We found Mattermost to be the leading open source Slack-alternative and suggeste
![Mattermost screenshot](/images/mattermost/mattermost.png)
It turns out that [after the succesful launch of MatterMost on Hacker News](https://news.ycombinator.com/item?id=9770322) there were a lot of requests for an easier way to install Mattermost and to add LDAP features to it.
It turns out that [after the successful launch of Mattermost on Hacker News](https://news.ycombinator.com/item?id=9770322) there were a lot of requests for an easier way to install Mattermost and to add LDAP features to it.
With Omnibus GitLab we have a great way to install software in 2 minutes on many platforms and GitLab CE and EE contain many LDAP features.
We decided to collaborate and the Mattermost team quickly added PostgreSQL support and OAuth login to Mattermost so it could connect to the [GitLab OAuth provider](http://doc.gitlab.com/ce/integration/oauth_provider.html).
......
......@@ -20,7 +20,7 @@ It includes the following fixes:
<!-- more -->
**Omnibus-gitlab packages note:** Before announcing this release, inital set of packages that was built contained an error.
**Omnibus-gitlab packages note:** Before announcing this release, initial set of packages that was built contained an error.
We've noticed this and yanked the packages(version 8.0.4-ce.0). Sadly, the packages were publicly available before this blogpost was live so if you installed/upgraded your GitLab in the timeframe(approx 12:00PM-12:45PM CET on Oct. 06, 2015.) where the broken packages were available, you will run into a `SyntaxError` during installation.
Run `sudo apt-get update` to get the correct version of the package (8.0.4-ce.1) and install the package again with `sudo apt-get install gitlab-ce` (or `gitlab-ee`).
......
......@@ -91,7 +91,7 @@ vulnerability.
### CVE-2016-0752 Possible Information Leak Vulnerability in Action View
This vulnerability, when present, lets an attacker load an arbitray file
This vulnerability, when present, lets an attacker load an arbitrary file
on disk to be interpreted by Rails as a template. Combined with user
uploads (which GitLab offers) this creates the potential for remote code
execution.
......@@ -99,7 +99,7 @@ execution.
It is hard to search for this vulnerability in source code because
untrusted input may be assigned to a variable in one place, with the
variable being passed to `render` in another place. We have not found
occurences of unsafely passing a value *directly* from `params`
occurrences of unsafely passing a value *directly* from `params`
to `render` in any released version of GitLab.
It is unlikely that any released version of GitLab is affected by this
......
......@@ -293,7 +293,7 @@ for just how flexible and powerful it is.
Actually, there's really not much to do here! CI is enabled by default on new
projects. If your iOS project has some environment variables you want to keep
secret, but you want to keep the project public on GitLab, you may want to disable
**Public builds** in Project Settings, under _Continous Integration_. This will
**Public builds** in Project Settings, under _Continuous Integration_. This will
hide the build results from everyone except members of the project.
You may also want to go to _Runners_ under your Project Settings and click
......
......@@ -99,7 +99,7 @@ Below you can find some implementation details of current solution.
1. Substitute each subsequent match with fully-expanded cross-project
reference.
This substitues reference like `#123` with `gitlab-org/gitlab-ce#123`.
This substitutes reference like `#123` with `gitlab-org/gitlab-ce#123`.
1. For each substitution generate HTML twice, using a new content and using an
old content.
......
......@@ -296,7 +296,7 @@ be necessary for [Step 5](#step-5-decrypt-your-private-key) ahead.
#### On Windows
**Note:** the numbers in the parenthesys correspond to the numbers on the image below.
**Note:** the numbers in the parentheses correspond to the numbers on the image below.
{: .note}
- Download the binary file **StartComTool.exe** and launch it
......
......@@ -46,7 +46,7 @@ live-running, production system is fraught with perils, and we did not want to
risk causing other issues. Instead, our Infrastucture Lead, Pablo Carranza
proposed blocking the vulnerable route via a HAProxy rule. This would only be
a simple configuration change in one place. The following Tuesday, Pablo
applied the HAProxy rule and verified that it successfuly blocked the route.
applied the HAProxy rule and verified that it successfully blocked the route.
With GitLab.com patched with this workaround, we next had to consider: how
much advance notice should we give to our users about a security release?
......
......@@ -445,7 +445,7 @@ You can have several "runner" definitions, each with a `limit` of builds/machine
The `concurrent` limit is a global setting. So if I had 3 runner definitions, each with a `limit` of 15, they would still be globally limited to 20 as defined in the `concurrent` global variable.
You can use different providers for specific needs, for example, to run OS X builds or Rapsberry PI builds or other exotic kinds of builds. In the example I am keeping it simple and just setting many builds in the same provider (Digital Ocean).
You can use different providers for specific needs, for example, to run OS X builds or Raspberry Pi builds or other exotic kinds of builds. In the example I am keeping it simple and just setting many builds in the same provider (Digital Ocean).
And don't worry about the monthly fee for each machine. When used in this manner, you will be paying per hour.
......@@ -510,7 +510,7 @@ They have many things right. First of all, it's a "simple" Ruby on Rails project
The APIs are all written using Grape. They have the [GitLab CE][ce] project separated from other components, such as the [GitLab Shell][shell] and [GitLab CI Multi-Runner][run].
They also forked [Omnibus][omn] in order to be able to package the CE Rails project as a ".deb". Everything is orchestrated with Docker. And when a new version is available, you only need to `apt-get update && apt-get ugprade` and it will do all the work of backing up and migrating Postgresql, updating the code, bundling in new dependencies, restarting the services and so forth. It's super convenient and you should take a look at this project if you have complicated Rails deployments into your own infrastructure (out of Heroku, for example).
They also forked [Omnibus][omn] in order to be able to package the CE Rails project as a ".deb". Everything is orchestrated with Docker. And when a new version is available, you only need to `apt-get update && apt-get upgrade` and it will do all the work of backing up and migrating Postgresql, updating the code, bundling in new dependencies, restarting the services and so forth. It's super convenient and you should take a look at this project if you have complicated Rails deployments into your own infrastructure (out of Heroku, for example).
I am almost done moving hundreds of repositories from both Bitbucket and GitHub to GitLab right now and the developers from my company are already using it in a daily basis without any problems. We are almost at the point where we can disengage from Bitbucket, GitHub and external CIs.
......
......@@ -90,6 +90,6 @@ Here is a list of the tools we use right now:
- [Prometheus](https://github.com/prometheus) &#8594; It will allow you to gather metrics in a time series provinding good exploration tools. Then graph those metrics in grafana building dashboards.
- [Blackbox exporter](https://github.com/prometheus/blackbox_exporter) &#8594; It will allow you to see what your customers are seeing from the outside, if it's slow, you will [see how slow](http://dashboards.gitlab.com/dashboard/db/gitlab-status)
- [Influxdb](https://influxdata.com/) &#8594; Time series database, supported by GitLab for pushing white box performance metrics.
- [Grafana](http://grafana.org/) &#8594; Graphing tool, we use it with both Influxdb and Prometheus to build graph dashobards that allow you to see how the aplication is behaving through time.
- [Grafana](http://grafana.org/) &#8594; Graphing tool, we use it with both Influxdb and Prometheus to build graph dashobards that allow you to see how the application is behaving through time.
- [ELK stack](https://www.elastic.co/webinars/introduction-elk-stack) (Elasticsearch, Logstash, Kibana) &#8594; Log processing and analyzing system. Logs are usually the first source of information that can and should be used. There's no lower hanging fruit than writing logs that add value, then parsing these logs to see how is the system behaving. Something as simple as requests per minute will tell you how much the system is being used, add errors per minute to the same graph and you will know if your last deploy is broken and should be reverted.
- [Sentry](https://getsentry.com/welcome/) &#8594; Real time error tracking system.
......@@ -29,7 +29,7 @@ Knowing this, the team was able to craft a [proposal](https://gitlab.com/gitlab-
## Feedback & Challenges
Here at GitLab we are able to gather feedback early by posting our proposals as issues that are publicly available to team members, contributors, customers, and users. With over 100 participants, the Issue Boards proposal recieved a lot of responses that validated many of our assumptions, addressed concerns, and provided insight for future improvements.
Here at GitLab we are able to gather feedback early by posting our proposals as issues that are publicly available to team members, contributors, customers, and users. With over 100 participants, the Issue Boards proposal received a lot of responses that validated many of our assumptions, addressed concerns, and provided insight for future improvements.
Some concerns included:
......
......@@ -49,7 +49,7 @@ having all [10 solutions][scope] ready to go for the GitLab community.
This is why we hosted a special, live event with
GitLab’s CEO, [Sid Sijbrandij]. During the event, Sid shared
the **GitLab Master Plan**, and demoed our advanced workflow for modern software
production using **Conversation Driven Developement (CDD)**.
production using **Conversation Driven Development (CDD)**.
Everyone is invited to tune in, encouraged to ask questions, express
opinions, and share ideas with us. At GitLab, **everyone can contribute!**
......
......@@ -36,7 +36,7 @@ That slideshow presentation is then automatically made available at its public U
https://gitpitch.com/user/project/branch?grs=gitlab
```
Here `user` and `project` matches our GitLab.com user and project names respectively and `branch` matches the repository branch where we commited our **PITCHME.md** file.
Here `user` and `project` matches our GitLab.com user and project names respectively and `branch` matches the repository branch where we committed our **PITCHME.md** file.
Note, the `/branch` can be omitted from the slideshow URL if we are referencing the `master` branch.
## GitPitch In 60 Seconds
......
......@@ -42,7 +42,7 @@ As a GitLab administrator you have the option to integrate your GitLab instance
with Sentry, an external exception tracking system. When this feature is
enabled, you can see details of each error ('500 page') that occurs on your
GitLab server. These details include HTTP headers of the request that
experienced the exception. Prior to GitLab 8.12.5, when an exception occured in
experienced the exception. Prior to GitLab 8.12.5, when an exception occurred in
the GitLab API (a URL starting with `/api/v3/`), GitLab would inadvertently send
the `Private-Token` header used to authenticate with the GitLab API in the error
report to Sentry. This meant that when you viewed a Sentry error report for an
......
......@@ -55,13 +55,13 @@ provide a minimum IOPS, so they can just drop you. If we wanted to make the disk
reach something, we would have to wait 100 ms latency.
[That's basically telling us to wait 8 years][space-time-article]. What we found
is that the cloud was not meant to provide the level of IOPS performance we needed
to run an agressive system like CephFS.
to run an aggressive system like CephFS.
At a small scale, the cloud is cheaper and sufficient for many projects.
However, if you need to scale, it's not so easy. It's often sold as, "If you
need to scale and add more machines, you can spawn them because the cloud is
'infinite'". What we discovered is that yes, you can keep spawning more
machines but there is a threshold in time, particulary when you're adding heavy
machines but there is a threshold in time, particularly when you're adding heavy
IOPS, where it becomes less effective and very expensive. You'll still have to
pay for bigger machines. The nature of the cloud is time sharing so you still
will not get the best performance. When it comes down to it, you're paying a lot
......
......@@ -41,7 +41,7 @@ Please read on for more details.
- **EE:** Port of rephrase-system-notes to EE ([!913])
- **EE:** Get rid of user activites table and replace it with redis ([!915])
- **EE:** Get rid of user activities table and replace it with redis ([!915])
- **EE:** Geo: Display Custom Avatars in secondary nodes ([!904])
......
......@@ -22,7 +22,7 @@ some of the awesome features we just released. Check out the video and highlight
### 1:07 GitLab's Vision
"When we [announced our series B round in Septmeber][master-plan], we said, "Ok, what we're going to do is we're going to try
"When we [announced our series B round in September][master-plan], we said, "Ok, what we're going to do is we're going to try
and ship the whole [GitLab flow][gitlab-flow], going from idea all the way to production and we're going to ship it by the end of the year."
### 2:42 What is Review Apps?
......@@ -59,7 +59,7 @@ commands."
10:38 Is there a mobile handbook of GitLab for the Kindle?
11:02 What are your thoughts on the short term possiblities of NLP, chat,
11:02 What are your thoughts on the short term possibilities of NLP, chat,
Conversational Development, and local development data sets?
12:38 How do you decide what to work on each release?
......@@ -81,7 +81,7 @@ data insights can you obtain from this group of users?
A couple of months ago, [Jacob Schatz][jacob-twitter], Front End Lead at GitLab, published a post
detailing [why we chose Vue.js][why-vuejs-post] as our JavaScript framework. Since,
this post has spurred tons of conversation on the topic. To faciliate the conversation
this post has spurred tons of conversation on the topic. To facilitate the conversation
further, GitLab Front End engineer Phil Hughes presented a front end update
and host a Q&A session along with Jacob.
......
......@@ -60,7 +60,7 @@ We need the following servers:
For a total of 64 nodes.
We would like to have one common node so that they are interchangable.
We would like to have one common node so that they are interchangeable.
This would mean installing only a few disks per node instead of having large fileservers.
This would distribute failures and IO.
......@@ -108,7 +108,7 @@ That is why we're getting a [E5-2687Wv4](https://ark.intel.com/products/91750/In
This processor costs $2100 instead of $670 but has 4 extra virtual cores and runs continuously on 3 Ghz instead of 2.2 Ghz.
Comprated to the E5-2630v4 that leads to a SPEC score or 1230 instead of 845 and 51.3 SPEC per virtual core instead of 42.3.
For the 4 dual processor database servers this upgrade will cost $11k.
We think it is worth it since the 20-40% of extra performence will buy us the month or two of extra time to distribute the database that we need.
We think it is worth it since the 20-40% of extra performance will buy us the month or two of extra time to distribute the database that we need.
# Disk
......@@ -176,10 +176,10 @@ M1. Should we use 128GB DIMMS to be able to expand the database server later eve
The servers come with 2x 10Gbps RJ45 by default (Intel X540 Dual port 10GBase-T).
We want to [dual bound](https://docs.oracle.com/cd/E37670_01/E41138/html/ch11s05.html) the network connections to increase performance and reliability.
This will allow us to take routers out of service during low traffic times, for example to restart them after a software upgrade.
We think that 20Gbps is enough bandwidth to handle our data access and replication needs, right now our higest peaks are 1 Gbps.
We think that 20Gbps is enough bandwidth to handle our data access and replication needs, right now our highest peaks are 1 Gbps.
This is important because we want to have minimal latency between the Ceph servers so network congestion would be a problem.
Ceph reference designs recommend a seperated front and back network with the back network reserved for Ceph traffic.
Ceph reference designs recommend a separated front and back network with the back network reserved for Ceph traffic.
We think that this is not needed as long as there is enough capacity.
We do want to have user request termination in a DMZ, so our HA proxy servers will be the only ones with a public IP.
......@@ -269,7 +269,7 @@ B10 Can we connect two SAS cables to get 2x 12 Gbps?
B11 What [HBA card](https://www.supermicro.com/products/nfo/storage_cards.cfm) should be added to the controller or does it come with an LSI 3108?
B12 Is it smart to make the controller a seperate 1U box or should we repurpose some of our normal nodes for this?
B12 Is it smart to make the controller a separate 1U box or should we repurpose some of our normal nodes for this?
B13 Any hints on how to test the backup restore (on AWS or our hardware, how often, etc.)?
......
......@@ -422,7 +422,7 @@ There are 3 options to resolve this:
1. Close the MR and create a new one
1. Push new changes to the merge request's source branch
1. Rebase/ammend, and force push to the merge request's source branch
1. Rebase/amend, and force push to the merge request's source branch
### My GitLab Pages website was not updated. How can I solve this?
......
......@@ -399,7 +399,7 @@ to be available on Raspbian Jessie.
Due to a migration to new build infrastructure, several months ago Raspberry PI
packages [started being released](https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1303)
under `debian` distribution of [raspberry pi2 repositiory](https://packages.gitlab.com/gitlab/raspberry-pi2/).
under `debian` distribution of [raspberry pi2 repository](https://packages.gitlab.com/gitlab/raspberry-pi2/).
This was not the original intention and in the following months users needed to do
a [manual change in their package repository sources](https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1303#note_21058665)
to fetch the latest package.
......
......@@ -9,7 +9,7 @@ description: "People asked how team-member-1 is doing after the DB incident of J
ee_cta: false
---
The engineer that gave the unfortunate command to [delete our primary database](/2017/02/01/gitlab-dot-com-database-incident/) was not only on our minds but also of other people. He's known by the community as "team-member-1", as we refered to him by this expression in our public communications during the incident.
The engineer that gave the unfortunate command to [delete our primary database](/2017/02/01/gitlab-dot-com-database-incident/) was not only on our minds but also of other people. He's known by the community as "team-member-1", as we referred to him by this expression in our public communications during the incident.
After we posted [the postmortem of the incident with GitLab.com](/2017/02/10/postmortem-of-database-outage-of-january-31/), we received notes from our community asking how was _team-member-1_ doing. We're here to tell you that.
......
......@@ -101,7 +101,7 @@ can also help to minimize security risks.
> "You might have certain tools to scan dynamically and inject attacks into
your systems, whether that might be directly into your data or your code base.
In the same way that you have human testers doing manual testing, in addtion to the automated testing,
In the same way that you have human testers doing manual testing, in addition to the automated testing,
you might have human users doing the security testing as well." - Victor
Again, if you're developing in small chunks, involving stakeholders earlier on into those environments,
......
......@@ -47,7 +47,7 @@ Many tools exist to help you manage complex scheduling and data aggregation. The
Run drills where you knock things over in a controlled environment and practice putting out those fires.
### Learn how to do incident response
You can learn a lot from actual firefighters. I learned a lot from 3 guys at Blackrock, who were actual firefighters turned ops guys who go around teaching ops orgs how to handle incidents better. When there’s a fire, there’s an incident commander, who is in charge of directing everyone else. Rank isn't important here; this person does not have to be manager, they should just be repsonsible for checking in on everyone for status updates. This person also assigns a scribe to take notes if necessary, although it's better to record calls if you can for better learnings later.
You can learn a lot from actual firefighters. I learned a lot from 3 guys at Blackrock, who were actual firefighters turned ops guys who go around teaching ops orgs how to handle incidents better. When there’s a fire, there’s an incident commander, who is in charge of directing everyone else. Rank isn't important here; this person does not have to be manager, they should just be responsible for checking in on everyone for status updates. This person also assigns a scribe to take notes if necessary, although it's better to record calls if you can for better learnings later.
### Implement "you write it, you wear it"
If you do nothing else in this list, do this. The people who are writing the code, deploying the infrastructure, or touching the guts should be involved in the on-call rotation somehow. These are the best people to fix issues - they’re the ones that know it inside and out. If you don’t have these people on-call, I’m going to boldly say you’re doing it wrong.
......
......@@ -231,7 +231,7 @@ Time flies and I do too! [Siem Reap, Cambodia][siemreap] was up next, with a sma
<img src="/images/blogimages/there-and-back-again-in-one-release/siemreap_airportcollen.jpg" alt="siem reap tuk tuk photo">
</div>
<div class="item">
<img src="/images/blogimages/there-and-back-again-in-one-release/siemreap_crocodiles.jpg" alt="Crocodile farm in residental neighbourhood">
<img src="/images/blogimages/there-and-back-again-in-one-release/siemreap_crocodiles.jpg" alt="Crocodile farm in residential neighbourhood">
</div>
<div class="item">
<img src="/images/blogimages/there-and-back-again-in-one-release/siemreap_angkorwat_tree.jpg" alt="tree in Angkor Wat">
......
......@@ -21,7 +21,7 @@ We **strongly recommend** that all affected GitLab installations
be upgraded to one of these versions **immediately**.
*Note: This is a coordinated release with several other companies and projects,
including `git` itself, which is why it is occuring at 18:00 UTC. As those
including `git` itself, which is why it is occurring at 18:00 UTC. As those
projects release their updates this release post will be updated with more
information.*
......
......@@ -25,7 +25,7 @@ At GitLab, we've addressed this with
the role of [VP of Scaling](/jobs/vp-of-scaling). The
word "scaling" in this case relates to the _organization_ instead of, for example, sales or user-base. Think of the VP of Scaling as a full-time interim
manager rotating between vastly different functions, building teams and
scaleable processes. The job is to "get in" and to figure out how to "get out"
scalable processes. The job is to "get in" and to figure out how to "get out"
responsibly. (As an aside: at first we struggled to come up with a good name for this role and considered everything from janitor/plumber (sweeping /connecting the entire company – vetoed), to
[Mr. Wolf](http://www.indiewire.com/2012/03/being-winston-wolfe-9-reasons-why-pulp-fiction-is-the-management-guide-every-indie-filmmaker-needs-48445/)
(fixes problems on demand – too negative), until eventually settling on the
......@@ -53,7 +53,7 @@ Coming onboard with a new team, I listen to the concerns and ideas from the team
For example, the Support Team faces the dual challenge of a growing _customer
base_ as well as a growing _product_ in terms of product scope and capabilities – straining the team. The "right now" solution involved adding
[support turbos](/handbook/support/#additional-resources-for-the-support-team) and hiring people in multiple timezones to spread the customer ticket load evenly. To make it _scaleable_ beyond the immediate needs is part of the Utopia for any team. In this case, our Support Engineers iterated quickly with the new hires to enable a mostly self-guided onboarding process as well as self-guided pathways for [continuous learning](/handbook/support/advanced-topics).
[support turbos](/handbook/support/#additional-resources-for-the-support-team) and hiring people in multiple timezones to spread the customer ticket load evenly. To make it _scalable_ beyond the immediate needs is part of the Utopia for any team. In this case, our Support Engineers iterated quickly with the new hires to enable a mostly self-guided onboarding process as well as self-guided pathways for [continuous learning](/handbook/support/advanced-topics).
Jumping from team to team in an interim role also provides for a great
opportunity to help spread best practices from team to team, and to erase or
......
......@@ -33,7 +33,7 @@ This process is important for understanding the goals of a research request, sco
After reviewing proposals and prioritizing the issues to tackle in a particular milestone, we figure out the types of research studies to conduct. Some of our most common [remote UX research methods](/2017/12/20/conducting-remote-ux-research/) include survey research, usability testing, first-click testing, and card-sorting. A great way to choose a research method is to ask yourself what you'd like to learn, who you need to reach, and how you want to communicate your questions to the participants (e.g. visually or verbally).
Recently we conducted a research study in support of our [product vision for Concurrent DevOps](/direction/product-vision/). Since GitLab was initially more developer focused, the purpose of this study was to reach out directly to people who work in operations and understand the needs and challenges they face in their roles. To ensure that we reached a broader audience, we conducted a survey followed by user interviews. We learned a lot about the needs of professionals in operations, including their responsibilties, the tools they use, and the versatility of their roles.
Recently we conducted a research study in support of our [product vision for Concurrent DevOps](/direction/product-vision/). Since GitLab was initially more developer focused, the purpose of this study was to reach out directly to people who work in operations and understand the needs and challenges they face in their roles. To ensure that we reached a broader audience, we conducted a survey followed by user interviews. We learned a lot about the needs of professionals in operations, including their responsibilities, the tools they use, and the versatility of their roles.
### Interpreting data and summarizing results
......
......@@ -9,7 +9,7 @@ description: "A recent internal survey revealed that the frontend team culture n
ee_cta: false
---
In Feburary, the [results of GitLab's first anonymous engineering engagement survey were announced][survey-results-announced].
In February, the [results of GitLab's first anonymous engineering engagement survey were announced][survey-results-announced].
The purpose of this survey was to understand the culture of the teams and the organization as a whole, and to identify areas of improvement (if any).
Through this engagement survey, it was identified that out of all the engineering teams, members of the frontend team felt the least favorable about being safe to share their opinions.
......@@ -56,7 +56,7 @@ Leading up to the Content Hack Day, I learned that this iteration of the event r
To my surprise, on the actual day, the frontend team had a 68.7 percent participation rate and eight blog posts. This is especially encouraging for the frontend team culture because the event took place on a public holiday for several team members which, statistically speaking, should have decreased our participation.
Overall, it's been amazing to see the culture shift since the beginning of the year. There are probably still many steps we can take to get better, but I am confident that if the team continues at its current trajectory, the frontend team culture will soon become the example for other teams to learn from about how to foster a postive culture.
Overall, it's been amazing to see the culture shift since the beginning of the year. There are probably still many steps we can take to get better, but I am confident that if the team continues at its current trajectory, the frontend team culture will soon become the example for other teams to learn from about how to foster a positive culture.
Cover image: [Photo][unsplash-photo] by [Kimson Doan][unsplash-author] on [Unsplash][unsplash]
{: .note}
......
......@@ -106,7 +106,7 @@ to be accomplished within a specific time frame.
As part of our next release ([11.2 coming on August 22](https://about.gitlab.com/direction/#112-22-aug)),
we're shipping Milestone lists. Similar to our assignee lists, you will be able
to quickly create a milestone view directly from your board. This is particulary
to quickly create a milestone view directly from your board. This is particularly
useful for those leveraging an Agile workflow. With the milestone list, you can
easily move issues (stories) between different milestones (i.e. sprints, iterations).
......
......@@ -83,7 +83,7 @@ Barbie also reiterated our commitment to [diversity](/handbook/values/#diversity
### [Product update](https://youtu.be/ZgFqyXCsqPY?t=33m58s)
To fill us in on what's new with GitLab the product, we're joined by [William Chia](/company/team/#thewilliamchia), Manager, Product Marketing. We delivered the full sofware development lifecycle at the end of 2016, then set our sights on [Concurrent DevOps](/2017/10/11/from-dev-to-devops/). William shares how conversations with users and customers alerted us to the "toolchain crisis" and how this has inspired us to deliver Concurrent DevOps with a single application covering the entire DevOps lifecycle.
To fill us in on what's new with GitLab the product, we're joined by [William Chia](/company/team/#thewilliamchia), Manager, Product Marketing. We delivered the full software development lifecycle at the end of 2016, then set our sights on [Concurrent DevOps](/2017/10/11/from-dev-to-devops/). William shares how conversations with users and customers alerted us to the "toolchain crisis" and how this has inspired us to deliver Concurrent DevOps with a single application covering the entire DevOps lifecycle.
#### [User perspective: Why GitLab?](https://youtu.be/ZgFqyXCsqPY?t=51m26s)
......
......@@ -36,6 +36,6 @@ There's no one, single factor that will get you into your account – the spirit
These challenges aren't made public – we're not going to give away exactly what you need to access a 2FA account, obviously 😆 We'll keep [iterating](/handbook/values/#iteration) on them too.
As mentioned, this new workflow is really a result of collaboration between Support and Security. Having identified that our existing process was less than ideal, we asked for an audit of our proposal from Security, to get their stamp of approval and ensure that we were leveraging our internal resources to keep our users' accounts safe. You can [check out the issue for this consulation with Security here](https://gitlab.com/gitlab-com/security/issues/45) for the full discussion.
As mentioned, this new workflow is really a result of collaboration between Support and Security. Having identified that our existing process was less than ideal, we asked for an audit of our proposal from Security, to get their stamp of approval and ensure that we were leveraging our internal resources to keep our users' accounts safe. You can [check out the issue for this consultation with Security here](https://gitlab.com/gitlab-com/security/issues/45) for the full discussion.
To avoid resetting your 2FA altogether, here's [how to keep your GitLab account safe and accessible](/2018/08/09/keeping-your-account-safe/).
......@@ -57,7 +57,7 @@ problem described by the customer before.
1. The full error message read, `fatal: Couldn't read ./packed-refs: Stale file handle`.
2. The error seemed to start when they started a manual Git garbage
collection run via `git gc`.
3. The error would go away if a system adminstrator ran `ls` in the
3. The error would go away if a system administrator ran `ls` in the
directory.
4. The error also would go away after `git gc` process ended.
......
......@@ -42,7 +42,7 @@ During the [GitLab Hackathon](/community/hackathon/) in September, one of our [C
## Where do we need help?
As you can see from the screenshot below, GitLab is almost fully translated into several languages, such as Chinese (both Simplifed and Traditional), French, German, Filipino, Brazilian Portuguese, Ukranian, etc. However, many languages are in early stages, with a lot of translation left to be done and may also need [proofreaders](https://docs.gitlab.com/ee/development/i18n/proofreader.html) to help review and approve translations. You can find steps to becoming a proofreader also outlined in [the proofreader documentation](https://docs.gitlab.com/ee/development/i18n/proofreader.html#become-a-proofreader).
As you can see from the screenshot below, GitLab is almost fully translated into several languages, such as Chinese (both Simplifed and Traditional), French, German, Filipino, Brazilian Portuguese, Ukrainian, etc. However, many languages are in early stages, with a lot of translation left to be done and may also need [proofreaders](https://docs.gitlab.com/ee/development/i18n/proofreader.html) to help review and approve translations. You can find steps to becoming a proofreader also outlined in [the proofreader documentation](https://docs.gitlab.com/ee/development/i18n/proofreader.html#become-a-proofreader).
![GitLab translation status](/images/blogimages/translation-blog/gitlab_translation_status.png){: .shadow.medium.center}
......
......@@ -44,7 +44,7 @@ When demand surpasses current capacity, it can be stressful to resolve existing
#### Changing mindsets in organizations to adopt faster, iterative approaches
Some development teams are slowed down by inefficient toolchains or outdated workflows because their organizations are resistent to change and adopting new practices. Introducing new ideas and methodologies can be an especially complex process in organizations that create products for industries with more restrictions and regulations than others.
Some development teams are slowed down by inefficient toolchains or outdated workflows because their organizations are resistant to change and adopting new practices. Introducing new ideas and methodologies can be an especially complex process in organizations that create products for industries with more restrictions and regulations than others.
> "Most blockers that arise are put in their own way. I would prefer to iterate while they rather plan everything out for long periods of time. Their own processes get in their way because they don’t think they can move faster. Many of their processes are filled with errors and take days or weeks. They’ve always done things a certain way and are not really willing to make a change."
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment