Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A3EA2D75F for ; Thu, 1 Nov 2012 17:06:10 +0000 (UTC) Received: (qmail 47031 invoked by uid 500); 1 Nov 2012 17:06:10 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 46997 invoked by uid 500); 1 Nov 2012 17:06:09 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 46974 invoked by uid 99); 1 Nov 2012 17:06:08 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 17:06:08 +0000 Received: from localhost (HELO mail-vc0-f180.google.com) (127.0.0.1) (smtp-auth username rnewson, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 17:06:08 +0000 Received: by mail-vc0-f180.google.com with SMTP id fl13so2773652vcb.11 for ; Thu, 01 Nov 2012 10:06:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.180.225 with SMTP id dr1mr25418273vdc.2.1351789567119; Thu, 01 Nov 2012 10:06:07 -0700 (PDT) Received: by 10.52.69.79 with HTTP; Thu, 1 Nov 2012 10:06:07 -0700 (PDT) In-Reply-To: References: <7060B520E54744EEA3300DD7842C26D8@cloudant.com> <83A56992-9BA7-4FE4-868E-D4FBE5426DF4@redcometlabs.com> Date: Thu, 1 Nov 2012 17:06:07 +0000 Message-ID: Subject: Re: Futon.Next Proof of Concept From: Robert Newson To: "dev@couchdb.apache.org" Content-Type: multipart/alternative; boundary=bcaec517a990f58fc704cd720820 --bcaec517a990f58fc704cd720820 Content-Type: text/plain; charset=ISO-8859-1 Can I get a definitive answer on whether node.js will be a build requirement? I'll add that I'm not objecting to that, I just want confirmation. On 1 November 2012 16:36, Garren Smith wrote: > > On 01 Nov 2012, at 6:17 PM, Russell Branca wrote: > > > On Thu, Nov 1, 2012 at 7:18 AM, Garren Smith > wrote: > >> > >> On 01 Nov 2012, at 2:37 PM, Simon Metson wrote: > >> > >>> 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 > >> I think it will make life a lot easier to have it in its own > repository. There is a lot of unnecessary overhead in developing a js > frontend around the couchdb code base. > >> > >>>> 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. > >> Lets use issues for now and if we need more help tracking progress we > can move to Trello. Could you or Russel say what you guys are currently > working on w.r.t Fauxton and where other developers could initially get > involved? Maybe this should all be done on the issues. > >> > >>> Cheers > >>> Simon > >>> > >> > >> Cheers > >> Garren > >> > > > > Ok we'll add some tickets to issues on the Futon.Next repo. > > > > The next thing I'm working on is expanding the plugin system and > > building a pluggable backend so that the CouchDB API module can be > > swapped out. As for other open areas, there is a lot of functionality > > that needs to get fleshed out. It would also be great if someone > > wanted to jump on things like _config and _logs. We're in the process > Great, I'm happy to get a working version of the _logs going. Can get it > done in the next couple days. But we if could get a nice list of stuff to > work on, so everyone knows how to pitch in. > > of getting the wireframes together, so for now we're just focusing on > > functionality and less on look and feel. > > > > > > -Russell > > --bcaec517a990f58fc704cd720820--