Open Source Community Structures
0 likes480 views
Open source community structures can take many forms, from a benevolent dictator model like Linux led by Linus Torvalds, to a committee-based model like Apache. Communication within these communities typically occurs through mailing lists, IRC, conferences, and code sprints. Contributions are often managed through pull requests and code reviews, and contributors may be asked to sign a contributor license agreement assigning copyright.
Open Source Community Structures
- 1. Open Source Community Structures Open Source Community Structures by Michel Alexandre Salim is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. 1 / 19
- 2. Who and what is Open Source? 2 / 19
- 3. Who 1985 - RMS founded the GNU Project The New Yorker: The GNU Manifesto Turns Thirty 1991 - Linus Torvalds announced Linux 1993 Ian Murdock announced the Debian distribution Bob Young) founded ACC Corporation FreeBSD 1.0 1994 Marc Ewing created Red Hat Linux 1995 Brian Behlendorf et al., Apache HTTP Server ACC-RHL merger to form Red Hat Software 1998 Netscape created Mozilla Bruce Perens and ESR, The Open Source Initiative 1999 Apache Software Foundation Red Hat IPO 2004 * Mark Shuttleworth invited senior Debian developers, founding Ubuntu Wikipedia: History of Free and Open-Source Software 3 / 19
- 4. What Free Software Open Source Software Licenses 4 / 19
- 5. What is free software? A program is free software if the program's users have the four essential freedoms: The freedom to run the program as you wish, for any purpose (freedom 0). The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this. The freedom to redistribute copies so you can help your neighbor (freedom 2). The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this. The Free Software Definition 5 / 19
- 6. What is open source? 1. Free Redistribution 2. Source Code 3. Derived Works 4. Integrity of The Author's Source Code 5. No Discrimination Against Persons or Groups 6. No Discrimination Against Fields of Endeavor 7. Distribution of License 8. License Must Not Be Specific to a Product 9. License Must Not Restrict Other Software 10. License Must Be Technology-Neutral The Open Source Definition 6 / 19
- 8. Some common FOSS licenses Permissive BSD / MIT / ISC Apache License WTFPL Weak copyleft File-based Mozilla Public License Common Development and Distribution License (derived from MPL v1.1) Module-based Eclipse Public License GNU LGPL Strong copyleft GNU GPL GNU Affero GPL Fedora wiki - Licensing:Main 8 / 19
- 9. Who Leads FOSS Projects? 9 / 19
- 10. Benevolent Dictator for Life 10 / 19
- 11. Benevolent Dictator for Life Examples GNU: RMS Linux: Linus Torvalds Python: Guido van Rossum Delegation Linux: List of maintainers and how to submit kernel changes Python: PEP 1 - PEP Purpose and Guidelines 11 / 19
- 12. Committee Apache How the ASF works Governance Debian Constitution Project Leader Technical Committee General Resolution Fedora Project Leader Council Engineering Steering Committee Packaging Committee 12 / 19
- 13. Corporation Java Java Community Process Java Specification Requests 13 / 19
- 14. Access to Repository Commit Bit FreeBSD: Commit Bit Types Module maintainers Debian Maintainers Fedora Package Maintainers Pull requests GitHub: Using pull requests Code reviews Android Open Source Project: Life of a Patch 14 / 19
- 15. But wait... 15 / 19
- 16. Copyright Assignment / Contributor License Agreement Wikipedia definition Apache Individual Corporate Fedora FPCA Canonical CLA Why the FSF gets copyright assignments from contributors 16 / 19
- 18. Communications mailing lists IRC video conferencing conferences code sprints 18 / 19
- 19. That's all, folks! 19 / 19