Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (athena.apache.org: domain of omuppi1@gmail.com designates
 209.85.212.179 as permitted sender)
MIME-Version: 1.0
Sender: omuppi1@gmail.com
From: Om <bigosmallm@gmail.com>
Date: Wed, 9 Jan 2013 11:15:21 -0800
Message-ID: 
 <CACK5iZd+qJSUH0AYEqgjM3w9G4gOL0Cbb0wGcQWVShV4_utabQ@mail.gmail.com>
Subject: New website release timing
To: dev@flex.apache.org
Content-Type: multipart/alternative; boundary=089e0103ee90fb54ab04d2dfe347

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

>
> Second, the Apache Publicity & Marketing team has scheduled the Press
> Release to publish to the wire services we subscribe to on Monday January
> 14th. This will give the Apache Flex website team (Nick K + ???) time to
> add all of the content to the publicly facing website. I understand that
> others are finalizing the work on the new version of the installer and are
> wrapping things up on this project, too. I assume someone will help Nick
> get all of Michelle Yaiser's Flex content uploaded before then....(LOL! or
> not....)


Not to take anything away from Nick's awesome work so far(thanks Nick!) ,
the website still needs quite some work.  I dont think it is fair to impose
this kind of a deadline on Nick.  And given that no one else has
volunteered to help out with the new website content, there is a very good
chance we wont have the new website up and running before the press release
goes out.

We have two choices, either we get more people to help out with the new
website content or we let the old website stay when the press release goes
out.  There are definitely going to be quite a few folks who will want to
check out our website when the release goes out.  It is better to have a
working, albeit duller looking website than an incomplete one.

Thoughts?

Om

--089e0103ee90fb54ab04d2dfe347--