Eric Fesler discusses using open source software. He explains that open source ensures certain software freedoms like free redistribution and access to source code. Fesler recommends choosing open source by defining needs, identifying options from directories like SourceForge, and doing a detailed review of aspects like community support and licensing. He advises working with open source by selecting best of breed components, managing version compatibility, and standardizing libraries.

1. Using Open Source
Eric Fesler - Audaxis

2. Me

3. Eric Fesler
eric@audaxis.com
http://www2.audaxis.com/roller/eric

4. AUDAXIS
Co-Founder
Technical Director
CTO

5. Audaxis
• Open Source solutions integrator
• Main Compiere Partner in Europe
• ezPublish Partner
• Open Source Java project contributor
• Drupal contributor

6. • What is Open Souce ?
• How to Choose an Open Source Solution ?
• Working with Open Source Components

7. What is Open Source ?

8. Open Source describes
a software licence that
ensures certain
freedoms.

9. Open Source Definition
Development Methodology
• Free Redistribution
• Source Code
• Derived Works
• Integrity of Author’s code
• No Discrimination against Persons or Groups
• No Discrimination against Fields of Endeavor
• Distribution of License
• License Must Not Be Specific to a Product
• License Must Not Restrict Other Software
• License Must be Technology-Neutral
Source: http://www.opensource.org/docs/osd

10. Free Software
Social Movement - 4 Freedoms
• The Freedom to run
• The Freedom to study
• The Freedom to redistribute
• The Freedom to improve

11. Free vs Open Source
FREE SOFTWARE OPEN SOURCE
• Freedom of the code • Freedom of the developer
• Source code will ALWAYS • Code CAN be included in
be available and can never proprietary works under
be restricted. certain conditions.

12. Licenses

13. OSI Approved
64
Academic Free License 3.0 (AFL 3.0) MIT license
Affero GNU Public License Motosoto License
Adaptive Public License Mozilla Public License 1.1 (MPL)
Apache License, 2.0 Multics License
Apple Public Source License NASA Open Source Agreement 1.3
Artistic license 2.0 NTP License
Attribution Assurance Licenses Naumen Public License
New and Simplified BSD licenses Nethack General Public License
Boost Software License (BSL1.0) Nokia Open Source License
Computer Associates Trusted Open Source License 1.1 Non-Profit Open Software License 3.0 (Non-Profit OSL 3.0)
Common Development and Distribution License OCLC Research Public License 2.0
Common Public Attribution License 1.0 (CPAL) Open Font License 1.1 (OFL 1.1)
CUA Office Public License Version 1.0 Open Group Test Suite License
EU DataGrid Software License Open Software License 3.0 (OSL 3.0)
Eclipse Public License PHP License
Educational Community License,Version 2.0 Python license (CNRI Python License)
Eiffel Forum License V2.0 Python Software Foundation License
Entessa Public License Qt Public License (QPL)
European Union Public License (link to every language's version on
their site) RealNetworks Public Source License V1.0
Fair License Reciprocal Public License 1.5 (RPL1.5)
Frameworx License Ricoh Source Code Public License
GNU General Public License (GPL) Simple Public License 2.0
GNU General Public License version 3.0 (GPLv3) Sleepycat License
GNU Library or "Lesser" General Public License (LGPL) Sun Public License
(LGPLv3)
GNU Library or "Lesser" General Public License version 3.0 Sybase Open Watcom Public License 1.0
Historical Permission Notice and Disclaimer University of Illinois/NCSA Open Source License
IBM Public License Vovida Software License v. 1.0
IPA Font License W3C License
ISC License wxWindows Library License
Lucent Public License Version 1.02 X.Net License
MirOS Licence Zope Public License
Microsoft Public License (Ms-PL) zlib/libpng license
Microsoft Reciprocal License (Ms-RL)

14. 3 types

15. • Level 1 - Gimme credit - APL, BSD, MIT
• Level 2 - Gimme fixes - MPL, LGPL, CDDL
• Level 3 - Gimme it ALL! - GPL
http://rollerweblogger.org/roller/entry/gimme_credit_gimme_fixes_gimme

16. Open source
developers must be
aware of the license
they use.

17. http://www.geekherocomic.com/2009/04/22/old-school-business-and-the-gpl/

18. Who is using Open
source?

19. • Large Companies - IBM, Sun
• Governments
• Association - Greenpeace
• Many others ...

20. Why using Open
Source?

21. “It’s impossible to avoid”
Gartner - 2007

22. “By 2011, at least 80%
of commercial software
will contain significant”
amounts of open source
code”
Gartner - 2007

23. Open source brings
you ...
• Lower Information Technology Costs
• Flexible software solution
• Customizable
• Open standards
• Collaborative support
• Vendor independency

24. Open Source
Challenges

25. • Documentation
• “Design for programmers”

26. Choosing an Open
Source Software

27. Open Source
Landscape

29. Server/Middleware
Software

30. Desktop Application

31. Web Application
®
eZ

32. Development
framework

33. How to choose an
Open Source
application ?

34. 1. Define needs and
constraints
• Organizational needs • Compatibility/Openness
• User needs • Existing skills
• Features
• Language
• Budget
• Timeframe

35. 2. Identify your options
• Recommendations
• Literature
• Software package
• Review and Directories

36. SourceForge
http://sourceforge.net
+230.000 projects

37. Freshmeat
http://freshmeat.net

38. 3. Detailed Review

39. What is specific to
Open Source ?

40. Reputation

41. Ongoing Effort

42. Standards and
Interoperability

43. Community Support

44. Commercial Support

45. Version policy

46. Documentation

47. Skill Set

48. Project development
model

49. License

50. Methodologies
• Open Business Readiness Rating (BRR)
• QSOS
• Open Source Maturity Model (Navico’s
OSMM)

51. BRR
http://www.openbrr.org
• Functionality • Architecture
• Usability • Support
• Quality • Documentation
• Security • Adoption
• Performance • Community
• Scalability • Professionalism

52. QSOS
http://www.qsos.org/

53. OSMM
http://www.navicasoft.com/pages/osmm.htm
• Software
• Support
• Documentation
• Training
• Integration
• Professional Services

54. How to compare with
Proprietary Solutions ?

55. 8./5$0,/'90$1
+,--./0$1 6 !5'9'?09$1
:';#),<).;# @ &4,<#;;0,/'9)!.>>,4$
345"0$#5$.4# =>#/#;;
7,5.-#/$'$0,/
State of the art

56. 8/06$1-0'91$2
,-../01$2 + !6'9'?19$2
:';#)-<)/;# @ &5-<#;;1-0'9)!/>>-5$
456"1$#6$/5# =>#0#;;
7-6/.#0$'$1-0
After customization

57. What you do not pay in
license you can invest in
service and
customization

58. Working with Open
Source Components

59. Component Landscape

60. Frameworks

61. Librairies

62. Frameworks

63. The key issue is ...

64. EXPERTISE

65. Define your stack

66. Struts
Spring
Hibernate

67. GWT
Spring
Hibernate

68. Keep an eye on new
versions

69. Upgrade your projects

70. Librairies

71. “Do not reinvent the
wheel”

72. Key issues

73. • Selection
• Compatibility
• Standardisation

74. Selection

75. Use Best of Breed
Components
• Reputation
• Stability
• Adoption

76. Version Compatibility

77. Dependency issue
My Lib A Lib C
Code 2.1 3.0
Lib B Lib C
2.5 3.1

78. Define Version Packs

79. Standardisation

80. Build your own
repository

81. Use Maven or Maven
like Versioning style

82. Always keep a safe copy
of the version source
code

83. Thank you !

84. References
• The first part of this presentation and its design are largely
inspired from: Making open source work - J Aaron Farr - 2008
http://www.slideshare.net/jaaronfarr/making-open-source-
work-presentation
• Choosing Open Source: A guide for civil society organizations
http://www.commons.ca/articles/fulltext.shtml?x=335
• Top Tips For Selecting Open Source - Software
http://www.oss-watch.ac.uk/resources/tips.xml
• Gimme credit, gimme fixes, gimme it ALL!
http://rollerweblogger.org/roller/entry/
gimme_credit_gimme_fixes_gimme