how opensourceworks

Copyright © 2012 FuseSource Corp.. All rights reserved. 1

How Open Source Works


History of Open Source

IBM 704

DOJ forces IBM to

unbundle free software

1950 1960 1970 1980 1990 2000 2010


History of Fuse open source Development

2004 2005 2006 2007 2008 2009 2010 2011 2012

ActiveMQ createdMay 2004

The CodeHaus

ServiceMix createdMay 2005

Camel createdMarch 2007

IONA acquireApril 2007

Karaf createdNovember 2007

Progress acquireOctober 2008

FuseSource createdOctober 2010

The Apache Software Foundation

LogicBlaze FormedMay 2005

CXF August 2006

Fabric createdFebruary 2011

Fuse Forge AndASF


Contributing to the Apache Software Foundation


Benefits of Contributing to Apache

As an Organization• Influence the key projects that ultimately will save you costs• Developers will have access to the best practices and innovation

in software development As a developer

• Appreciation• Self-education• Reputation• Control• Reuse


How do I start ?

Choose your project Join the mailing list or forum Check out the code Find open issues and feature requests Ask Developers what you could work on Help out other users on the user lists


Contributing

Ideas! Features and Bug Fixes Unit tests Documentation Benchmarks Help out other users on the user lists


Working inside the Apache Software Foundation

Community before Code Let they that do make the decisions If it didn’t happen on the mailing list – it didn’t happen Any new feature should always be in jira first Critique the code – not the coders To become a committer – act like a committer


How FuseSource works with Apache


FuseSource employees work on many Apache projects


How FuseSource packages distributions of Apache Projects


FuseSource Subscription : Certified Distributions

Fuse ESB (ServiceMix), Fuse Message Broker (ActiveMQ),Fuse Mediation Router (Camel), Fuse Services Framework (CXF)

• Tested – integrated tests on supported platforms• Productized distributions – versioned, supported releases• Freely available with Apache license (can edit code and redistribute)• Enterprise-class distributions of popular apache projects


Fuse: regular, stable releases.

Frequent (often daily) snapshot releases

Highly collaborative development

Developer-driven process in Apache community

Test, documentation follow release, are driven by community

Patches for customers are returned to community

Additional documentation and extras also contributed

Apache

FuseSource distributions

Code,

Basic docs

Code

Docs

Demos

Test

Interop

Support

Licensing

Assurance

Core development occurs within the Apache community

Community releases are more “cutting edge”

FuseSource adds testing, QA, docs, extras

Regular, stable, tested & supported releases

“Product-oriented” development

End-user focused process, thru feedback in FUSE community

Test, documentation etc. are part of release

how opensourceworks

Documents

fusesource subscription

fusesource employees

committer8 copyright

apacheprojects10 copyright

apache9 copyright

apache communitytest

apache license

user lists6 copyright