Download as PDF, PPTX
Uploaded byFrederik Questier
Free Libre Open Source Software Development
This document provides an overview of Free Libre Open Source Software (FLOSS) development. It discusses what FLOSS is, why to use and develop FLOSS, and how FLOSS is developed. FLOSS development is described as an open, collaborative process done within communities internationally. Developers work together decentralizedly using tools like mailing lists, version control systems, and bug trackers. New contributors start by engaging with communities, submitting issues and patches. Community leadership focuses on meritocracy, autonomy, and delegating tasks. Challenges to Cuban participation include internet access and license decisions, but these may be addressed through solutions.
More Related Content
Similar to Free Libre Open Source Software Development
Free Libre Open Source Software Development
- 1. FLOSS Free Libre OpenSource Software Development Prof. dr. Frederik Questier - Vrije Universiteit Brussel Presented for Cuba ELINF project april 2021
- 3. 9 FLOSS development workshops I. Whatis FLOSS? II. Why use FLOSS? III. Why develop FLOSS? IV. How to develop FLOSS? Contributing to a FLOSS project Starting a FLOSS project
- 4. In the beginning almostall software was... ➢ produced by academic & corporate researchers in collaboration ➢ shared with source code IBM “SHARE” user group (1955) Digital Equipment Computer Users' Society (DECUS, 1961) Source code: if encrypt(password) == encryptedpassword, then login=1, end Compiled code: 00100101110101001100110000111101100011000111000110101
- 5. … until BillGates wrote an Open Letter to Hobbyists: “Your sharing is stealing” (1976)
- 6. 18 1986: Stallman defined “FreeSoftware” as software with the freedoms to ➢ use ➢ study & modify ➢ share ➢ share modifications
- 7. The freedom tostudy & modify requires access to source code
- 8. 1998: “Open Source”sounds better than “Free Software”?
- 9. 22 Free software: idealism OpenSource: pragmatism (almost identical) software categories together: Free Open Source Software (FOSS) Free Libre Open Source Software (FLOSS) Spanish: “software libre y codigo abierto”
- 10. Software categories ➢ Anti-features arefeatures that users don’t want, including: ➢ Copy-protection ➢ DRM = Digital Rights/Restrictions Management ➢ Data lock-in because of secret file formats ➢ Time-limit / Planned obsolescence ➢ Artificial limitations (e.g. limited RAM, HD and max 3 concurrent programs in MS Windows Vista Home) ➢ Advertisements ➢ Tracking / Spyware
- 12. 1991 comp sci student Usenetposting to the newsgroup "comp.os.minix.": “I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones.”
- 13. >13594 developers from>1300 companies have contributed to Linux kernel
- 14. "Congratulations, you're onthe winning team. Linux has crossed the chasm to mainstream adoption." ➢ Jeffrey Hammond, principal analyst at Forrester Research, LinuxCon, 2010 “Linux has come to dominate almost every category of computing, with the exception of the desktop” ➢ Jim Zemlin, Linux Foundation Executive Director, 2011 “Linux is the benchmark of Quality” ➢ Coverity Report 2012
- 15. 100% of top500 supercomputers run Linux
- 17. Android, a mobileversion of Linux, has overall largest market share
- 18.
- 19. 33 Linus Torvalds “Making LinuxGPL'd was definitely the best thing I ever did.”
- 20. Free Software Licenses ➢ The4 freedoms are guaranteed and enforced by licenses ➢ Copyleft licenses ➢ protect the freedoms for everyone ➢ e.g. GNU GPL (General Public License) ➢ Permissive licenses ➢ include the freedom to deny the freedoms for others ➢ e.g BSD (Berkeley Software Distribution) →BSD code often in non-free closed source software (MS, Mac, ...)
- 22.
- 23. FLOSS promoted by ➢ VLIR-UOS ➢ VLIRED ➢ DarkAIV,EsFacil, Esfacil Authority, Easybuild, ABCD… ➢ (Moodle, Dspace) ➢ UCI ➢ Nova Linux ➢ Cuba: Estrategia Maestra: Informatización 2016 ➢ “10. Priorizar el empleo del Software Libre”
- 24. Werken met portfolio's 04/10/05| pag. 38 Why use FLOSS?
- 25. Good reasons to useFLOSS ➢ Stay in control ➢ Stay secure ➢ Avoid data lock in ➢ Avoid vendor lock in ➢ Interoperability ➢ Modularity ➢ Easy localization (including translation) and customization ➢ Most often cross platform ➢ Easier troubleshooting ➢ Sometimes better support ➢ Avoid license management and compliance issues ➢ Reduce costs ➢ Demanded when public funds are given
- 26. Row 1 Row2 Row 3 Row 4 0 2 4 6 8 10 12 Column 1 Column 2 Column 3 Our social responsibility: how open is the future?
- 27. Stay in control! Ifyou don't control the program, the program controls you! W hy?
- 29. Stay secure! You can'ttrust software if its source code is hidden W hy?
- 31. ➢ From the EuropeanParliament investigation into the Echelon system (05/18/2001): “If security is to be taken seriously, only those operating systems should be used whose source code has been published and checked, since only then can it be determined with certainty what happens to the data.”
- 32. ➢ Cryptographer, computer securityexpert Bruce Schneier: “Only bad security relies on secrecy” “Demand open source code for anything related to security”
- 33. Avoid: data lock in vendorlock in Improve interoperability W hy?
- 34. The (Unix) philosophyof connectable and reusable modular components → best modules are most reused → get most feedback → survival of the fittest → quality W hy?
- 35. Modularity and lightweightsolutions allow to use small or old devices W hy?
- 36. FLOSS tools are mostoften cross-platform W hy?
- 37. FLOSS tools are mostoften cross-platform CPU architectures supported by ➢ Microsoft Windows ➢ x86, ARM ➢ Linux ➢ Alpha, Blackfin, ARM, Atmel AVR32, Axis Communications' ETRAX CRIS, Texas Instruments TMS320, 68k, Fujitsu FR-V, Qualcomm Hexagon, HP PA-RISC, H8, IBM System/390, IBM Z/Architecture, IA-64, x86, M32R from Mitsubishi, Microblaze from Xilinx, MIPS, MN103 from Panasonic Corporation, OpenRISC, Power Architecture, SPARC, UltraSPARC, SuperH, Synopsys DesignWare ARC cores, S+core, Tilera, Xtensa from Tensilica, UniCore32, ColdFire W hy?
- 38.
- 40. Free license =eternal ! Avoid: License management burden License compliance issues “Piracy” W hy?
- 41. Sometimes we reallyneed to free ourselves from corporate brainwashing! Example: Don't use personal operating systems in multi-user environments W hy?
- 42. Esperenza Computer Classroomwith software sponsored by Microsoft 1 computer per user?
- 43. One (library catalog)computer per user?
- 44. 72 Free yourself Free yourself fromdogmas! from dogmas!
- 46. (K12)LTSP Linux Terminal ServerProject Networked classrooms Fat server runs the applications Thin clients visualize the applications need no hard disk can be 15 years old PC's
- 47. Better support Support isoften core of the FOSS business model + fair competition of service providers Easier troubleshooting Because of transparency W hy?
- 48. Increasingly governments andfunders demand Open Standards Source code W hy?
- 49. Werken met portfolio's 04/10/05| pag. 90 Why develop FLOSS?
- 50. Good reasons to developFLOSS ➢ No need to start from scratch ➢ Easy localization and customization ➢ Network effects ➢ Get contributions from others ➢ Steer future developments ➢ Possibility to involve students ➢ Business opportunities ➢ Fun ➢ Learning ➢ Altruism ➢ Self-advertizing
- 51. 94 "Seven open sourcebusiness strategies for competitive advantage” John Koenig, IT Manager's Journal, 2004 “Companies continue to waste their development dollars on software functionality that is otherwise free and available through Open Source. They persist in buying third-party proprietary platforms or creating their own proprietary development platforms that deliver marginal product differentiation and limited value to customers” Picture reproduced with permission
- 52. 95 Success in FLOSSrequires you to serve ➢ those who spend time to save money ➢ those who spend money to save time -- Mårten Mickos, CEO MySQL
- 53. Software freedom allowsyou to tap into innovation power and network effects otherwise not available Mårten Mickos, CEO MySQL
- 54. Study on theEconomic impact of open source software on innovation and the competitiveness of the Information and Communication Technologies (ICT) sector in the EU, 2006, R.A. Ghosh, UNU-MERIT, NL. et al., 287 pp.
- 55. Study on theEconomic impact of open source software on innovation and the competitiveness of the Information and Communication Technologies (ICT) sector in the EU, 2006, R.A. Ghosh, UNU-MERIT, NL. et al., 287 pp.
- 56. 102 “Open Source ...it's just a superior way of working together and generating code.” “Like science, Open Source allows people to build on a solid base of previous knowledge, without some silly hiding.” “you can obviously never do as well in a closed environment as you can with open scientific methods.” Linus Torvalds (2007-03-19). The Torvalds Transcript: Why I 'Absolutely Love' GPL Version 2.
- 57. FLOSS Free Libre OpenSource Software Development Part II Prof. dr. Frederik Questier - Vrije Universiteit Brussel Presented for Cuba ELINF project april 2021
- 58. How is FLOSSdeveloped? ➢ Openly ➢ Collaborative in communities ➢ Decentralized ➢ International ➢ With peer review ➢ Mainly by developers who are also users
- 59. 109 Development Linus Torvalds' style Delegateeverything you can Be open to the point of promiscuity Release early and often Linus' Law "given enough eyeballs, all bugs are shallow."
- 60. 110 Book published under OpenPublication License 19 lessons for open source development
- 61.
- 62. 112 The Cathedral andthe Bazaar about developers 1. Every good work of software starts by scratching a developer's personal itch. 2. Good programmers know what to write. Great ones know what to rewrite (and reuse).
- 63. 113 The Cathedral andthe Bazaar about users 6. Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging. 7. Release early. Release often. And listen to your customers. 8. Given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone. 11. The next best thing to having good ideas is recognizing good ideas from your users. Sometimes the latter is better.
- 64. 114 The Cathedral andthe Bazaar about development 17. A security system is only as secure as its secret. Beware of pseudo-secrets. 18. To solve an interesting problem, start by finding a problem that is interesting to you. 19. Provided the development coordinator has a medium at least as good as the Internet, and knows how to lead without coercion, many heads are inevitably better than one.
- 65.
- 66. Recommended best practicesfrom the open source development model From: Ibrahim Haddad, The Open Source Development Model: Overview, Benefits and Recommendations http://aaaea.org/Al-muhandes/2008/February/open_src_dev_model.htm
- 67. How is thesoftware released? ➢ Live repository (mainly for devs) ➢ Nightly builds (mainly for automated testing) ➢ Newest releases ➢ Candidate releases ➢ Stable releases (e.g. every 6M) ➢ Long Term Support releases (e.g. every 2Y)
- 68. Feature life-cycle inthe open source development model Understanding the Open Source Development Model, 2011, Ibrahim Haddad, Brian Warner, The Linux Foundation
- 69. Tools used byFLOSS developers ➢ Mailing lists ➢ Wikis ➢ (Distributed) version control systems (Git) ➢ Bug trackers ➢ Task lists ➢ Testing and debugging tools ➢ Package management systems ➢ Web site ➢ Web forum for supporting users
- 70.
- 71.
- 72. Contributing to FLOSS means participatingin a community
- 73. Becoming a contributingproject member is a learning process
- 74. Developers? ➢ Grow in theirrole ➢ Feedback ➢ Bug reports ➢ Feature requests ➢ Patches ➢ Core repository access ➢ Management / leadership roles (meritocracy) ➢ Usually not assigned tasks. Select tasks. ➢ Mix of volunteers and employees of different organisations
- 75.
- 76. How to startparticipating in a FLOSS community? ➢ Explore the community ➢ Subscribe to the dev mailing list ➢ Create account for code repository ➢ Grow in your contributions ➢ Feedback ➢ Bug reports ➢ Feature requests ➢ Patches ➢ Core repository access ➢ Management / leadership role (meritocracy)
- 77. Werken met portfolio's 04/10/05| pag. 130 Build and Manage a Community?
- 78.
- 79.
- 80.
- 81. Drupal Content Management Platform ➢ Powers2% of websites ➢ USA White House, MTV UK, Sony Music, Al Jazeera, ... ➢ >2900 themes ➢ >30000 modules ➢ 121000 active contributors ➢ >1.3M registered users on drupal.org
- 83. ➢ Commercial Open Sourcecompany ➢ Founded 2007 ➢ $173 million venture capital ➢ Over $200 million revenue in 2018 ➢ 3800 enterprise customers ➢ 800 employees ➢ Fastest Growing Private Technology Company in North America, 2013 ➢ “A leader for Web Content Management” by the 2014 Gartner Magic Quadrant
- 84. The general opensource system development cycle Ming-Wei Wu and Ying-Dar Lin. 2001. Open Source Software Development: An Overview. Computer 34, 6 (June 2001), 33–38. DOI:https://doi.org/10.1109/2.928619
- 85. Creating a FLOSS project& community ➢ Build trust ➢ License, quality, documentation, support, … ➢ “Release early, release often” ➢ “Be open to the point of promiscuity” ➢ Users → Contributors → Developers ➢ Community tools
- 86. Creating a FLOSS project& community ➢ Community leadership ➢ ≠ management ➢ Influence is a matter of merit ➢ Show, don’t tell ➢ Autonomy of everyone ➢ Dare to delegate
- 87. FLOSS community partipation/creation Cubanbarriers & challenges? ➢ Internet connectivity limitations ➢ Embargo restrictions ➢ Local policies ➢ Autonomy versus local management ➢ License decisions? ➢ Spanish versus English? ➢ Culture & attitudes?
- 88. FLOSS community partipation/creation Cubanbarriers & challenges? Solutions?
- 89. Assignment ➢ Search and list ➢ Website ➢ Sourcecode repository ➢ License ➢ Documentation ➢ Communication channels ➢ Bug / feature request tracking tool ➢ For these projects: ➢ ABCD v2 ➢ ABCD v3 ➢ EsFacil ➢ Moodle ➢ Vivo ➢ Dspace ➢ Invenio ➢ Polaris OS
- 90. Sources and recommended readling ➢ TheCathedral and the Bazaar, by Eric S. Raymond https://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar ➢ Producing Open Source Software: How to Run a Successful Free Software Project, by Karl Fogel, 2nd edition 2017, https://producingoss.com/ ➢ The Seven Laws Of Open Source Leadership, by Adrian Bridgwater, Forbes 2016, https://www.forbes.com/sites/adrianbridgwater/2015/09/06/the-seven-laws-of-open-source-leadership/
- 91.
- 92. Additional credits ➢ Photo LinusTorvalds: GFDL. Permission of Martin Streicher, Editor-in-Chief, LINUXMAG.com ➢ Picture (open source business strategies) from IT Manager's Journal, may 2004, with personal permission from John Koenig ➢ Screenshot http://www.openhandsetalliance.com/ ➢ Cartoon Open Source Fish by openssoft ➢ T-Shirt “Best things of life are free” by http://zazzle.com ➢ Drupalcon DC 2009 copyright by “Chris” (Flickr) ➢ Screenshot Acquia ➢ Internet map by The Opte Project, CC-by ➢ Open arrow, CC-by-nd by ChuckCoker ➢ Share matches CC-by-nc-nd by Josh Harper ➢ Question mark CC-by by Stefan Baudy ➢ Social Icons by Iconshock http://www.iconshock.com/social-icons/
- 93. This presentation wasmade with 100% Free Software No animals were harmed Questier.com Frederik AT Questier.com www.linkedin.com/in/fquestie www.slideshare.net/Frederik_Questier Q uestions? ¿Preguntas?