Engineers in this team are dedicated to our Engineering Productivity efforts.
|Kyle Wiebers||Interim Quality Engineering Manager, Engineering Productivity|
|Rémy Coutable||Staff Backend Engineer, Engineering Productivity|
|Mark Fletcher||Backend Engineer, Engineering Productivity|
|Jen-Shin Lin||Backend Engineer, Engineering Productivity|
|Albert Salim||Senior Backend Engineer, Engineering Productivity|
The global issue board for the team can be found here: Quality - Engineering Productivity Team
The Engineering Productivity team creates metrics in the following sources to aid in operational reporting.
This metric captures how many Merge Requests are merged into customer facing projects divided by the number of product team members.
Customer facing projects are projects which would come with an installation of GitLab. The current list can be found with all the projects identified in the
projects_part_of_product.csv file in the
Product team member is defined as all non-VP or Director role in Development, UX, Quality, and Product Management.
With this measure, there is a preference towards adding new projects into the existing product. In the event that a new GitLab project is included in the product that a customer would receive then please open an issue on the quality team tasks project.
Within the issue, please add details on how this project is included with an Omnibus or Cloud Native installation of GitLab for consideration by the Engineering Productivity team. The team will evaluate the request and make any updates to charts and metrics in the sources listed above.
The Engineering Productivity team will make changes which can create notification spikes or new behavior for GitLab contributors. The team will follow these guidelines in the spirit of GitLab's Internal Communication Guidelines.
For changes which dogfood new pipeline features or changes to the pipeline flow, the team will communicate on the company call, add to the Engineering Week in Review, and #development in Slack.
For all other pipeline changes, the team will add to the Engineering Week in Review and #development in Slack.
Communication guidelines are documented on the triage-ops handbook page