Thanks for the info on the separate repos. I assumed that since we already have Couch scattered across a large # of repos.
It's all about what sort of build instructions we put in the "main" CouchDB distribution. As long as the main build script doesn't auto-forcibly-invoke building of all of these other tools, I'm fine. Assuming the above is true I'm +1. -Joan ----- Original Message ----- > From: "Jan Lehnardt" <j...@apache.org> > To: dev@couchdb.apache.org, "Joan Touzet" <woh...@apache.org> > Sent: Wednesday, June 3, 2015 2:06:41 PM > Subject: Re: [DISCUSSION] nmo to the ASF > > > > On 03 Jun 2015, at 19:35, Joan Touzet <woh...@apache.org> wrote: > > > > Is the intent with all of these contributions to ship them in > > a contrib/ tree? We're starting to get cluttered with tools and > > languages, and with couchdb-python also in the wings as potential > > contribution, I am concerned about the build process for the > > tool mandating npm, python, etc. > > I see them in different repos with their own build/release cycles > that aren’t bound to core CouchDB. > > The CouchDB distribution then can choose to bundle whatever latest > version of whatever tool when its time to release comes up. I see > it making more sense for nmo (I think of it as Fauxton-CLI) and less > for couchdb-python and nano, but this is all open for debate, my > main point here is that these are not bound to an Apache CouchDB > Release necessarily. > > Does this address your concerns? > > > > -Joan > > > > ----- Original Message ----- > >> From: "Jan Lehnardt" <j...@apache.org> > >> To: dev@couchdb.apache.org > >> Sent: Wednesday, June 3, 2015 9:32:00 AM > >> Subject: Re: [DISCUSSION] nmo to the ASF > >> > >> > >>> On 03 Jun 2015, at 15:24, Alexander Shorin <kxe...@gmail.com> > >>> wrote: > >>> > >>> On Wed, Jun 3, 2015 at 4:12 PM, Jan Lehnardt <j...@apache.org> > >>> wrote: > >>>>> On 03 Jun 2015, at 15:09, Alexander Shorin <kxe...@gmail.com> > >>>>> wrote: > >>>>> > >>>>> On Wed, Jun 3, 2015 at 4:01 PM, Jan Lehnardt <j...@apache.org> > >>>>> wrote: > >>>>>>> On 03 Jun 2015, at 14:43, Alexander Shorin <kxe...@gmail.com> > >>>>>>> wrote: > >>>>>>> > >>>>>>> On Wed, Jun 3, 2015 at 1:40 PM, Jan Lehnardt <j...@apache.org> > >>>>>>> wrote: > >>>>>>>>> On 03 Jun 2015, at 04:38, Alexander Shorin > >>>>>>>>> <kxe...@gmail.com> > >>>>>>>>> wrote: > >>>>>>>>> > >>>>>>>>> Hi Robert, > >>>>>>>>> > >>>>>>>>> What's the rationale of your donation? > >>>>>>>> > >>>>>>>> The benefit then is that we can ship it with CouchDB :) > >>>>>>>> > >>>>>>>> I’m +1000, I’ve wanted something like this forever. > >>>>>>> > >>>>>>> I'm not sure that we'll have consensus on shipping nodejs > >>>>>>> tools, > >>>>>>> especially with current state of nodejs. > >>>>>> > >>>>>> The current state of Node.js is fine. > >>>>> > >>>>> I wouldn't say that: node.js is dead, io.js develops quite > >>>>> fast, > >>>>> but > >>>>> they provides broken releases for Windows and Linux quite often > >>>>> (2.1.0 > >>>>> was broken for instance for me and I had to wait for 2.2.1). > >>>> > >>>> Node.js is not dead. Please stop posting FUD. > >>>> > >>>> The io.js and Node.js projects are going to be merged in the > >>>> future, work > >>>> is currently ongoing. Node.js has stable releases all around, > >>>> there is no > >>>> technical reason, not to bet on it. There is a significant > >>>> community and > >>>> industry around Node.js/io.js. > >>> > >>> I don't watch the TV. Good news then (: > >> > >> Hahahah :D > >> > >> Best > >> Jan > >> -- > >> > >> > > -- > Professional Support for Apache CouchDB: > http://www.neighbourhood.ie/couchdb-support/ > >
