A hackfest to revamp our onboarding and group mentoring in infrastructure and releng teams.
We currently have a scattered collection of documentation and information about contributing to the infrastructure and releng teams. We would like to map out and organize our onboarding documentation and progression and expore new ideas to get new or casual contributors involved.
We want to handle:
- Marketing / expectations: what do we require of contributors? Why would someone want to contribute? This should include causal contributors that just want to fix some issue but don't have time or desire to contribute long term as well as contributors that want to learn and grow skills while helping out, to experenced contributors that want to share their knowledge and experence.
- Clear steps on how to onboard. (joining fi-apprentice, where things are, etc)
- Pool of "things to do" to gain more experence / trust. (possible badges?) (run meetings, handle oncall, help with tickets, fix alerts, etc)
- Clear expectations for gaining more access and being able to do more.
- Process for stepping back/handing off when time or interest changes.
Ideally we would finish this hackfest with an outline of the above to run by all the infra and releng folks that might not be at flock and then have a clear idea of the documentation we need to create. Bonus points for drafts of some of the docs as part of the session.
