- You have availability in your schedule to meet with your mentee on a bi-weekly basis for at least 30 minute meetings for the entire length of the program
- You plan to make every effort to attend all live trainings included in the program structure
- You are not on a [Formal Coaching plan](/handbook/leadership/underperformance/#options-for-remediation) or PIP (Performance Improvement Plan)
- You can complete the [DIB training certification](https://university.gitlab.com/access/saml/login/internal-team-members?returnTo=https://university.gitlab.com/learn/course/dib-training-certification) before the program begins
Note: Anyone at GitLab, regardless of gender identity, can apply to be a mentor in the Women at GitLab mentorship program.
@@ -27,12 +27,12 @@ description: "The GitLab Learning Restructure Working Group aims to create a pla
### Update /Learn
1. Inventory existing training programs to establish a SSoT ==> Complete, established in [GitLab Learn](https://university.gitlab.com/)
1. Update <https://university.gitlab.com/>to capture SSoT and provide more clarity on which training is for what ==> Complete
1. Inventory existing training programs to establish a SSoT ==> Complete, established in GitLab Learn
1. Update to capture SSoT and provide more clarity on which training is for what ==> Complete
### Create future coordination processes and plan
1. Document in the Handbook a process that DRIs working on learning content will follow to keep [GitLab Learn](https://university.gitlab.com/)up-to-date, to ensure it remains the SSOT of GitLab-produced learning content. This will include existing content and planned content. ==> Complete, documented and established #gitlab-learn-updates Slack channel for reminders to update and x-team communications.
1. Document in the Handbook a process that DRIs working on learning content will follow to keep GitLab Learnup-to-date, to ensure it remains the SSOT of GitLab-produced learning content. This will include existing content and planned content. ==> Complete, documented and established #gitlab-learn-updates Slack channel for reminders to update and x-team communications.
title:Development Department Learning and Development - Reliability
---
## Goal of this training
As we have a renewed focus on reliability in engineering to reduce outages, we have made many changes to the handbook, production documentation, and our processes. While we have announced them via multimodal communication (EWIR, slack, email, meetings), not everyone has likely seen and internalized all of the important changes.
We want to gather all the crucial changes, explain why we made them, discuss a summary, and link to where you can find more information.
This material is available as a [learning pathway on GitLab's Level Up](https://university.gitlab.com/access/saml/login/internal-team-members?returnTo=https://university.gitlab.com/learn/course/development-reliability).
[Improving SUS](https://docs.google.com/presentation/d/1kMZcRnOjuQ0K3TtT1YxedhFb5-Ej_cr2mXxeeJ9sbZ0/edit#slide=id.g98418cf290_0_29) - slides 9 through 14 in particular
[Course on backwards compatibility](https://university.gitlab.com/access/saml/login/internal-team-members?returnTo=https://university.gitlab.com/learn/course/backwards-compatibility-training)
## How to use the stage group dashboards to understand how a feature category performs
@@ -23,7 +23,7 @@ Not only are buddies helpful to someone that has just started with GitLab, but a
- Be sure to suggest [location channels](/handbook/communication/chat/#location-channels-loc_) and [Social Slack Groups](/handbook/communication/chat/#social-groups) where they can immediately plug in with other team members who appreciate similar things.
1.**Ask where they need help and connect them with the experts**. Buddies should make the effort to connect new GitLab team-members with subject matter experts if your assigned team member requests additional help in a given area. Examples are below.
- For new GitLab team-members who have not worked in a [remote organization](/handbook/company/culture/all-remote/) before, they may need assistance in thinking through an ideal [workspace](/handbook/company/culture/all-remote/workspace/) and embracing [informal communication](/handbook/company/culture/all-remote/informal-communication/). Consider asking seasoned remote colleagues in the `#remote` Slack channel to reach out and answer questions.
- If they're new to [Git](https://university.gitlab.com/), consider asking experts in the `#git-help` Slack channel to reach out and offer a tutorial.
- If they're new to Git, consider asking experts in the `#git-help` Slack channel to reach out and offer a tutorial.
- If they're new to [Markdown](https://about.gitlab.com/blog/2018/08/17/gitlab-markdown-tutorial/), consider asking experts in the `#content` Slack channel to reach out and offer support.
1.**Help with the team page.** For less technical new hires, adding themselves to the [team page](/handbook/company/team/) might feel like the most daunting task on the onboarding issue. Offer to help with the process. This doesn't necessarily have to happen on day one, but you should let them know that you're available to help if and when they need it. Consider scheduling a second meeting later in the week to walk them through [the process](/handbook/about/editing-handbook/#add-yourself-to-the-team-page)
- In particular, help them to create their SSH key as this tends to be a sticking point for many new hires. You can also show them [Lyle's walkthrough](https://youtu.be/_FIOhk03VtM).
