Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
From: "Rui Silva" <flex@rduartes.net>
To: <flex-dev@incubator.apache.org>
Subject: Too many open subjects
Date: Fri, 6 Jan 2012 03:13:52 -0800
Reply-To: flex@rduartes.net
Message-ID: <70311c7d$36b6d930$48b2f1fc$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

First of all, WOW! This list is a living proof of Flex's relevance in 
today's web development scene! And the REAL community is still out there 
waiting to jump in as soon as we start showing something going out the 
door. Brace yourself, because this will be a roller-coaster ride! I'm 
absolutely loving every single topic we are discussing and we're touching 
in so many, so important things that will have major impacts on how this 
project moves forward.

But, that's also the thing that worries me. We're leaving too many things 
open without trying get to some sort of closure (which in Apache terms, I'd 
say consists of a voting process). I understand that this is somewhat the 
result of this initial boom of energy resulting from the creation of a new 
project and that we want to get our main worries right in from the start. I 
also understand that this will inevitably start to tone down as the project 
progresses. There are, however, some subjects that I'd like to close down 
as soon as possible, like the Subversion branching and naming strategies, 
for instance. Should we have a vote on these?

Sorry if I'm sounding like I'm spoiling the fun, but I've suffered too much 
from attention span issues in other situations too feel comfortable with so 
many important things flying around.

Best,
Rui