flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Keith Sutton <ke...@spoon.as>
Subject Re: State of the Project
Date Mon, 23 Jan 2012 19:04:28 GMT
Having the vision/mission worked out is important to any project moving 
forward however it is also important to have (or be aware of) the 
necessary resources and support needed for success. Some of the 
necessary pieces sometimes go beyond the code into the 
platform/ecosystem/community/industry. The lack of automation and SDK 
3.x  (as two examples) do not make the 4.6 code unusable but it does 
hamstring an important segment of the ecosystem/industry which could 
compromise the project's ability to succeed (before it ever gets off the 

At this point Apache Flex is in the position of waiting for donations 
and Alex and co are stuck in the position of being the messengers (and 
we know what happens to them).

If automation and SDK 3.6 (as two examples) are considered critical by 
the project to it's health and success within the ecosystem/industry 
then how is Apache Flex going to influence the decision makers at Adobe?

Clearly a developer Automation is a significant e

On 1/23/2012 10:30 AM, Alex Harui wrote:
> On 1/23/12 3:00 AM, "Martin Heidegger"<mh@leichtgewicht.at>  wrote:
>> I think the tension here is justified. Many people waited for a long
>> time to work on things and the expectations are high.  Right now a lot
>> of requests and questions that the people have could be avoided if we
>> had some certainties:
>>     * What can we work on/discuss about?
> You can work on the code in Carol's whiteboard, or do just about anything
> you want in your own whiteboard.  You can discuss just about anything.
>>     * What is Apache Flex about?
>>        To me a clear mission statement that describes what the aim of the
>> flex project is, is long overdue.
> There are multiple missions.  One of which is to support improvements to
> exisiting apps and continued development of those apps and new apps.
> Another is to explore a migration strategy or compatibility-story or
> cross-compilation with the HTML/JS/CSS stack.
>>     * How and when can we "document" feature/bug/fix requests? I have
>> read mailing-list entries like "Jira is ready" and the
>>        Jira bug tracker is available for public use. However people
>> restrain because they want Adobes Jira to be imported before
>>        that. So: Does that make Jira: "not ready"?
> JIRA is open.  I'm hoping to migrate the old bugs this week, and it might
> make migration harder if there is lots of new stuff in Apache JIRA.  So I'm
> asking folks to be patient a little longer.

View raw message