Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: Futon.Next
From: Jan Lehnardt <jan@apache.org>
In-Reply-To: 
 <CAGt9U8gsAAXr+th1wFskTb+PSHEYMD+BnPkb3UtZTpr6GgUX8g@mail.gmail.com>
Date: Thu, 1 Nov 2012 13:37:18 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <581BEA9D-49E9-41A8-BE4D-C53DA6227EF4@apache.org>
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>
To: dev@couchdb.apache.org


On Nov 1, 2012, at 13:31 , 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.
>=20
> Discussing, tracking ideas, requirements and suggestions of such a =
topic
> solely on the ML get a little tedious in my opinion.

Aren=92t these tracked at =
https://github.com/Futon/Futon.Next/issues?state=3Dopen
for now? I=92d suggest that IRC is as bad as a mailing list to manage =
these
things :)


> What are the opinions on a Futon.Next IRC meeting?

I think we have a good foundation to move on with. I=92m not sure how a
meeting would help here. I=92d rather not distract the people who work
on this :)

Cheers
Jan
--=20


>=20
> On Mon, Oct 29, 2012 at 7:30 AM, Randall Leeds =
<randall.leeds@gmail.com>wrote:
>=20
>> 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.
>>>>>=20
>>>>=20
>>>> If Futon.Next should become a proper CouchApp as discussed then we
>>>> certainly need a CouchApp push tool.
>>>=20
>>> 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.
>>=20
>> 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.
>>=20
>> 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.
>>=20