-
Notifications
You must be signed in to change notification settings - Fork 70
Outreach planning checklist
James O. D. Hunt edited this page Jan 12, 2024
·
17 revisions
If you are interested in being involved in an outreach project, please contact the Outreach coordinators to discuss your idea for an outreach project.
The following items must all be completed before an outreach project can start.
Done? | When? | Task | Notes |
---|---|---|---|
☐ | Initially | Discuss and agree the content with a coordinator | We can be flexible, but the current Kata focus is on rust programming |
☐ | Initially | Agree project start and end dates | |
☐ | A few days before start date (latest) | Provide details of the students who will be involved | Name, email address, GitHub username and Slack ID |
☐ | Before contacting mentors | Discuss timezones differences | Mentors could be anywhere in the world, so timezones must overlap within "normal work hours" |
☐ | 4-8 weeks (minimum) before start date | Provide details to mentors and get their written agreement to attend |
The following items are recommended, but not essential. However, to maximise the chance of a successful project, we would strongly encourage you to complete these tasks too:
Done? | When? | Task | Notes |
---|---|---|---|
☐ | After initial agreement | Create contingency plan in case hardware not available or students absent / mentors unavailable | Identify at least one "backup mentor" |
☐ | 3 weeks before start date | Meeting with the coordinator and the mentors to talk through the "pre-flight checklist" | Allows time to arrange for hardware, etc |
☐ | 1 week before start date | Meeting with coordinator, students and mentor to talk through the "pre-flight checklist" | Sets expectation and helps students get "up to speed" to help project run smoothly with no surprises! |