* Properly structuring UnBall's ROS package
Previously, our git repo was tracking the entire structure for compiling UnBall's ROS package, including its catkin workspace. However, each developer should have it's own catkin workspace in their computers and a symbolic link to our ROS package. This allows everyone to have only one place for compilation (even for other packages that requires catkin) and avoid weird paths, such as `software/src/unball/src/unball`.

* How to migrate:
First, create and initialize a catkin workspace somewhere, e.g. your home dir:
```
mkdir ~/catkin_ws
mkdir ~/catkin_ws/src
cd ~/catkin_ws/src
catkin_init_workspace
```

Then, create a symbolic link from our source code to your catkin workspace:
```
ln -s <path_to_unball_repo>/software ~/catkin_ws/src/unball
```

Voilà, it's done! Simply edit your files wherever you cloned our repo and compile them in `~/catkin_ws` with `catkin_make`. Remember to `source ~/catkin_ws/devel/setup.sh` requires the new path in order to work.