index.html.md 1.54 KB
Newer Older
1
---
2
layout: handbook-page-toc
3 4 5
title: "Gitaly Team"
---

6
## On this page
7
{:.no_toc .hidden-md .hidden-lg}
8 9

- TOC
10
{:toc .hidden-md .hidden-lg}
11

12 13 14
## Common Links

- Gitaly's [public issue tracker](https://gitlab.com/gitlab-org/gitaly/issues/).
15 16 17
- [Chat channel](https://gitlab.slack.com/archives/g_create_gitaly); please use
the `#g_create_gitaly` chat channel for questions that don't seem appropriate to
use the issue tracker for.
18 19 20

## What is the Gitaly team?

21 22 23 24
The Gitaly team is responsible for building and maintaining systems to ensure
that the git data storage tier of GitLab instances, and _GitLab.com in particular_,
is fast. Gitaly migrated GitLab.com away from NFS, and is now working on a
highly available Git storage layer.
25

26
### Development
27 28 29

The goals of Gitaly are

30
1. Deliver a reliable storage layer
31 32
1. Optimize git services using caching

Brittany Rohde's avatar
Brittany Rohde committed
33
See [the design document](https://gitlab.com/gitlab-org/gitaly/tree/master#reason) for an in-depth explanation behind the motivation for GitLab.
34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49

### Process

#### Onboarding

When a new developer joins Gitaly, their resposibility will include maintaining
the Gitaly project from their first day. This means that the developer will get
`Maintainer` access to the repository and will be added to the
`gitlab.com/gl-gitaly` group so they appear in merge request approval group.

#### Retrospectives

At the beginning of each release, the Gitaly EM will create a retrospective issue
to collect discussion items during the release. The first weekly Gitaly meeting
after the 18th that issue will be used to discuss what was brought up.