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
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.
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.
Winnie is a software developer from Germany.
He introduced GitLab to his company when a web interface for Git was needed. Since then he has helped GitLab improve by posting merge requests and commenting on issues. When not at work, Winnie enjoys gardening—dreaming of a tomato forest in his backyard.
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.