Idea for cross-team onboarding task
As a way to have Developers be (or start to be) comfortable with the production environment of GitLab.com where their features and services run,
AND
As a way to have Production Engineers be (or start to be) familiar with the code base of the GitLab application,
I'd like to propose that we create an onboarding task for each role, namely:
-
For Developers: make a change in production (i.e. on GitLab.com). The idea is to get comfortable with the production architecture and environment but not to spend more than 0.5-1 day on this onboarding task. -
Read about the production architecture -
Examples can include building monitoring and alerting for a feature or service; building an automation in gitlab-cog; etc.
-
-
For Production Engineers: contribute a merge request to GitLab's code base. The idea is to get comfortable with the application architecture and codebase, but not to spend more than 0.5-1 day on this onboarding task. -
Read about the application architecture -
Contribute a merge request to one of the following repos: gitlab-ce, gitlab-ee, gitaly, workhorse, gitlab-runner
-
Thoughts on this, @stanhu @pcarranza @DouweM @smcgivern @rymai @ayufan @andrewn ?
Edited by Ernst van Nierop