Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jonbcampos@gmail.com
 designates 209.85.214.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <B924CD80-E14F-4975-A71C-979906CB3017@classsoftware.com>
References: <B924CD80-E14F-4975-A71C-979906CB3017@classsoftware.com>
From: Jonathan Campos <jonbcampos@gmail.com>
Date: Mon, 30 Jul 2012 21:42:17 -0500
Message-ID: 
 <CAAd0WrZ7CdQRnRa1RWzy-PRPwZtp_srnw8OhsE4SimGUmdpzbA@mail.gmail.com>
Subject: Re: What namespace should new components go in?
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=e89a8ff2561aa3132104c61721f1

--e89a8ff2561aa3132104c61721f1
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jul 30, 2012 at 9:06 PM, Justin Mclean <justin@classsoftware.com>wrote:

> 2. Place components under a single new namespace called
> http://flex.apache.org/ns.
> Advantages: All new components have a new ant target, new swc and
> namespace so easy to see what is new in the SDK and if a project is using
> Apache Flex. Work already done in patches branch. Namespace is valid URL
> and was suggested by a mentor.
> Disadvantages: It's a new namespace.
>

I like this idea but maybe an "experimental" namespace and then the
official "apache" namespace or spark, etc.

-- 
Jonathan Campos

--e89a8ff2561aa3132104c61721f1--