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.
Provide a durable, performant, and reliable Git storage layer for GitLab.
The following people are permanent members of the Gitaly Team:
|Zeger-Jan van de Weg||Engineering Manager, Gitaly|
|Jacob Vosmaer||Staff Backend Engineer, Gitaly|
|Christian Couder||Senior Backend Engineer, Gitaly|
|James Fargher||Senior Backend Engineer, Gitaly|
|Pavlo Strokov||Senior Backend Engineer, Gitaly|
|Sami Hiltunen||Backend Engineer, Gitaly|
|John Cai||Backend Engineer, Gitaly|
|Paul Okstad||Senior Backend Engineer, Gitaly|
|Patrick Steinhardt||Senior Backend Engineer, Gitaly|
The following members of other functional teams are our stable counterparts:
|Mark Lapierre||Senior Software Engineer in Test, Create:Source Code (primary) & Create:Gitaly (secondary)|
|New Vacancy - James Ramsay (Interim)||Senior Product Manager, Create:Gitaly|
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.
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.