-
Notifications
You must be signed in to change notification settings - Fork 70
Outreach mentor checklist
James O. D. Hunt edited this page Feb 7, 2023
·
29 revisions
This page lists some of the tasks a Kata Containers outreach mentor should undertake.
By participating in a Kata Containers Outreach project you agree to be bound by the "mentors golden rule":
Mentors Golden Rule:
Keep asking the students if they need help, and if they do, help them!
| When? | Category | Type | Task | Notes |
|---|---|---|---|---|
| week -1 | team | required | Identify code areas for students to work on | |
| week -1 | team | required | Identify potential list of tasks for students to work on (GitHub issue list ideally) | |
| week 1 | team | required | Send contact details of all mentors to students | |
| week 1 | team | required | Add GitHub and Slack usernames for all students to the outreach wiki page | GitHub user and Slack usernames only |
| week 1 | team | required | Add all GitHub users to the outreach team | |
| week 1 | team | required | Arrange a weekly meeting (Zoom / MS Teams) at a suitable time for all students | |
| week 1 | team | required | Talk students through the student checklist | Identify students without required skills |
| week 1 | team | required | Ask each student what they particularly want to get out of the project | |
| week 1 | team | recommended | Identify any upcoming public/personal holidays, exam weeks, end of term travel, etc | |
| week 1 | team | essential | Work with students and teacher/professors to identify SMART task(s) for each student or group of students | |
| week 2 | code | required | Ensure students have installed rust | Any problems? |
| week 2 | code | required | Ensure students have installed Kata and created a Kata container | Any problems? |
| week 2 | code | required | Discuss progress learning rust | Students should have attempted to write some rust code by this stage |
| week 3 | familiarisation | recommended | Play with agent-ctl
|
Build it too |
| week 3 | familiarisation | recommended | Play with kata-ctl
|
Build it too |
| week 3 | rust | optional | Read This Week in Rust | Sources: https://github.com/rust-lang/this-week-in-rust |
| final week | team | required | Ask students for feedback on the overall project (good and bad!) | Add it to the ideas page |
| final week | team | optional | Ask students if they would consider writing a blog post on Kata, the community, etc. |
General agenda:
- Any opens/problems/concerns/worries?
- Round robin "status update" from each student:
- Achievements since the last meeting? Ideally "yes" 😄
- Any problems? Note: This should always be "yes" as we'd like to understand the issues faces and how they overcame them! Plus, it encourages the students to talk about (minor) issues as it will hopefully encourage them to raise any big issues later!
- Discuss plan for next meeting.
- Offer to present to students on particular topics of interest.
| When? | Category | Type | Task | Notes |
|---|---|---|---|---|
| week 1 | read | strongly recommended | Talk through the project overview and onboarding presentation | |
| first few weeks | contribute | strongly recommended | Present on how to run and write new unit tests | |
| any time | code | recommended | async rust presentation | Most of the new code uses asynchronous rust, which requires a different programming paradigm |