open source components integration

Open Source components integration

© Anyware Technologies-All Right Reserved


David Sciamma

Eclipse Technical Manager

June 23rd, 2009

Objectives

Design Development Maintenance

How to choose an Open


Open Source component integration – June 23rd, 2009 – David Sciamma – Anyware Technologies

�How to choose an Open

Source component�How to integrate it in your

developments

�How to be involved



How to choose an Open Source component?

Objectives

• Best component

• Risk analysis

• Choice of a version



Criteria

Eclipse Public License

• License

►Different licenses for different cases

►What is the targeted business model?

►Copyleft?



Eclipse Public License

Apache License

GPLLGPL

BSDMozilla Public Licence

MIT

►Copyleft?

►Compatible with GPL?

Criteria

• CommunityUsers

Contributors



►How strong / vibrant is this community?

Committers

Criteria

• Ecosystem

► Individuals

►Service providers

►Adopters



►Adopters

− Software vendors

− Industry

►Diversity == Strong ecosystem

Criteria

• Maturity

►Quality, Development

process

►Tests

• Predictability

►Roadmap

►Respect of the initial

schedule



►Bug tracker

►Success stories

►Previous versions

Criteria

• Hosted by

►Foundation

►Forge

► Independent



► Independent

• Intellectual property ©

Methodologies

• QSOS

• OpenBRR

• Open Source Maturity Model (OSMM)



• …

Tools/Databases

• FLOSSMetrics

• QSOS

• Ohloh



• …

• The experience !



Integrate components into your developments

Different roadmaps

Your roadmap

T0 V1 V2 V3 V4



The component’s roadmap

VN VN+1 VN+2 VN+3VN-1

Roadmap integration

• 3 approaches

Passive Active Integrated



User Contributor Committer

Passive approach

Your roadmap

T0 V1 V2 V3 V4

Consumption(only)

User





(only)

Passive approach

• Consume frozen version of components

• Implement work around for bugs

• Advantages

User



• Advantages

►Safe

►Predictable

► Independent

Active approach

Your roadmap

T0 V1 V2 V3 V4

ConsumptionContributions:Bug fixes, feature requests…

Contributor





Consumption Bug fixes, feature requests…Communication channels….

Active approach

• Consume frozen version of components

• Suggest bugs and new features

• Integrate new version in the following iterations if it

includes fixes

Contributor



includes fixes

• Advantages

►New features / fixes can be integrated in N+1

►Shared effort on fixes

Integrated approach

Your roadmap

T0 V1 V2 V3 V4

Developments

Committer





are integrated

Integrated approach

• Integrate your roadmap and the component roadmap

• Develop on top of development branches

• Add new features to the component

Committer



• Advantages

► Influence the component roadmap

► Integrate soon

►Do not maintain work around or fork of the component



Be involved!

Why be involved ?

• Be able to influence/change the component roadmap

• Integrate your constraints

• Expertise image



• Create a more mature component

How to be involved ?

• Promote the software you use

• Suggest new features

• Test release candidates and report bugs



• Submit documentation improvements

• Participate in support channels

• Write code and fix bugs



Conclusion

Conclusion

• Open Source components are now often used

►“85% of companies are already using open-source software,

with most of the remaining 15% expecting to do so within the

next year .” - Gartner Research, Nov. 2008

But it must be carefully integrated into your developments



►But it must be carefully integrated into your developments

• The next step is to be involved!

►Switch from the consumer mode to the actor mode

Questions?David Sciamma

[email protected]


open source components integration

Technology