A primer on adapting open source software to an IT service organization. Focuses on how open source licenses are different and how it may affect your business model and intellectual property.

1. Introduction to Free Open Source Software Licenses Harley D. Pascua @leypascua http://ph.linkedin.com/in/leypascua

2. Disclaimer All information in this presentation are from my own research and understanding of open source license mechanics and technicalities. The Open Source Initiative and Free Software Foundation have nothing to do with this presentation. I am not an open source or free software expert. Just to be sure, hire a lawyer*.

3. Free, Open Source What is Software?

4. Free Software is like Free Beer X

5. It is nothing close to a freebie.

6. Free software has a license that ensures certain There are four freedoms in free software. freedoms *

7. Freedom to Run the program for any purpose

8. Freedom to Study how the program works, and adapt it to your needs

9. Freedom to Redistribute copies so you can help your peers

10. Freedom to Write and release improvements So the community benefits

12. What’s stopping Open Source? ?

13. You can’t use open source It may compromise intellectual property

14. You can’t use open source It lacks integration with existing infrastructure.

15. You can’t use open source It lacks certification, there are no warranties.

16. You can’t use open source You don’t have the culture to govern it.

17. You can’t use open source You love proprietary software so much that you need expensive training to learn it.

18. There are supporting factors that encourage Open Source adaptation.

23. Consider Open Source And use it to reduce the risk of vendor lock-in.

24. Make the move to open source. T he big guys are playing.

26. The light is GREEN for open source. Save money and provide stability. No forced upgrades. Have rights to the code. Reach a skilled community of developers.

27. The light is GREEN for open source. Save money and provide stability. No forced upgrades. Have rights to the code. Reach a skilled community of developers.

28. 80% of all commercial software will contain open source code. By 2010

29. Open source is defined by ten sections. Read them carefully.

30. Free Distribution. Free software must be distributed freely. 1

31. Free Source Code. Source code must be readily available. 2

32. Derived Works. Allow modifications and combined works to be distributed. 3

33. Integrity of Code. “ Unofficial" changes can be made available but readily distinguished from the base source 4

34. All People Have Rights. Diverse people and groups should have equal rights to the free software. 5

35. Rights for All Endeavors. Free software shall not restrict its use for any specific industry or effort. 6

36. Distribution of License. The rights attached to the program must apply to all to whom the program is redistributed 7

37. Not Specific to a Product. The license must not be restricted to a specific product distribution. 8

38. Must Not Restrict Other Software. The license must not insist that all software distributed with an open source software must be open source. 9

39. License Must Be Technology Neutral. No provision of the license may be predicated on any individual technology or style of interface. 10

40. You can distribute software in three ways. Make copies on physical media, send files through the wire or open it for subscription.

46. You can’t just mix and match software licenses They have to be compatible.

47. License Compatibility A license p is compatible with a license q (or is q-compatible ) if and only if: A work licensed under p can be distributed under the terms of q . “ ”

48. Watch out for GPL Compatibility! It can make or break your business strategy.

51. Drawing the Line Between GPL Compatible and Incompatible Licenses

54. License Compatibility

55. Can You Re-License? It depends on how the derived work was created. Use of the Software Permissive Weakly-Protective Strongly-Protective Derivative Work (modified, copied code) YES DEPENDS NO Combined Work (static/dynamic linking) YES YES NO Derivative and Combined Work YES DEPENDS NO

57. GPL Compatibility is most important when you plan to distribute a version of a derived work.