Welcome to the Rootski.io knowledge base. The purpose of this space is to make contributing to Rootski.io as straightforward as possible.

<aside> 📌 If you're new here, hi! Read through this page and go through the "Onboarding" page linked at the bottom of this page.

</aside>

Important Links

Consider this place as the "source of truth" for our team links. If you find any have broken, the working version should be here.

<aside> ☝ I recommend creating a Rootski bookmarks folder in your browser and bookmarking these.

</aside>

Untitled

Notes about the team calendars:

Calendar - Rootski Availability (Loose) - You'll need to request access. List your typical availability here. This isn't a guarantee of when you can work, it's more to give everyone else a rough idea when they can reach out to meet with you. If you want to work with someone, check this calendar, and reach out to them to plan a time. If you set a meeting, put it on the next calendar.
Calendar - Rootski Meetings - If you've actually scheduled a meeting with someone, please put it on this calendar. That helps us know when people are committed to work a certain time. It also helps us see who is being active, included, ignored, etc.

Mission of "The Rootski Project"

The mission of "The Rootski Project" AKA opening up Rootski.io development to a small, closed community of developers is to:

Make Rootski.io development faster and more fun
Offer contributors personal coaching and real-world experience that are hard to simulate in a personal project. The idea is that it's hard to learn production-grade skills without building production-grade software with production-level best practices.

Depending on how much you want to lean into the project, you could do work equivalent to the role "senior" developer in a typical software company. The tools and development practices used in Rootski, can definitely bring you past the level of "junior developer" or "intern" in several software-related roles.