Free distribution
Source code access
Derived works
Protect integrety author's source code
2011: 85% will include elements O.S.
Global 2000 80% infrastructure, 25% business software
50% expertise to customise OSS
Not a business model
Not prelude commercial exploit
Based on services revenue
Community describes open source
Motivations, Revenues for product that reies OSS, Reducing costs, Providing community benefit, Pressure on competitors
Competitive positioning weapon
Confused scenarios of licenses, support, subscriptions
Copyleft, GPL, Apache, MIT, MPL, CPL, OSF
Reciprocal, GPL (80%)
Artistic, BSD
No "free", Sourcing a product increases costs, Companies need to analyze costs
Reduce costs, Acquisitions and updates
Building a community costs
Best interest stakeholders
Extend reach
Enables conversations
In line with, On underlying business model, Overall goals, Restrict fragmentation
Work with Webkit, Eclipse, AJAX, Dojo
XMP
BlazeDS
Tamarin
Flex (and ssociated libs)
FlexUnit
AIR sample codes
Adobe Source Libs
Generic image libs
Adobe Media Gallery
Background, Decision (spring 07), Announcement (april 07), Infrastructure (february 08), Mozilla Public License, Open Source and Free (commercial) Packages
Why?, Increase size and loyalty of community, Solid business foundation, Enable entrance of Flex into niche markets, Improve product definition process
Risks, Competitive tools can more effectively compete, FDT, IntelliJ, Lose license from OEM deals
License decision process, Single or dual?, Viral?, Reciprocal or academic?, Protect Adobe IP?, Accept contributions?, How to avoid IP contamination
Governance model, Adobe Flex management team sets priorities, Bugs and festure requests filed and voted via public system, Specs made available for public discussion, Gumbo specs were released one year ahead, Patches from community accepted via bug system, No external committers yet, but working on it
Head/heartaches, Licensing: everyone's a critic, Encouraging community, Ideas not broadly applicable, Easier to criticize than fix, Balance community goals and Adobe goals, How do you share when some technologies that are the basis of it are private?, Internal testing mechanism is extensive, but too fragile to put out publicly
What different?, Research other OS projects bettr, Communities, Sharing roadmaps, Make sure that Adobe benefit is related to amount of effort, Outside contributions dont start flowing in, Publishing specs is time consuming, Accepting patches is time consuming
