+1 even if we decide that the concept shouldn't be part of the core project we should make sure that it is maintained well since it represents a community effort and w certainly don't want our community to look broken. On Nov 30, 2013 12:46 PM, "Jan Lehnardt" <[email protected]> wrote:
> > On 30 Nov 2013, at 11:34 , Dirkjan Ochtman <[email protected]> wrote: > > > On Sat, Nov 30, 2013 at 11:05 AM, Benoit Chesneau <[email protected]> > wrote: > >> If we considers the couchapps concept as a part of the couchdb project, > >> then we should: > >> > >> - either start some action > >> > >> - or find a new name and new way to document the concept > >> > >> If some of you consider that we should just ditch the couchapps concept > >> from the couchdb and make couchdb another database, then we should also > >> clarify this situation and start a real discussion about it and at the > end > >> take a decision > > > > IMO the CouchApps concept should not be a part of the CouchDB project, > > even though it is obviously related to it. Having too wide a focus > > means not having that much focus at all, and I think we should focus > > on being the cool MVCC database w/ REST API that makes things like > > CouchApps possible. > > Regardless of that, CouchApp.org should be in the hands of people that > care about it and if we can help with that, we should. > > Best > Jan > -- > > >
