|
| 1 | +## Mentorship Program for New Ansible Release Management! |
| 2 | + |
| 3 | +Under this initiative, we’ll mentor and train new community members to become active member of Ansible Release Management.This program offers several key benefits by establishing a formal process for training future release managers. |
| 4 | + |
| 5 | +### Improved Efficiency and Knowledge Transfer |
| 6 | + |
| 7 | +Structured Onboarding: By laying out the steps and process for training new release managers, the program creates a more efficient and standardized way to bring new people up to speed. |
| 8 | + |
| 9 | +Structured Knowledge Sharing: Instead of relying on ad-hoc learning, the program ensures that knowledge is shared in a more organized way. This helps prevent critical information from being lost or overlooked when a new person joins the team. |
| 10 | + |
| 11 | +### Increased Team Resilience and Capacity |
| 12 | + |
| 13 | +**Diverse Contributor Pool**: The program brings in new contributors from different time zones. This provides a wider network of people who can answer questions and assist with tasks, reducing the burden on the current team. |
| 14 | + |
| 15 | +**Pre-Vetted Candidates**: The program prepares contributors from a “readiness perspective,” meaning you will have a group of people who are already familiar with the process and have a solid foundation of knowledge. |
| 16 | + |
| 17 | +### Enhanced Project Visibility and Contributor Recognition |
| 18 | + |
| 19 | +**Shadowing Opportunities**: The program allows new contributors to shadow current release managers. This provides an extra set of eyes on the release process, which can help catch potential issues. |
| 20 | + |
| 21 | +**Contributor Recognition**: Participants who shadow release managers will gain recognition for their efforts, similar to the Kubernetes model. This can motivate new contributors and make the program more attractive to potential candidates. |
| 22 | + |
| 23 | +### What the Program Hopes to Deliver? |
| 24 | + |
| 25 | +The program is designed to equip participants with the essential knowledge and skills needed for release management, including: |
| 26 | + |
| 27 | +- How to become an active member of the Release Management working group. |
| 28 | + |
| 29 | +- The process for reviewing pull requests related to release management. |
| 30 | + |
| 31 | +- How to handle and manage the Ansible Community Package release and the Community Execution Environment (Base and Minimal) release. |
| 32 | + |
| 33 | +### Note |
| 34 | + |
| 35 | +The program is a possibility, not a guarantee. It promises to enable people with the necessary knowledge and skills, but it does not promise to make them a release manager with immediate effect. Its main goal is to share knowledge and empower future contributors. |
| 36 | + |
| 37 | + |
| 38 | + |
| 39 | +Now this document to captures steps, methods and track progress of the mentorship program. This intends to help the mentees (interested new release managers) and mentor of the Ansible to be able to understand and get the overview of the program. |
| 40 | + |
| 41 | + |
| 42 | +## Step: 1 : |
| 43 | + |
| 44 | +- Call for volunteers over Forum Post and Bullhorn |
| 45 | + |
| 46 | + |
| 47 | +## Step 2 : Introductory call |
| 48 | + |
| 49 | +Discuss the following during the call |
| 50 | + |
| 51 | +- Introduction |
| 52 | +- Ansible Community overview |
| 53 | +- Communication channels |
| 54 | +- Semvar |
| 55 | +- the community release processes. |
| 56 | +- Ansible Community Package Release |
| 57 | +- Release concepts |
| 58 | + |
| 59 | + |
| 60 | +## Step 3: Share the resources on the following concepts with the mentees: |
| 61 | + |
| 62 | +- see the `training_resources.md` in the this repo. |
| 63 | + |
| 64 | + |
| 65 | +**THIS IS A LIVE DOCUMENT WHERE WE WILL CAPTURE THE STEPS WE TAKE DURING THE MENTORSHIP JOURNEY** |
0 commit comments