come. ************ UPDATE -- 11/15/11 ************ Further to the above questions and answers, we received many comments for clarification and additional information on certain topics. We have provided answers to these below: What specifically is Adobe proposing? We are preparing two proposals for incubating Flex SDK and BlazeDS at the Apache Software Foundation. In addition to contributing the core Flex SDK (including automation and advanced data visualization components), Adobe also plans to donate the following: Falcon, the next-generation MXML and ActionScript compiler that is currently under development (this will be contributed when complete in 2012) Falcon JS, an experimental cross-compiler from MXML and ActionScript to HTML and JavaScript. Flex testing tools, as used previously by Adobe, so as to ensure successful continued development of Flex with high quality Adobe will also have a team of Flex SDK engineers contributing to those new Apache projects as their full-time responsibility. Adobe has in-development work already started, including additional Spark-based components. Isn't Adobe just abandoning Flex SDK and putting it out to Apache to die? Absolutely not -- we are incredibly proud of what we've achieved with Flex and know that it will continue to provide significant value for many years to come. We expect active and on-going contributions from the Apache community. To be clear, Adobe plans on steadily contributing to the projects and we are working with the Flex community to make them contributors as well. Flex has been open source since the release of Flex 3 SDK. What's so different