Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of mainerror@gmail.com
 designates 209.85.217.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPaJBx7ak07bEnOSUHknBP21yZVnBwpKEW_hHn96AEB0Qf0A2w@mail.gmail.com>
References: 
 <CAFUSCh-en-K44NBmy=WYVJGkwgkA_Nepb6zcC_V5_2_fSA024Q@mail.gmail.com>
	<CAPaJBx7ak07bEnOSUHknBP21yZVnBwpKEW_hHn96AEB0Qf0A2w@mail.gmail.com>
Date: Sat, 3 Nov 2012 17:44:02 +0100
Message-ID: 
 <CAGt9U8hFpTCrK=X=C6dUBqs1rYFM70NpJb=a3Lo1Eav686cmog@mail.gmail.com>
Subject: Re: Futon.Next Proof of Concept
From: Octavian Damiean <mainerror@gmail.com>
To: dev@couchdb.apache.org
Content-Type: multipart/alternative; boundary=e0cb4efe2f12b24c2504cd99f5e7

--e0cb4efe2f12b24c2504cd99f5e7
Content-Type: text/plain; charset=UTF-8

Compiled artifact in this case means, compiled LESS files to CSS (minified
or not), JavaScript (minified or not) and HTML. So no bytecode, it would
still be readable (except minified JS and CSS are a bit hard to read bit
still plaintext).

Cheers,
Octavian

On Sat, Nov 3, 2012 at 5:37 PM, Noah Slater <nslater@apache.org> wrote:
>
> Also, Bob sed:
>
> If the choice is node as a build dependency versus checking in compiled
> > artifacts, I choose node.
>
>
> Perhaps someone can clarify for me what a compiled artefact is? We can't
> ship compiled code. We can ship compressed or package code. But if we're
> compiling code into bytecode or machine code, that is a complete no-no in
> both our repos and our releases.
>
> --
> NS
>

--e0cb4efe2f12b24c2504cd99f5e7--