Open Source Software - What is it?
- 1. JOHAN LINÅKER, PHD Open Source Software (What??)
- 2. About Johan
- 3. What is Open Source Software?
- 4. Liberally Licensed, Collaboratively Developed Software* * https://medium.com/@stephenrwalli/there-is-no-open-source-business-model-cdc4cc20238
- 5. Liberally Licensed, Collaboratively Developed Software* * https://medium.com/@stephenrwalli/there-is-no-open-source-business-model-cdc4cc20238
- 7. Liberally Licensed Software • Software available under an open source license – License that follows the Open Source Definition and is approved by the Open Source Initiative (http://opensource.org) • Software which you may inspect, use, modify and redistribute • As long as you don’t discriminate against any user och use-case • Different conditions apply per license requirements • Copyright holder still holds its copyright
- 8. Permissive vs. Copyleft licenses • Permissive licenses – do whatever you want, as long as you recognize the copyright holder – E.g., MIT, BSD, Apache • Copyleft licenses – Above + share any modifications, additions and connecting code under same license. – GPL 2, GPL 3, AGPL • Permissive common for standardiszations and collaboration on non-differentiating software • Copyleft common when copyright holder wants to capture value back
- 9. Liberally Licensed, Collaboratively Developed Software* * https://medium.com/@stephenrwalli/there-is-no-open-source-business-model-cdc4cc20238
- 11. Collaboratively Developed Software • Software developed as projects by networks of individuals and organizations, aka. Open Source Communities • ”Members” of the community commonly both users and developers • Are united by a common vision and goal around the Open Source Software. • Incentives may differentiate – Individuals: Sense of belonging, recognition for contributions, solves paintpoint, build CV – Companies: Lower costs, increased innovation, branding and PR, strategic tool
- 12. Technical and non- technical contributions • A contribution can come in many forms… – Code contributions (bugfixes, improvements, features, test cases) – Design and prioritization input – Reporting and triaging of bugs – Suggesting improvements and new functionality – Writing documentation and manuals – Answering questions and joining discussions – Arranging events and meetups – Writing blog-posts and creating content for social media – Offering server space and cloud computing – Testing and quality assurance – Monetary support
- 13. Development process • Informal processes - often specific for each community • Collaborative development • Transparent and open discussions on issues (e.g., bugs reports, feature requests) and roadmap • Stored and available via online and open infrastructure • Decentralized requirements management • Community full of stakeholders, all with their own agendas (which may not always align)
- 14. Development Infrastructure • Means of synchronous and asynchronous communication – E.g., bulliten boards, mailing-lists, real-time chat • Ticket system for reporting, discussing and managing issues – E.g., Jira, Bugzilla • Knowlegde base/Wiki e.g., for road map, documentation, and communiy governance • Source code repository with code review and potentially build functionality