Dmitriy started GitLab in September 2011 and has released it every month on the 22nd since then. He wanted to make a great and free project management system that he could use every day. He loved to work on GitLab so much that in January of 2013 he began to work on GitLab fulltime. When he has time he loves to code a major new GitLab feature in two days. He loves a good Martini and a merge request that can be accepted without comments.
- GitLab CE Lead
Marin loves to develop in Rails but has also grown an interest in operations, specifically Amazon Web Services and Opscode Chef. When video conferencing with him you get a cat running accross the room as a bonus. He is notorious for starting early in the morning just after breakfast and not having lunch until his workday is over. You would expect him to be hungry and grumpy the last few hours but as long as his internet connection is up he is always friendly and upbeat. He loves travelling and talking. A lot of talking. A lot.
Robert is a developer who loves science and technology. He currently studies telematics with focus on digital signal processing at Graz University of Technology. In his spare time he enjoys mountain biking, skiing and photography. When not in front of his computer, Robert can often be found with a glass of good single malt whisky or beer in his hand discussing sports and open source software.
- issue triage lead
Jacob is a doctor in logic. He likes to understand and explain complex technical systems. That helps with his job as a senior service engineer at GitLab.com. In his spare time he likes to read Unix books and has a second career as tango DJ in Amsterdam.
a golden gear medal for bravery and acts of merit serving in the trenches of GitLab Omnibus
- unix security
Sytse saw the first ruby code in 2007 and loved it so much he dove head first into programming. Before that he was engaged in business administration roles and combining that with software development is his passion. He is always looking to make a template out of something or to automate a process. His team members suspect he has todo list and reminders for everything, including breakfast and getting his hair cut. He loves a good beer and organizing a trip to a conference.
- readme and documentation
- interface text
Achilleas is an open source enthusiast that tries to get involved in as many projects as possible. His linux distro of choice is Archlinux, although since 2013 he's enjoying making packages for Fedora. You'll often listen him quoting from his favorite movie "The Big Lebowski". When he is not in front of his laptop (a Thinkpad X220 of course!) he practises Aikido, reads Bukowski and enjoys a good meal he cooked all by himself.
- GitLab Recipes Lead
Hannes is a developer who loves open source. His motto is: "If something is broken that you need and you are able to fix it, don't just talk about it. Fix it!" In his spare time he enjoys swimming, badminton and relaxing with his friends. When he is not in front of his computer, he can often be found on various camping places where he helps out the scouts of his hometown.
Kamil is a low-level programming enthusiast with years of experience in building apps for all platforms. He is also a security, virtualization and graphics expert with a variety of programming languages in his toolkit together with deep operating systems architecture knowledge. He's focusing lately on security principles of mobile platforms and the "container revolution". In his spare time he likes to run, cycle and play good games, although not all at the same time.
- GitLab CI Lead
Stan started working on GitLab because he just wanted to see more Slack notifications, but his interest in the project snowballed after that. Stan has spent close to 20 years writing software at almost every level of the stack, from Linux kernel code to Web applications. Having retired from running marathons, he now spends his free time preparing for triathlons and photographing events.
James is a software developer in Orlando, FL, US.
He started following GitLab development in 2012 looking for a better git management interface. Needless to say, it was love at first sight. Since then he's has been supporting GitLab users in the freenode IRC channel.
Many core team members did a lot of fixes, improvements and refactoring. The above list indicates some of their specialties but it is not complete.
GitLab core team members who are no longer active but whose work is very much appreciated can be found on the core team alumni page.
The GitLab core-team is not bound to any single (not-)for-profit organization. This arrangement is similar to those of the Ruby, Ruby on Rails, Linux and PostgreSQL projects. There is no formal process, team members discuss topics on the private gitlab-core mailing list and Slack channel. You can get invited for the core team after contributing to GitLab for a sustained period of time. You can contribute by coding but also by giving feedback on merge requests, triaging on the issue tracker or helping out on the mailinglist. Core contributors are invited after a proposal from a core-team member that gets two positive responses on the core-team mailing list and no negative ones.