Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of kxepal@gmail.com designates
 74.125.83.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGt9U8gsAAXr+th1wFskTb+PSHEYMD+BnPkb3UtZTpr6GgUX8g@mail.gmail.com>
References: <054053281C1E41E9955761009CA159FF@cloudant.com>
	<C4A1A200-C7CE-498D-91CB-C84ED7405EE2@redcometlabs.com>
	<CAKmKYaBjBm1GYbCQacniMQhq0xUskojS_tTfzyc+DLNauSFhBw@mail.gmail.com>
	<D45D1C08-77F7-4BC7-9EB3-6DFD628D5A22@redcometlabs.com>
	<CAKmKYaAS=EDonCiv8eN6TEyRNu1kw8-oMPQLJiD8dA12fD2iRw@mail.gmail.com>
	<CAL-h1aQ9EaBJ=23wcabhGKZFbCwsJU8GxF_oB4NumD3jCcrEnQ@mail.gmail.com>
	<28FFE3619CC347D594B36B67A288B274@cloudant.com>
	<CAGt9U8hiFUnQGBsYFRxg32=p2_n81Jhd8e6Cc=NYJx3p0hifPQ@mail.gmail.com>
	<CAL-h1aTEXESv9Ga4vA5zFYDqh8RXH3mJbmWz5tooqQL--HemWw@mail.gmail.com>
	<CAAL6JQifXe-Juudqhpuh_xWofXnVnX9gtUfbp5g3ErWD3j-CRA@mail.gmail.com>
	<CAGt9U8gsAAXr+th1wFskTb+PSHEYMD+BnPkb3UtZTpr6GgUX8g@mail.gmail.com>
Date: Thu, 1 Nov 2012 15:37:08 +0300
Message-ID: 
 <CAHdjipLVRg+j5MxVSBqx32ui9HBCU7gDMJYYSzpKBNqgUh2T+w@mail.gmail.com>
Subject: Re: Futon.Next
From: Alexander Shorin <kxepal@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8

On Thu, Nov 1, 2012 at 4:31 PM, Octavian Damiean <mainerror@gmail.com> wrote:
> I'd propose a Futon.Next IRC meeting with all the people that care about
> the topic. There we could gather a list of requirements, ideas and actually
> discuss how we want to proceed.
>

+1 for special meeting about Futon.Next.

Some of requirements was defined at github issues:

https://github.com/Futon/Futon.Next/issues

But they needs in well discussion and explanation to make sure that
everyone understand them in same way.

--
,,,^..^,,,


On Thu, Nov 1, 2012 at 4:31 PM, Octavian Damiean <mainerror@gmail.com> wrote:
> I'd propose a Futon.Next IRC meeting with all the people that care about
> the topic. There we could gather a list of requirements, ideas and actually
> discuss how we want to proceed.
>
> Discussing, tracking ideas, requirements and suggestions of such a topic
> solely on the ML get a little tedious in my opinion.
>
> What are the opinions on a Futon.Next IRC meeting?
>
> On Mon, Oct 29, 2012 at 7:30 AM, Randall Leeds <randall.leeds@gmail.com>wrote:
>
>> On Thu, Oct 25, 2012 at 10:35 AM, Ryan Ramage <ryan.ramage@gmail.com>
>> wrote:
>> >>> I'd assume that in a release we'd compile things down into the
>> share/www
>> >>> directory and serve out of there (as we do with the current futon, and
>> will
>> >>> do with the docs), so what we need IMHO is a build tool not a couchapp
>> push
>> >>> tool.
>> >>>
>> >>
>> >> If Futon.Next should become a proper CouchApp as discussed then we
>> >> certainly need a CouchApp push tool.
>> >
>> > One requirement out of Cloudant is the ability to turn things on and
>> > off. This will require persistance. Have a db to persistant settings
>> > would be a feature of using a couchapp.
>>
>> That's not how I read this requirement. My understanding was that
>> Cloudant wanted the ability to turn off features at build
>> configuration time. It would affect which js files get pushed. That
>> means it would either effect which files grunt.js processes, or it
>> would affect what files get listed in some couchapp manifest.
>>
>> If runtime configuration is necessary, that should be articulated more
>> clearly as a requirement, but I worry that this starts to balloon into
>> more of a CMS agree with Alexander that it starts to look like we've
>> gone too far.
>>