Revive our first demo project

[snowmantw]

@kaichih @kumarrishav ,

I think we should focus on our originally first demo, so that we can make sure what we built is close to what we want. Maybe we should take a time to review the project in person, if @kaichih has already replicated it from the original site?

For now, I think we need to consider from test cases the first demo would have, and build it from test cases to make sure things are fully probed before we jump into the uncertain situation. Although speed is what we care about, but code legacy would prove it is the real lethal enemy as every muddy starting-fast project shows.

[kaichih]

@snowmantw , in this case, should we create a milestone called "Preparation of the first demo". What do you think? Please refer to #12.

[kumarrishav]

That's what we are doing currently : preparing our first POC/demo. Right now we are very far from it. I think
only after Milestone 1,2,3 (at least) , we will reach a workable DEMO/POC.

[kumarrishav]

I created these issue, so that we can mention all these details on our wiki. Once wiki has centralized info, we can close lots of opened issue.

[kumarrishav]

Also, i think Milestone is limited to a single repo. So, for each repository we need separate Milestone. @kaichih @snowmantw

[kumarrishav]

Or another solution can be:
we can create an issue on this repo for myself where i will list down all the issue (from various repo) links which i want to do in MileStone-1 and add this issue in MileStone -1.

How about this?

[kaichih]

That sounds good to me.
Thanks Kumar.