karlbennett / coma Goto Github PK

Before we can start we need to know what we can actually do with the sources we wish support. Can we stream? Or will we have to use a browser to remotely drive the sources UI?

Acceptance Criteria

1. Find out how songs can be accessed remotely* from the following sources
   • Grooveshark
   • Google Music
   • Spotify
   • Dropbox
   • TorrentSync

* I say remotely because I'd like coma to be able access all the sources without having to install their respective clients.

The scope of the first iteration of coma should be decided before we begin.

Acceptance Criteria

1. All contributors agreeing on the first set of core features coma should provide.

Related Tickets
#4 Check streaming access of different sources

I've created an initial draft of the README.md that provides an idea of the behaviour first coma minimum viable product. I would very much appreciate some feedback on the proposed commands as well as the document in general.

Acceptance Criteria

1. Sign off of the README.md from all coma contributers.
2. Any proposed and agreed upon improvements applied.

coma should have a simple, maintainable, and understandable structure. Because of my web development background I would naturally like it implemented as a client server application. Where the command line is used to interact with the service through some form of messaging protocol. REST is the first thing that comes to mind because it is simple, well understood, has the added advantage of allowing the easy implementation of other kinds of local and remote interfaces.

Acceptance Criteria

1. A high level architecture is agreed upon by all contributers.