Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of simon@cloudant.com designates
 209.85.215.180 as permitted sender)
Date: Thu, 1 Nov 2012 12:37:56 +0000
From: Simon Metson <simon@cloudant.com>
To: dev@couchdb.apache.org
Message-ID: <7060B520E54744EEA3300DD7842C26D8@cloudant.com>
In-Reply-To: <B118C1F6-81A0-4F90-9814-A103E2860511@redcometlabs.com>
References: 
 <CAFUSCh-en-K44NBmy=WYVJGkwgkA_Nepb6zcC_V5_2_fSA024Q@mail.gmail.com>
 <CAAL6JQhBgiss45MRQGejLkuE3UQZYf1zqm5SaqZUjaN8TGVPPg@mail.gmail.com>
 <B88FB7EB44EE469F9D8633857CD1613C@cloudant.com>
 <B118C1F6-81A0-4F90-9814-A103E2860511@redcometlabs.com>
Subject: Re: Futon.Next Proof of Concept
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi, 


On Thursday, 1 November 2012 at 09:56, Garren Smith wrote:

> Could we seperate this out of Couchdb as a pure couchapp for now? Might make it easier to work on.

I think keeping it in a fork of CouchDB is good. It hopefully addresses some of Noah's concerns re visibility and will help keep us honest (e.g. stop us from diverging away from an end goal of something served out of _utils). There's nothing stopping people deploying as a couchapp out of that source tree though, once I merge in your patch :D
> Simon could you share your wireframes with everyone? 

Yes, we're working on that now (amongst other things). 
> We have an issues list here https://github.com/Futon/Futon.Next/issues Should we keep using that as our todo list for Fauxton?

Yeah, I think that's a decent place. I've been using trello recently which is another nice tool for tracking progress (orthogonal to a todo), maybe that's OTT, though. 
Cheers
Simon