Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: <F86AC6A6-8B31-44AC-B0C6-9AE80749A632@programmazione.it>
References: 
 <CAJNb-9q+34-UwLBv24mJS6xN-n7czZ_mFp4Z7KpaouOXW1FNrg@mail.gmail.com>
	<D4B09FF1-64F5-440B-BC1E-36A2282B9AAC@programmazione.it>
	<529A19BF.1060209@lymegreen.co.uk>
	<2B31B8CB-2E3E-4AAD-A4C8-93C614A109F5@programmazione.it>
	<CAHdjipLOr3p_Nj3MD21bP8VCMbrt8mHvgeGa4fGi4eYdK6a9GA@mail.gmail.com>
	<6364DA60-4B97-41CA-ACB0-29F3D7BAC4D5@programmazione.it>
	<CAJNb-9r==44m1CGy3iSwxcrOvq+_YD_UZ4rGzyKtPWEx442SoQ@mail.gmail.com>
	<F86AC6A6-8B31-44AC-B0C6-9AE80749A632@programmazione.it>
Date: Sat, 30 Nov 2013 16:20:21 -0800
Message-ID: 
 <CAFUSCh8fJJLePaNMfM5QhxHd-ND-f9-F9eZuY1VcMu6EZQqq1g@mail.gmail.com>
Subject: Re: [discuss] couchapp.org down, couchapp.org spammed
From: Russell Branca <chewbranca@apache.org>
To: dev@couchdb.apache.org
Content-Type: multipart/alternative; boundary=089e0158a92e6671d504ec6e07d2

--089e0158a92e6671d504ec6e07d2
Content-Type: text/plain; charset=ISO-8859-1

In its current form, couchapp.org is a relic that has been mostly abandoned
and is not maintainable by the community. I strongly feel we should move
the couchapp documentation into official documentation. I see two relevant
points of interest in this discussion. First is the notion of couchapps as
the self contained application platform that utilizes show/list functions,
and whether these should be included in CouchDB. I don't think this is the
important issue at hand.

The bigger issue is that the defacto method of defining design documents is
to use one of the many "couchapp" tools, and the only place this is
documented as a whole is couchapp.org. This is a disservice to the
community, and one that needs to be resolved. This is a constant source of
confusion to new users who quickly realize the futility of defining design
docs in the browser, and get lost when told "just use a couchapp", and then
they inevitably end up clicking on the top google result for "couchapp",
couchapp.org. We need to have this properly documented in the official
documentation so that the process is fully defined for new users.

A couple of options for approach would be to formalize the folder
definition of a couchapp and list tools known to be compatible, or to
officially bless a tool like Erica. While I do want to see Fauxton provide
powerful editors for all the different function types, I don't think this
is sufficient as people typically want to keep their design docs raw code
under SCM. Whatever approach is taken, I think the number one priority here
is ensuring proper documentation explaining to users best practices for
defining and maintaining design docs.


-Russell


On Sat, Nov 30, 2013 at 2:57 PM, Filippo Fadda <
filippo.fadda@programmazione.it> wrote:

> List and show are not stored procedure. We already discussed that Benoit.
>
> http://wiki.apache.org/couchdb/Formatting_with_Show_and_List
>
> From the documentation: "Show and list functions are side effect free and
> idempotent. They can not make additional HTTP requests against CouchDB.
> Their purpose is to render JSON documents in other formats."
>
> Apples are not pears. I'm not buying it, stop selling list and show like
> stored proc. A stored procedure, in general, is not side effect free or
> idempotent.
>
> > If you just want a database then any KV is enough for your purpose. If
> now
> > you want a DBMS which at least I want, then you probably want a way to
> > store procedures and such to adapt the query language to your needs.
> Guess,
> > what is the purpose of lists and shows?
>
> Not in the way they are. To me, actually list and show are useless. I'm
> sorry, this is what I think. Can we just move on?
>
> -Filippo

--089e0158a92e6671d504ec6e07d2--