On Mar 18, 2013, at 23:42 , Stephen Bartell <[email protected]> wrote:
> Thanks guys for clearing that up. > > I work mostly in multi git setups, so naturally flags were going up over > this. The reasons make sense though. Just out of curiousity, what do you do to mitigate the pain? :) Jan -- > > > On Mar 18, 2013, at 3:15 PM, Russell Branca <[email protected]> wrote: > >> Hi Stephen, >> >> >> There was a fair bit of discussion behind this, and single repo ASF is the >> real blocker. Also, while Fauxton can run as a couchapp, by default it >> builds down into static files and is hosted by CouchDB the same way as >> Futon. >> >> That said, making Fauxton as easily to develop as possible for new >> contributors has been a primary concern of ours. We've gotten all >> dependencies moved into package.json, and Garren has been knocking out a >> new development server which will allow you to develop locally and not have >> to build CouchDB as a part of Fauxton development. The new process will >> basicaly be: >> >> git clone couchdb >> cd couchdb/src/fauxton >> npm install >> ./bin/dev-server >> >> And you'll be up and running. >> >> >> -Russell >> >> >> On Mon, Mar 18, 2013 at 3:06 PM, Stephen Bartell <[email protected]>wrote: >> >>> Referencing the topic [Merging the fauxton branch into master] >>> >>> Im just wondering, why can't fauxton development take place in an entirely >>> separate repo from couch. Its a couch app after all, correct? >>> >>> I think fauxton could be an example of couch's modular design. >>> >>> As I write this email, I think I've realized a blocker to this idea. And >>> that is that Couch really lives in a single ASF repo. Nonetheless, I want >>> to throw this out there. >>> >>> Best, >>> Stephen Bartell >>> >>> >>> >>> >>> >>> >>> >
