|
| 1 | +# Astropy Maintainer Mentoring Program Proposal |
| 2 | + |
| 3 | +## Project team |
| 4 | + |
| 5 | +The grant will go to [Aperio Software Ltd.](https://aperiosoftware.com), and the |
| 6 | +following people will be working on the project: |
| 7 | + |
| 8 | +* Thomas Robitaille - Coordination committee member and astropy core maintainer. |
| 9 | +* Stuart Mumford - astropy.visualization and infrastructure maintainer. |
| 10 | +* Heather Mumford - Learning and Development professional with extensive |
| 11 | + experience in developing and delivering coaching and mentoring programmes. |
| 12 | + |
| 13 | +We believe that this team encompasses both the knowledge of mentoring programs |
| 14 | +in general as well as the specific needs of the Astropy community to develop an |
| 15 | +effective maintainer mentoring program. |
| 16 | + |
| 17 | +## Project Summary |
| 18 | + |
| 19 | +This project is to set up a lightweight (as in easy to run and maintain) but |
| 20 | +formal mentoring program to encourage, recruit, and train both new maintainers |
| 21 | +for the astropy core and coordinated packages, as well as people into other |
| 22 | +roles. |
| 23 | + |
| 24 | +There are two primary goals for the mentoring scheme: |
| 25 | +1. To increase the number of people in maintainer and other roles in the Astropy |
| 26 | + community. |
| 27 | +2. To provide a more structured way to facilitate succession of people into |
| 28 | + vacant roles. |
| 29 | + |
| 30 | +This will reduce the projects reliance on the current small number of people in |
| 31 | +critical roles. This mentoring program is *not* aiming to recruit more |
| 32 | +contributors at this time. |
| 33 | + |
| 34 | +## Project Work Plan |
| 35 | + |
| 36 | +This project is split into three phases. At each phase we will actively solicit |
| 37 | +feedback from the Astropy community to continually improve the program. |
| 38 | + |
| 39 | +### Phase 1: Design Program and Produce Documentation |
| 40 | + |
| 41 | +In this phase we will design the program and develop all the documentation |
| 42 | +needed for all participants, this will include: |
| 43 | + * Introduction to the program, including its scope and goals. |
| 44 | + * Requirements for mentors and mentees: what makes a good mentor/mentee, what |
| 45 | + is expected of program participants. |
| 46 | + * A mentor handbook containing all the information needed to help a mentor |
| 47 | + through the program. |
| 48 | + * A mentee handbook containing all the information needed to help a mentee |
| 49 | + through the program. |
| 50 | + * Guidelines for mentors on when their mentees might be ready to "graduate" to |
| 51 | + a maintainer role. |
| 52 | + * Guidelines for when mentees might exit the program without "graduating" to a |
| 53 | + maintainer role. |
| 54 | + |
| 55 | +### Phase 2: Implement and Run the Mentor Program for the first year |
| 56 | + |
| 57 | +In this phase, the program will be run and coordinated for one year. |
| 58 | + |
| 59 | +Running the programme for the first year will involve: |
| 60 | + |
| 61 | + * Identify suitable mentors based on criteria developed in phase 1. |
| 62 | + * Work with the wider Astropy community to identify potential mentees, based |
| 63 | + on criteria developed in phase 1. |
| 64 | + * Train mentors and mentees on what good mentoring relationships look like and |
| 65 | + what is expected of them. |
| 66 | + * Pair mentors and mentees, considering time-zones, personalities, and support |
| 67 | + required. |
| 68 | + * Monitor progress through evaluations and check-ins. |
| 69 | + * Graduate mentees into suitable Astropy roles as and when appropriate. |
| 70 | + |
| 71 | +The program for the first year will be administered using the minimal amount of |
| 72 | +new technology possible (instead relying on existing solutions), with the focus |
| 73 | +on learning what works for the Astropy community and what can be improved and |
| 74 | +automated in the future. |
| 75 | + |
| 76 | +### Phase 3: Review and Improvements |
| 77 | + |
| 78 | +Towards the end of the first year of running the program a review of how well |
| 79 | +the program has achieved its objectives will be performed in collaboration with |
| 80 | +the participants from the first year and the wider community. |
| 81 | + |
| 82 | +It is expected that any significant changes to the program of development of |
| 83 | +software to help with administering the program would form part of a new |
| 84 | +proposal in the next cycle for evaluation by the community. |
| 85 | + |
| 86 | +### Budget |
| 87 | + |
| 88 | +The total budget request is for $15k, which is for 100 hours of contractor work |
| 89 | +at $150 per hour, split up as 3 days of work (24 hours) each for phases one and |
| 90 | +three and one hour a week for phase 2 (52 hours). |
0 commit comments