Proposed QIIME2 Roadmap

That means that if I wanted to run something like a batch job (5
commands executed serially), this would require me to create a q2 script
that needs to be processed by the interactive q2 shell and then
gets executed? That seems like re-inventing the wheel, something like what
the Mothur CLI does.

In hope to reduce the volume of e-mails in everyone's inbox, let's have
this conversation over a call.


On (Sep-23-14|15:08), Evan Bolyen wrote:
> > +finalized and everything is
> > +subject to change.** Once we reach agreement on the project's direction and
> > +vision, we will provide additional documents with further details
> > +(e.g., requirements and design documents).
> > +
> > +The roadmap is meant to provide a high-level view of the QIIME2. **It does not
> > +contain specific implementation details.** For example, we may mention the use
> > +of a database, but we're not yet defining the database schema or assuming use
> > +of a particular database implementation (e.g., PostgreSQL).
> > +
> > +This document was originally prepared based on conversations between
> > +@gregcaporaso, @ebolyen, and @jairideout.
> > +
> > +## Aspects of QIIME2
> > +
> > +### Client-Server Architecture
> 
> You have the idea correct.
> 
> One of our explicit goals is to support everything from a laptop to a cluster. This means progressive enhancement. For the average user, it conceptually isn't much different from an IPython notebook, where you type `ipython notebook`. Instead you might type `qiime start`, it could launch the server and the web-browser pointed at that server and the server will just use something like a SQLLite database at a path.
> 
> In the context of a cluster you could have the qiime-server running as an explicit service (like `service qiime start`) which users log into using their cluster credentials. The sysadmin can take responsibility for using a different database, managing plugins, ports, etc.
> 
> Here's a diagram representing the idea maybe a little better:
> https://drive.google.com/file/d/0B_qySw7nb-DKOVU0NFlNRHZvTWc/edit?usp=sharing
> 
> In that diagram, each component can exist on it's own host, or they can all exist on the same host (like a laptop). 
> 
> But definitely the goal is for this to be as simple as possible and to work out-of-the-box.
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/biocore/metoo/pull/4/files#r17942882