We are using several awesome tools to build Rootski. Getting past the initial learning curve of these tools will level up your development speed by many times.
Please go through the learning resources linked to each of these tools to get up to speed about what they are for and why we use them.
It's okay to still be learning. The team is very friendly and will always answer your questions. But please respect your teammates time by training yourself on each of these points before pair programming. We're happy to clarify, but there is already so much to explain, we shouldn't be explaining things you can easily look up yourself.
<aside>
📌 As you learn these tools, please be active on the #onboarding-and-training Slack channel. While we shouldn't be teaching you these tools from scratch, we are more than happy to clarify particular points of confusion and find more resources. You can also share the parts you think are the coolest! This will help others who are going through / have gone through the same process.
</aside>
🔥 = Prerequisite for any technical collaboration
⭐️ = Important, but can wait until needed on a per-project bases
This is quite a process. You can achieve it by running make run after cloning Rootski. But you may run into barriers. Learning and setting up the prioritized tools below will make this possible for you.
Refer to the [onboard.sh](<http://onboard.sh>) script for help installing many of these things, but don't run it because it is currently broken and may mess up your system (sorry Yash 🤕).
bash (everyone)zsh; everyone)I'm marking this as high priority because it is fairly easy and will help you move faster in the terminal.