> To get this rolling, we need to understand what we do and why we do it.
Considered couchapps new amazing features( http://markmail.org/message/poxvkumqqi4fugeo and http://markmail.org/message/rfbczt46ytlldjtj) and ermouth proposal for a platform-indipendent and browser-only couchapp development environment( http://markmail.org/message/rckxmbx3tl7nags5), Couchapps can really have big impact on CouchDB adoption-rate... so I think they are a big plus for the project. Furthermore, as CouchDB Hosting provider, I can say Couchapps are extensively used by users.. so the story could be instead to give them more visibility, by advocating them and clarifying what they can and cannot do.. with facts, tutorials, examples and benchmarks. 2015-05-06 18:24 GMT+02:00 Jan Lehnardt <[email protected]>: > > > On 06 May 2015, at 18:18, Alexander Shorin <[email protected]> wrote: > > > > On Wed, May 6, 2015 at 6:49 PM, Giovanni Lenzi <[email protected]> > wrote: > >> What you all think about it? > > > > I think we need just clarify what CouchApp is, define it's show cases > > and area where they are works perfectly. > > First step is to back couchapp.org online (almost done). Then, just > > fill it the right content. That will solve any confusions. > > Before we fix anything, we need to understand how to fix it. To understand > how to fix it we need to understand what we do. To understand what we do, > we need to understand why we do it. — Hence, we first need to find a “The > Why of CouchDB” story that reflects our intentions before any of the other > decisions can happen. That’s what my original message is about. > > > > I'm -1 for removal CouchApps as a since it's not possible as CouchApps > > are not a some entity, but a way of organizing design documents in > > order to solve some specific problem. > > The problem is, as outlined in my emails on marketing@ that I linked > earlier > that “CouchApp” means at least eight different things to different groups > of > people. That is terribly confusing and makes people new to CouchDB leave us > in spades because it is just too complicated. > > I never meant for the actual technical features in CouchDB to be removed > and > I never said so. > > > We just need to find a sweet spot, a right vector for their future since > as > > for now I feel CouchApp as a technology is just lost in space. > > Exactly, and its harming CouchDB. > > To get this rolling, we need to understand what we do and why we do it. > Then > we can decide if and how “CouchApp” in whatever form fits into this. > > Best > Jan > -- > >
