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)
Message-ID: <5010481A.20304@spoon.as>
Date: Wed, 25 Jul 2012 12:25:14 -0700
From: Keith Sutton <keith@spoon.as>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: flex-dev@incubator.apache.org
Subject: [ROADMAP] What is next?
References: <FE3592FD-590B-4D41-A18A-F864AFB21C3D@spoon.as>
In-Reply-To: <FE3592FD-590B-4D41-A18A-F864AFB21C3D@spoon.as>
Content-Type: multipart/alternative;
 boundary="------------010805080503020402050604"

--------------010805080503020402050604
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

With the successful release of 4.8.0-incubating it would be timely to 
have a discussion/consensus around the priorities going forward.

A couple of fundamental factors should be considered in this discussion:

    1) Adobe resources are not indefinite and from statements made early
    in the year it is possible they may no longer be available within
    6+/- months (plan for the worst case). Once these resources are gone
    it will be significantly harder to access/transition code assets;

    2) Successful open source projects/communities are commercially
    viable, as much as open source is about cool technologies and code
    it is also about having the resources to do what they want for as
    long as they want;

    3) Within the Fortune 1000 companies which has the greater installed
    base and therefore need for support/transition - Flex 3;

    4) This is not a typical open source project that grows over time,
    this is a commercially viable product with a significant customer
    base and ecosystem, Apache Flex does not have the luxury of time as
    organizations wrestle with the decisions in the 6-12 months over
    Flex versus HTML5/JS/CSS (hope is not a roadmap).

After gleaning through emails and blog posts the following is a list of 
potential things-to-do-next (please identify anything needing 
addition/deletion). When considering what is a priority, ask yourself 
'is this essential to Apache Flex success beyond the next 6-12 months':

    1) 4.6 ViewStack
    2) 4.6 Accordion
    3) 4.6 DateField
    4) 4.6 DataChooser
    5) 4.6 Enhanced DataGrid
    6) 4.6 missing automation libraries
    7) 4.6 missing fabridge
    8) 4.6 missing flash-integration
    9) 4.6 missing samples
    10) 4.6 missing embedded font support
    11) 3.x Flex SDK
    12) Flex compiler source code
    13) BlazeDS/BlazeDS.NET
    14) TLF
    15) Gravity
    16) FXG
    17) Squiggles
    18) OSMF

Notes:
Falcon and Falcon JS are not on the list until Q4 2012 and beyond
Adobe "Not be contributing the AIR for Linux SDK, LCDS, or LCCS to Apache"
Adobe "will ensure that the Adobe Flex SDK 4.6 and prior will be 
supported in future versions of Flash Player and AIR
Adobe "plans to maintain support for Flex projects in updates to Flash 
Builder 4.x"

--------------010805080503020402050604--