Chris Smith

That's a good question... I think @IanTheEngineer and I talked about it a while ago and ended up not including it since it's not exactly a `ROS` package as you...

Ah interesting. Just adding docs seems useful - how does it auto-generate docs/tutorials? Presumably there'd need to be some work to make that happen. If we wanted to use ROS...

Cool. I'm not familiar with using `doxygen` or `sphinx` for javascript. We'd have to extend them in some way or find some open source code to do so? Assuming that's...

[sphinx-js 2.0](https://pypi.python.org/pypi/sphinx-js) looks like it will work with our existing JS docs actually - they likely need to be updated and filled out more but it won't require rewriting everything.

Should be - setting up the environment and actually running the tests there has been on my list for a while...

We do automatically run tests against pull requests/commits through travis... It'd be good if we tested against future versions of Ubuntu - I think we need docker for this because...

I think 14.04, 16.04, and 18.04 would be good - support for 14.04 will probably drop ~soon (I think OSRF is dropping 14.04/Indigo next April) but we should continue supporting...

I think we'll need to use different ROS versions for xenial and bionic too (probably kinetic and melodic respectively)

I'm not immediately sure why `ros-melodic-catkin` can't be found... I'm a little surprised the 16.04 and 18.04 builds start trying to install packages though. As far as I'm aware, travis...

I think I'd at least like to hear what ROS thinks. Doing this would break the api and make it harder for new and current users.