The mission of the core team is to represent the wider GitLab community and ensure that everyone can contribute. The arrangement of the core team is similar to those of the Ruby, Ruby on Rails, Linux, and PostgreSQL projects. The core team is not bound to any single organization and primarily consists of volunteers that have made significant contributions to GitLab in development, documentation, online community forums, translation, UX design, etc., as well as up to two GitLab company team members. All core team members are encouraged to engage with the wider community and help contributors by triaging issues and reviewing merge requests.
Core team members can be reached by
group, in an issue or a merge request, which also includes an
issue tracker, a
wiki, and a
to contact through email. You can also reach out core team members at the
gitter channel or the
The core team has also
calls. During this call, core team members are encouraged to discuss topics related to
the GitLab open source
and the wider
Current members can nominate a new member from the wider community at any time using a confidential issue to limit any possible negative feedback in the smallest setting possible. The nominee will be added to the core team if they accept the nomination and have received positive votes from two-thirds (2/3) of all current core team members within a two week period. Any core team member can gracefully stand down and become a core team alumni if they think they can no longer allocate time for contributing. More information is available in the Core Team handbook page.