Onboarding Checklist
This checklist is here to guide your first steps and help you feel settled. Not everything will apply to everyone - feel free to adapt it based on your role or current project.
Week 1 – Getting Oriented
-
Set up your work email and relevant accounts
→ List of tools and platforms we use: [Insert link]
-
Join our communication channels
→ IRC / Matrix / chat channels: [Insert link or instructions]
-
Get access to relevant Git repositories
→ Repository list and access guidance: [Insert link]
-
Introduce yourself to the team
→ Preferred channel and suggested format: [Insert link]
-
Book a 30-min intro call with your main contact
→ Who this is: [Insert name/role/template invite]
-
Review the handbook and team resources
→ Start here: [Insert link]
-
Check for any team-wide updates or key discussions
→ Where to find this: [Insert link to mailing list, changelog, or update doc]
-
Set up your hardware / dev environment
→ Setup guide: [Insert link or checklist]
Week 2 – Getting into the Work
-
Review current priorities for your project
→ Project overview: [Insert link]
-
Get familiar with our development and review process
→ Guide to submitting patches, using CI, etc.: [Insert link]
-
Read through documentation for the codebase(s) you’ll be contributing to
→ Docs and READMEs: [Insert links]
-
Submit your first patch, doc edit, or contribution
→ Where to send it / how to tag reviewers: [Insert info]
-
Reach out with any questions or uncertainties
→ How we usually handle this: [Insert guidance]
-
Let us know if you're missing access or context
→ Who to talk to: [Insert contact]
Ongoing
-
Join our next in-person meetup (if timing aligns)
→ Upcoming dates and details: [Insert link]
-
Share any blockers or feedback with your main contact
→ We encourage regular check-ins and openness
-
Contribute to documentation or onboarding materials
→ Docs you can help improve: [Insert link]
-
Stay curious—this is a learning culture, and support is always nearby