Return-Path: X-Original-To: apmail-couchdb-marketing-archive@minotaur.apache.org Delivered-To: apmail-couchdb-marketing-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 74D1017931 for ; Sun, 20 Sep 2015 01:27:06 +0000 (UTC) Received: (qmail 27144 invoked by uid 500); 20 Sep 2015 01:27:06 -0000 Delivered-To: apmail-couchdb-marketing-archive@couchdb.apache.org Received: (qmail 27101 invoked by uid 500); 20 Sep 2015 01:27:06 -0000 Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: marketing@couchdb.apache.org Delivered-To: mailing list marketing@couchdb.apache.org Received: (qmail 27089 invoked by uid 99); 20 Sep 2015 01:27:06 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Sep 2015 01:27:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 9A7381A2712 for ; Sun, 20 Sep 2015 01:27:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=6.31 tests=[SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id JKuWv-OU2FOu for ; Sun, 20 Sep 2015 01:26:58 +0000 (UTC) Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTP id 95C0B207EA for ; Sun, 20 Sep 2015 01:26:57 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 57141CC386 for ; Sat, 19 Sep 2015 21:26:56 -0400 (EDT) X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id oJmTRirHmVoA for ; Sat, 19 Sep 2015 21:26:53 -0400 (EDT) Received: from new-host.home (pool-96-230-114-112.bstnma.fios.verizon.net [96.230.114.112]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 510DDCC385 for ; Sat, 19 Sep 2015 21:26:53 -0400 (EDT) Subject: The Future of Couch: [Was: The future of couchapps] To: marketing@couchdb.apache.org References: <26483399.1013.1442700738794.JavaMail.Joan@RITA> From: Miles Fidelman Message-ID: <55FE0B5C.2090709@meetinghouse.net> Date: Sat, 19 Sep 2015 21:26:52 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:38.0) Gecko/20100101 Firefox/38.0 SeaMonkey/2.35 MIME-Version: 1.0 In-Reply-To: <26483399.1013.1442700738794.JavaMail.Joan@RITA> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit I just spent a little time comparing "Cloudant Local" with CouchDB - and in addition to ongoing support for CouchApps, it seems like Cloudant Local supports geospatial functions as well. Which leads me to wonder two things: - Whatever happened to geoCouch? - What's the general direction of the CouchDB ecosystem. Are we seeing Cloudant diverge from Couch, with IBM-supported features not making their way back into the open source version of Couch? Miles Fidelman Joan Touzet wrote: > I'll concur with Alex here. My survey of the PMC members so far has > resulted in 100% of us in agreement with Jan's comments. > > This is not a power play, it is a logical, reasoned decision with many > factors that play a part -- not the least of which is that there are so > many great web frameworks out there that do such a better job than we do > with CouchApps. We'd need a massive effort to catch up with them, and a > significant number of developers just to keep pace. Right now, there's > no one working on CouchApps period, as has been repeatedly stated on the > list. > > If you are willing to put in the time to develop the Erlang, JavaScript > and possibly C to build the new functionality, and are able to sustain > development on that over the course of the years it would take to match > e.g. Python or Node.JS's community level for web apps...well, let's just > say that I look forward to your GitHub pull requests. :) > > Best regards, > Joan > > > > ----- Original Message ----- >> From: "Alexander Shorin" >> To: marketing@couchdb.apache.org >> Sent: Saturday, September 19, 2015 1:45:52 PM >> Subject: Re: The future of couchapps >> >> Hi John, >> >> The future of CouchApps is trivial and was already discussed on this >> ML[1]: this feature stalled over 4 years already, it has quite enough >> issues and limitations, it lacks maintainer. If something of these >> won't change in nearest future, CouchApps are doomed. And all >> solutions lies though the hero(es) who will maintain and develop this >> feature. >> >> The question here is not only about to keep existed code works. It's >> also about vision of what CouchApps are, what they have to be, how to >> evolve them and make really great and useful feature for CouchDB >> users >> and not only. >> >> Currently, there is no active leader of CouchApp feature in CouchDB >> team, so this place is vacant and we are welcome everyone who would >> like to take this duty on his/her shoulders. Otherwise CouchApps >> will >> continue to be feature of secondary type, sort of accidental side >> effect from technical decisions of good past days. No need to say >> what >> such state means. They may simply not survive next major release. >> >> [1]: Follow this thread: >> http://mail-archives.apache.org/mod_mbox/couchdb-marketing/201505.mbox/%3CCAPMhwa5R6CdeQP-m_FHfqYsJ4NDwLYiePuwrsi2bRfzifncRpw%40mail.gmail.com%3E >> - it's long, but has all the same answers. >> >> -- >> ,,,^..^,,, >> >> >> On Sat, Sep 19, 2015 at 8:16 PM, Johs Ensby wrote: >>> Hi all -- both couchapp lovers and skeptics, >>> >>> I want to start a new thread based on the below conversation >>> between Jan and Giovanni at the end of the thread [VOTE] >>> WHY/HOW/WHAT. >>> >>> I am in the group of stakeholders that have a business that rely on >>> CouchDB. And I use couchApps hosted on Cloudant. I would like to >>> see the community grow, not split again and there seems to be a >>> tone developing that I am sorry if I have been a contributor to. >>> Rather than having wide-reaching discussion about dream features >>> of future couchapps, I will try to stay on the subject of a future >>> for couchapps or not. >>> >>> The "watch me" from Jan below is very disturbing to me. >>> I would appreciate seeing some comments from PMC members on this. >>> >>> Johs >>> >>> >>>> On 18. sep. 2015, at 13.52, Jan Lehnardt wrote: >>>> >>>>> - you don't know if tomorrow some erlang skilled couchapp lover >>>>> won't get >>>>> in and start working on the app part (to say the truth some of >>>>> them were >>>>> already active in the past, but they chose to left just because >>>>> of >>>>> this/yours direction) >>>> In my last email I specifically suggested for such a person to >>>> step up and I’d welcome them wholeheartedly. >>>> >>>> >>>>> - you can't remove something that ALREADY exists which A LOT of >>>>> people >>>>> like, use and have businesses on top, just because you and a few >>>>> people >>>>> don't like it >>>> Watch me. -- In theory, there is no difference between theory and practice. In practice, there is. .... Yogi Berra