I just took the time to read through this interview with Phil Costa, director of Product Management for Flex at Adobe. (Many thanks to Dave McAllister for his link.) You may remember that Adobe announced in April its intention to open-source Flex.
Now, the company is talking about why. It's very interesting to see that the decision to open-source a product is somewhat universal in the considerations that go into it. It brings back memories of early 2003 when we (at Novell) were giddy about releasing the company's UDDI server as open source...
I particularly found Phil's thoughts on the LGPL (i.e., why Adobe opted not to go with LGPL and instead used MPL) fascinating.
At its core, Adobe's decision to open-source flex stemmed from a desire to make the project bigger than the company. That is, independent of the company. Something you could embrace without embracing the company, too. This is precisely the same reasoning that went into Alfresco's decision to GPL our enterprise content management system, so Phil's comments resonate with me.
In response to How Software Is Built's question as to why Adobe decided to open-source Flex, Phil replied:… Read more