This page is not complete.
This page should be a solid guide to starting up a new dev environment for Kuma. For now, it will at least link to pages you need to know about.
Step one: Set up the build environment
The first thing you need to do is to set up the build environment. This involves installing some tools, then forking the Kuma repository on Github. After that, there are some scripts to run and files to set up. The guide has been built up to really lead you through the process quite neatly.
Step two: Find something to do
There's lots of work to do on Kuma! For starters, though, you should look through our good first bugs list. These are bugs that have been triaged as being relatively easy to fix, and each one has an experienced Kuma developer assigned to mentor anyone that wants to try to resolve the issue.
Sometimes things get messed up and the Kuma test setup on your computer stops working correctly. Here we offer some suggestions for things to do to try to get it working again.
The first thing to try is to destroy and rebuild your Kuma virtual machine. Open a terminal, move into the
kuma project directory, and issue the following command:
vagrant destroy && vagrant provision
If you want to retain the database you already have, be sure to make a backup and restore it after reprovisioning.
Redownload the VM image
If you worry that your VM image is bad or out of date, you can force vagrant to download a new one by issuing the following command:
vagrant box remove kuma-ubuntu