Today Adobe has announced that a large portion of the next version of Flex goes open source under Mozilla Public License (MPL). Here’s the partial list of what becomes open: mxml, compc, and ActionScript compiler, command line debugger FDB, Flex framework and RPC libraries and testing infrastructure.
These are some of the components and tools that will not be open sourced: Flex Builder, Charting components, Flash Player, Apollo.
This is a step toward creating a wider Flex 2 market. The interest to rich Internet technologies grows leaps and bounds, and Adobe Flex is one of the leaders in this league. There is already a decent number of developers who are interested in Flex and Adobe hopes that open sourcing Flex will bring more developers on board.
The source code of the Flex framework was available all the time, but the developers could have improved it by extending these components. But now they will be able to improve the original components as well.
Another good thing is that the third-party component developers will be able to include Flex compilers into their components. To the best of my knowledge, MPL will allow third parties distribute their own components under any other licenses as long as the original Flex code stays under MPL.
Next week we’ll start selling our first commercial Flex components and plugins at myflex.org. I’d love to hear an explanations of the MPL licensing from one of the Adobe officials using these components as an example. Does this move really encourages commercial component development by small companies?
The Web tier compiler is a gray area though – it’ll be open sourced for Apache containers and Microsoft IIS.
I was not able to get a clear answer if the third-party developers will be able to include Flex Web compiler into components deployed under commercial J2EE servers. In May, we are releasing our flagship component called FlexBI, which uses Flex Web compiler. Yesterday, we were assuming that it would by our customer’s responsibility to obtain Web tier compiler from Adobe. Will it change with open sourcing Flex? Are we allowed to include the Web tier compiler without worrying about what J2EE server our customer will deploy it under? What do you say, Adobe?
How are you planning to fix the Flex bugs in the new world? Sun Microsystems has so called bug parade for Java. People were able to vote for bugs, and the most “popular bugs” were supposed to be taken care of. This was a failure because some of the most voted bugs were sitting there for 7 years.
What about forking Flex framework? Is this going to be an issue?
One more question. Are we allowed to copy paste a chunk of the Flex source code into our commercial component as long as we keep references to the original author of this piece of code?
The FAQ on open source Flex, is written in Legal language, it would be nice to have an explanation in English with some use cases I’ve mentioned above.
Adobe will still govern the modifications of the Flex libraries – they’ll set up the repositories for the Flex source code, will set up builds, etc.
I believe that open sourcing Flex will draw attention of some serious developers to the new kid on the block. The Flex team may become substantially larger.