Developer Tooling team
Mission
- Build state-of-the-art developer tools that are efficient and reliable, empowering developers to keep their development environments up-to-date painlessly.
- Enable contributors to contribute to our tools.
- Measure what matters: improvements in developer experience, efficiency, and toil reduction, using both quantitative and qualitative metrics.
Vision
The Developer Tooling team’s vision is to create tools that enable GitLab team members and the wider community to contribute to GitLab efficiently, without the friction and manual toil that often come with working on large, complex software projects like GitLab.
Areas of responsibilities
Team structure
Members
Team Members | Role |
---|---|
Mohga Gamea | Engineering Manager |
![]() |
Backend Engineer, Developer Tooling |
![]() |
Backend Engineer, Developer Tooling |
![]() |
Frontend Engineer, Developer Tooling |
![]() |
Staff Backend Engineer, Developer Tooling |
Stable counterpart
Person | Role |
---|---|
![]() |
GDK Project Stable Counterpart, Application Security |
OKRs
Objectives and Key Results (OKRs) help align our sub-department towards what really matters. These happen quarterly and are based on company OKRs. We follow the OKR process defined here.
Here is an overview of our current OKRs.
Communication
Description | Link |
---|---|
GitLab Team Handle | @gl-dx/developer-tooling |
Slack Channel | #g_developer_tooling |
Team Boards | Team Board |
Issue Tracker | gitlab-org/dx/tooling/team |
6a7eccf0
)