1. Open SourceJuly 26, 2008 Ronell B. Sicat( MS EcE )‏ opening ourselves to OPEN SOURCE

2. Part 1: Introduction part 2: "IOSN: Connecting and Empowering Communities through F/OSS" by Dr. Sarmienta Part 3: Open Source Review part 4: OPEN CONTENT part 5: how can we contribute? part 6: Case study: sahana part 7: open forum opening up to open source

3. Part 1: introduction an OPEN SOURCE experience

4. Part 2: "IOSN: Connecting and Empowering Communities through F/OSS" the power of OPEN SOURCE by Dr. Francisco Sarmiento III

5. Part 3: Open Source Review Getting to know OPEN SOURCE

6. what is Open Source? http://www.opensource.org 1: http://en.wikipedia.org/wiki/Open_source Software development methodology which makes source code publicly available for editing and redistribution. Open source means a freedom to access a product's source (goods and knowledge) 1.

7. The Open Source Definition 2 ● Free Redistribution. ● Source Code: complete, available and accessible. ● Derived Works. ● Integrity of The Author's Source Code. ● No Discrimination Against Persons or Groups/ Fields of Endeavor. ● License Must Not Restrict Other Software. 2: http://www.opensource.org/docs/definition.php

8. Principles of Open Source 3 Openness - availability of the design documents and source code enables the community to provide peer reviews and to use the software for their purposes and provide feedback on the quality. Transparency - A glass door is transparent but whether it is open or not is a different matter. Transparency provides the community the ability to witness the inner workings of the administrators. 3: http://wiki.pentaho.com/display/BEEKEEPER/2.+The+Principles+of+Open+Source

9. Principles of Open Source 3 Early and Often - the philosophy of making information available in its earliest drafts and updating it often. Community - It is these principles and the results of using them that ultimately attract and retain the community. The community is a byproduct of the project. The project is a byproduct of the open source principles. 3: http://wiki.pentaho.com/display/BEEKEEPER/2.+The+Principles+of+Open+Source

10. Benefits of Open Source Software Better quality. Higher reliability. More flexibility. Lower cost. End to predatory vendor lock-in.

11. Example 1: Firefox Open source web browser. Created under Mozilla.

12. Firefox community

13. Example 2: OpenOffice.org Open Source office suite. Founded by Sun Microsystems in 2000.

14. OpenOffice.org Applications

15. OpenOffice.org Community

16. Motivation of oss Developers To meet a real need (Ex. Sahana). Motivated by technical challenge and would rather write software than buy an off-the-shelf product. Can't find a commercial product that meets their needs. Pride and reputation. Good training. From: http://www.opportunitywales.co.uk/2-1-5a.htm

17. Part 4: Open Content and CC Licensing copyleft not copyright

18. What is Open Content? “All material (text, sound, images) that the general public can freely use, distribute and modify without the traditional restrictions imposed by copyright.” 4 Counterpart of Open Source Software. Open Content can be licensed using copyleft.  “Copyleft is a play on the word copyright and describes the practice of using copyright law to remove restrictions on distributing copies and modified versions of a work for others and requiring that the same freedoms be preserved in modified versions.” 5 4: Liang, Lawrence. Free/Open Source Software: Open Content. 5: http://en.wikipedia.org/wiki/Copyleft

19. Creative Commons Introductory Videos

20. “Creative Commons defines the spectrum of possibilities between full copyright — all rights reserved — and the public domain — no rights reserved. Our licenses help you keep your copyright while inviting certain uses of your work — a “some rights reserved” copyright.” 6 5: http://creativecommons.org/about/ Creative commons 5: http://creativecommons.org/about/  “Some rights reserved”  Full Copyright  Public Domain 6: http://creativecommons.org/about

21. Creative Commons: Licenses Attribution. You let others copy, distribute, display, and perform your copyrighted work — and derivative works based upon it — but only if they give credit the way you request. Noncommercial. You let others copy, distribute, display, and perform your work — and derivative works based upon it — but for noncommercial purposes only. No Derivative Works. You let others copy, distribute, display, and perform only verbatim copies of your work, not derivative works based upon it. Share Alike. You allow others to distribute derivative works only under a license identical to the license that governs your work.

22. Creative Commons: Licenses

23. Wikimedia Example http://commons.wikimedia.org/wiki/Image:European_Common_Frog_Rana_temporaria.jpg

24. Part 5: C ontributing to O pen s ource for a good cos :

25. How Can WE Contribute? ● Create and share your work. ● Participate in software development communities. ● Submit bug reports. ● Suggest new features and options. ● Help write good documentation. ● Translate code/documentation to another language. ● Maintain a FAQ or HOWTO document. ● Convince people to chose Open Source products when possible. ● Send the programmers some money. =) From: http://www.granneman.com/techinfo/linux/contributewithoutcoding.htm

26. how can we contribute? Submit patches:  “A patch, or diff, is a record of changes made to a resource. Typically a patch will add a new feature, fix a bug, or add documentation to the project.” 7  “Patches are the preferred way to submit contributions to open development projects such as open source software.” 5 7: http://www.oss-watch.ac.uk/resources/softwarepatch.xmlhttp://www.oss-watch.ac.uk/resources/softwarepatch.xml 8: Friedman, Thomas L. “The World is Flat”. 2006. APACHE was coined from “aPAtCHy” or many patches. 8

27. how can we contribute? Build your own software repository:  “Repository generically refers to a central place where data is stored and maintained. A repository can be a place where multiple databases or files are located for distribution over a network.” 9 9: http://www.webopedia.com/TERM/r/repository.htm # Ubuntu supported packages deb http://archive.ubuntu.com/ubuntu feisty main restricted deb http://archive.ubuntu.com/ubuntu feisty-updates main restricted deb http://archive.ubuntu.com/ubuntu feisty-security main restricted deb http://archive.ubuntu.com/ubuntu feisty-proposed main restricted deb-src http://archive.ubuntu.com/ubuntu feisty main restricted deb-src http://archive.ubuntu.com/ubuntu feisty-updates main restricted deb-src http://archive.ubuntu.com/ubuntu feisty-security main restricted deb-src http://archive.ubuntu.com/ubuntu feisty-proposed main restricted

28. Support F/OSS Create, Share or Use OPEN SOURCE SOFTWARE. Create, Share or Use OPEN CONTENT. Promote, promote, promote.

38. Part 6: Case Study: SAHANA SAHANA maulit muli...

39. Managing Disasters (SAHANA) Free and Open Source Disaster Management system. Was born of the Sri LankaTsunami in 2004. Web based collaboration tool that addresses the common coordination problems during a disaster:  Finding missing people.  Managing aid.  Managing volunteers.  Tracking camps effectively between Government groups, the civil society (NGOs) and the victims themselves. From: http://www.sahana.lk/

40. Managing Disasters (SAHANA) Runs on GNU/Linux, xBSD, MAC OS X and Microsoft Windows. F/OSS. Uses LAMP software stack. Can be readily distributed, localized and customized according to the requirements of the region or community using it. Poor countries can also afford to use it. From: http://www.sahana.lk/

41. SAHANA in the Philippines Philippine SAHANA Initiative.  April 24, 2007.  Organized by Bluepoint foundation.  Provided training for NDCC, Red Cross, AFP, DOH, DPWH, DOST and other Government intitutions.

42. How does SAHANA look like?

43. conclusion Open Source Software rocks!!!

44. Thank You for listening. Any Questions?

45. The POSS model is a robust combination of an open source project, a professional open source company backing that project, and a complete Go To Market program. Not only does the model benefit from the advantages of each there are additional benefits for all participants. Professional Open Source Software Model

46. Proprietary Model

47. Professional Open Source Software Model Open source model

48. Professional Open Source Software Model professional Open source software model

49. Open source community benefits directly from the full-time engineering staff that exist because of the fee-paying customers. The customers benefit from the increased quality of the software, quality of design, and increased traction enabled by the open source community. Professional Open Source Software Model

50. The POSS company benefits by increasing its valuation when it meets the needs of both customers and open source community. The model is powerful because the customers, partners, engineers, and open source communities are all self-motivated to behave in ways that are beneficial to themselves and, as a side effect, beneficial to all the others. Professional Open Source Software Model