Create Functionality Roadmap + Plans

[13rac1]

We should have a discussion about long term plans for Roundware, then create a roadmap to v1.0.

Here is my initial thoughts:

• 0.3 - APIv2 - Fully RESTful API matching APIv1 plus basic User Accounts
• 0.4.- Ansible or SaltStack or ??? for configuration management. #183
• 0.5 - Complete unit test and browser (Selenium) test coverage.
• 1.0 - Full release

More items:

• Listen Map
• Device based audio generation (I think this may just need APIv2)
• Send asset tags in stream metadata via metadata update or taginject. (required by Feb 2015, #178)
• Support additional installation targets/stacks.
• All the other existing issues in the list (Gstreamer1.0 to not use our old libgstshout2.so... hopefully)

Should we discuss optimizing/changing the support stack? I don't see a reason to change the Linux distribution, but the web server and the database could be changed. I'm not sure the cost/benefit is worth it at this point though.

• Webserver - Apache, could be changed to nginx or gunicorn or ??? Need to determine the benefits, if any.
• Database - MySQL, could be changed to MariaDB or PostGreSQL or ??? Need to determine the benefits, if any. See #184

[hburgund]

I would like to see a significant upgrade to the Dashboard at some point before v1.0. This is related to the Listen Map mention above and will be vastly facilitated by api/2 and the more full integration of DRF. Things like graphs, charts, tables and displays of the basic data of a RW installation are hugely important to organizations that install RW and having it all in a nice flexible dashboard is a huge value add.

I think the current bootstrap-based dashboard http://localhost:8888/dashboard/ is a reasonable and flexible structure and I've included many placeholders for the sorts of things I think would be useful, but there are many more that can be added, of course.

Related issues: #57, #60