Using github milestones for task tracking

[Tim Hockin]

Hi everyone.  The excitement around this project is awesome, thank you all.

We have a LOT of work to do, and I think we need to be really aggressive on timeframes.   Going through the issues this weekend, it's clear that some are more important than others.  I added a bunch of labels, but I think we should consider milestones.

Here's my proposal:

Milestone "v0.1.0" -- aka "alpha".  This covers all the work we need to do which is architecturally critical.  We have to prove to ourselves that we can achieve the goals we have set out to achieve.  There are several major technical decisions we need to make, which will be hard to un-wind, so we should focus on those first.  This milestone is almost exclusively about proving viability.

Anything that isn't related to that should be pushed out beyond this milestone.  That doesn't mean work won't get done on other topics, as needed, but we should focus on these major issues.

Objections?

Tim