Prepare for release

@bohlender @dmiklic 

We want to base our own software on the `sicks300` driver. As we want to deploy our software via Ubuntu ROS packages, we'd need this to be released to the ROS universe or at least host it on our own ROS Ubuntu repository (with the former clearly being the preferred solution). 

I have tested releasing it to our own repository (http://lcas.lincoln.ac.uk/repos/building/) from our fork (https://github.com/strands-project/sicks300) which has a few release tags in that I omitted from this pull request and it works nicely (tested for hydro and indigo). But we would rather want to commit this back upstream including our own additions (see https://github.com/bohlender/sicks300/pull/3) rather than having a diverging fork. 

As I said, I'm happy to actually make the release (as I have some experience with that), but want to pass this by you first. 

This PR is about some small changes I introduced to make it also compile with ROS indigo and also introducing myself as a maintainer. Feel free to ignore the latter ;-)

Alternatively, we as the [STRANDS project](http://strands-project.eu) can also take over sole maintenance duties for this repo if you want us to. In any case, we'd love to get this released ASAP so we can continue with releasing the rest of our software.

__In case you want to release yourself:__

In order to release the package after this pull request and also see https://github.com/bohlender/sicks300/pull/3 are being merged, you would have to follow [these instructions](http://wiki.ros.org/bloom/Tutorials/FirstTimeRelease), but as I said, I'm happy to do it for you.