There is only one serious course about Free and Open Source Software Development delivered in Australia annually, the postgraduate level COMP8440 at ANU. Moreover the course is delivered by Andrew "Tridge" Tridgell who authored the seminal open source projects samba and the rsync algorithm. During this course he discusses his wealth of experience and trains then assesses students on contributing to the open source community.
This talk will be conveying as much of this week-long course as is possible in the time available, as seen through the eyes of a graduating student who was always keen about open source yet who hadn't made their first pull-requests until during this course. Now, more than a year later, the presenter is actively involved in several open source projects and will be talking about some of the characteristics of the open source community today and describing in specific detail about how to become involved. The presenter will discuss the highs, the lows, the awkwardness and unique sense of connection and achievement that can only be fulfilled by contributing to open source.
Elena Williams is a python/django web developer now working in Perth. She graduated from Master ITS program from CECS ANU in 2012. She's taught Django/Python, been involved with the Django, Python and Linux communities around Australia and organised the Python user group in Canberra whilst studying at ANU. She presented about open source participation at PyConAU 2012. She is also enthusiastic about teaching programming to non-programmers, kitesurfing, snowboarding, endurance navigation sports; is an active hacker/maker and was only called a Douglas Adams "tragic" by the Canberra Times once.
Open source refers to software whose source code is publicly accessible and allows for modification and redistribution. The document discusses key aspects of open source including its philosophy of free access and sharing, criteria for open source licenses, examples of popular open source software, and advantages like availability of source code and large developer communities. Common open source licenses are also outlined.
The document defines open source as a philosophy that promotes free redistribution and access to a product's design, ideas, and implementation details. Open source software is released to the development community for further evolution, whereas closed source software is developed privately by a small team. Open source has advantages like availability of source code, not depending on vendors, better quality/customizability, and lower costs compared to proprietary software. However, open source can also have disadvantages like a learning curve, incompatibility issues, and lack of financial incentives for developers. Popular examples of open source include Android, Linux, Firefox, and LibreOffice. The document also discusses open source licensing and common myths about open source software.
A slideshow on what Open Source is, how to start contributions with special focus on Mozilla's own contribution pathways.
Credits: Ritwick Halder (http://www.slideshare.net/geniusanalyser/open-source-seminar-presentation?qid=46528d24-df84-4603-b731-4f7883341a2f&v=default&b=&from_search=7)
This slidedeck is the first presentation in a series of presentations on legal issues on open source licensing by Karen Copenhaver of Choate Hall and Mark Radcliffe of DLA Piper. To view the webinars, please go to http://www.blackducksoftware.com/files/legal-webinar-series.html. You may also want to visit my blog which frequently deals with open source legal issues http://lawandlifesiliconvalley.com/blog/
More than ever, open source software is at the heart of modern online businesses and technology companies. Open source is nearly everywhere: web browsers, smartphones, home wireless routers, databases, web servers, and countless components of free, commercial, and large enterprise software. But most open source software comes with strings attached, and if misunderstood, they can trip up the unwary.
Topics:
• The most common sources of non-compliance with open source licenses
• The key differences between the most popular licenses
• The basis in intellectual property law for open source licensing
• How courts in the US and abroad have enforced open source licenses
These slides are from a webinar by attorney Ansel Halliburton on September 22, 2015.
Open source refers to a philosophy of free access to software design and implementation details. It promotes sharing and modifying source code. Some key advantages of open source include availability of the source code, contributions from a large development community, lower costs, and greater customizability compared to proprietary software. However, open source software may require more learning and have issues with incompatibility or quality assurance. Popular examples of open source include Android, Linux, and open source digital content. Licenses like GPL determine how open source code can be used and distributed.
- Twitter relies heavily on open source software and contributes a significant amount of code back to the open source community.
- In 2011, Twitter created an Open Source Office to direct all open source efforts related to compliance, standards, and engineering outreach.
- The Open Source Office established review processes, licensing guidelines, and development best practices to manage open source code in a transparent and compliant manner while still facilitating contributions and collaboration.
Open source refers to software whose source code is publicly accessible and allows for modification and redistribution. The document discusses key aspects of open source including its philosophy of free access and sharing, criteria for open source licenses, examples of popular open source software, and advantages like availability of source code and large developer communities. Common open source licenses are also outlined.
The document defines open source as a philosophy that promotes free redistribution and access to a product's design, ideas, and implementation details. Open source software is released to the development community for further evolution, whereas closed source software is developed privately by a small team. Open source has advantages like availability of source code, not depending on vendors, better quality/customizability, and lower costs compared to proprietary software. However, open source can also have disadvantages like a learning curve, incompatibility issues, and lack of financial incentives for developers. Popular examples of open source include Android, Linux, Firefox, and LibreOffice. The document also discusses open source licensing and common myths about open source software.
A slideshow on what Open Source is, how to start contributions with special focus on Mozilla's own contribution pathways.
Credits: Ritwick Halder (http://www.slideshare.net/geniusanalyser/open-source-seminar-presentation?qid=46528d24-df84-4603-b731-4f7883341a2f&v=default&b=&from_search=7)
This slidedeck is the first presentation in a series of presentations on legal issues on open source licensing by Karen Copenhaver of Choate Hall and Mark Radcliffe of DLA Piper. To view the webinars, please go to http://www.blackducksoftware.com/files/legal-webinar-series.html. You may also want to visit my blog which frequently deals with open source legal issues http://lawandlifesiliconvalley.com/blog/
More than ever, open source software is at the heart of modern online businesses and technology companies. Open source is nearly everywhere: web browsers, smartphones, home wireless routers, databases, web servers, and countless components of free, commercial, and large enterprise software. But most open source software comes with strings attached, and if misunderstood, they can trip up the unwary.
Topics:
• The most common sources of non-compliance with open source licenses
• The key differences between the most popular licenses
• The basis in intellectual property law for open source licensing
• How courts in the US and abroad have enforced open source licenses
These slides are from a webinar by attorney Ansel Halliburton on September 22, 2015.
Open source refers to a philosophy of free access to software design and implementation details. It promotes sharing and modifying source code. Some key advantages of open source include availability of the source code, contributions from a large development community, lower costs, and greater customizability compared to proprietary software. However, open source software may require more learning and have issues with incompatibility or quality assurance. Popular examples of open source include Android, Linux, and open source digital content. Licenses like GPL determine how open source code can be used and distributed.
- Twitter relies heavily on open source software and contributes a significant amount of code back to the open source community.
- In 2011, Twitter created an Open Source Office to direct all open source efforts related to compliance, standards, and engineering outreach.
- The Open Source Office established review processes, licensing guidelines, and development best practices to manage open source code in a transparent and compliant manner while still facilitating contributions and collaboration.
Open Source Licenses / A presentation By Dr. Kalyan C Kankanala
Contact Us for Intellectual Property Services
BananaIP Counsels
Regd Office
No.40,3rd Main Road,JC Industrial Estate,
Kanakapura Road,Bangalore – 560 062.
Email: contact@bananaip.com
Telephone: +91-80-26860414 /24/34
Open Innovation and Opensource SoftwarePradyot Sahu
The document discusses open innovation and open source software. Open innovation involves using innovations created by others through processes, products, or knowledge. It is characterized by purposeful knowledge inflows and outflows, organic growth of innovation, and reliance on outside innovators. Open source software development is a form of open innovation where the intellectual property is openly available and projects involve collaboration. However, open innovation does not always involve making internal components openly available as with systems like IBM PCs.
There are hundreds of open source licenses. Most developers don't take the time to read or understand them, but can you continue to ignore them? We have seen a rise in litigation around open source license over the last 10 years. And, in the last 12 months we have seen the first examples of OSS copyright trolls that are taking developers to court in an attempt to monetize GPL violations.
This presentation covers: How OSS licenses are enforced;
What are the main types of OSS licenses; How to identify them;
and what steps you need to take to ensure you are complying.
We cover use case scenarios and do a "deep dive" on the most used licenses today and how to understand them
Fundamentals of Free and Open Source SoftwareRoss Gardler
Introduction to the OSS Watch Business
and Sustainability Models Around Free and Open Source Software. this presentation doesn't deal with the business models, it introduces FOSS and the key licence types.
GNU GPL, LGPL, Apache licence Types and DifferencesIresha Rubasinghe
The document discusses various open source software licenses including the GNU GPL, LGPL, and MsPL. It compares the different versions and terms of these licenses and provides examples of business models for open source software such as dual licensing and third party support services. The last section addresses combining open source license types and how some like the GPL and LGPL are compatible while others like different GPL versions may not be.
The document discusses how to properly license open source software to avoid legal issues. It recommends: 1) picking the right license for your project; 2) including attribution, license notices, and the full text of the license in your source code; and 3) using a contributor license agreement to assign copyrights of contributions to the project owner. Failure to follow proper licensing can result in losing control of your code, patents, trade secrets or even your company to legal issues. The presentation provides tips and examples of how to properly implement licensing.
Introduction to Open Source Hardware, OSHWA and Open Hardware SummitDrew Fustini
The document provides an overview of open source hardware, including definitions of open source, examples like Arduino, required documentation for electronics projects, licenses, and resources like the Open Hardware Summit and Open Source Hardware Association. It discusses open hardware principles, certification, and the use of Linux on open hardware boards and single-board computers.
"Open Source licensing and software quality" by Monty Michael Widenius @ eLib...eLiberatica
This is a presentation held at eLiberatica 2009.
http://www.eliberatica.ro/2009/
One of the biggest events of its kind in Eastern Europe, eLiberatica brings community leaders from around the world to discuss about the hottest topics in FLOSS movement, demonstrating the advantages of adopting, using and developing Open Source and Free Software solutions.
The eLiberatica organizational committee together with our speakers and guests, have graciously allowed media representatives and all attendees to photograph, videotape and otherwise record their sessions, on the condition that the photos, videos and recordings are licensed under the Creative Commons Share-Alike 3.0 License.
Open Source as IT and Business StrategyKarim Baïna
Open source as IT and Business Strategy for emergent countries. Morocco situation with regards to open source. How an emergent country may benefit from adpting open source software. How an emergent country can be prapared to oss transitiion. Examples of developed countries and emergent countries having adopted open source software within their IT strategy. Business models of open source.
Transforming IT with an Open Source StrategyInnoTech
This document summarizes several case studies of companies that implemented Hortonworks' open data platform solutions. It describes Mercy Medical System's goal of creating a single patient record across its health system and how Hortonworks helped achieve that. It also outlines how Progressive Insurance uses Hortonworks to ingest sensor data to power usage-based insurance, and how Western Digital uses it to gain insights from manufacturing test data to improve product quality. Finally, it discusses a home improvement chain's need for a customer golden record and targeted marketing, which Hortonworks enabled.
symfony: An Open-Source Framework for Professionals (PHP Day 2008)Fabien Potencier
This document provides an overview of the symfony open-source framework. It discusses that symfony is a PHP framework created by Sensio based on their 10 years of experience. It was built for professional websites and complex applications. The document outlines key symfony concepts like its use of the MVC pattern and organization into modules. It also highlights symfony's open-source license and documentation as well as its developer community and support offerings.
112 - The Role of Mentoring and Project Characteristics for Onboarding in Ope...ESEM 2014
Context: Onboarding is a process that helps newcomers become integrated members of their organisation. Successful onboarding programs can result in increased performance in conventional organisations, but there is little guidance on how to onboard new developers in Open Source Software (OSS) projects. Goal: In this study, we examine how mentoring and project characteristics influence the effectiveness and effi ciency of the onboarding process. We study a collaboration program involving a total of nine Open Source Software projects and more than 120 students from dfferent universities around the world as part of Facebook’s Education Modernization Program. Method: We use quantitative measurements of source code repositories, issue tracking systems, and discussion fora to examine how newcomers become contributing members of their OSS projects. Results: We found that developers receiving deliberate onboarding support through mentoring were more active at an earlier stage than developers entering projects through conventional means. Also, we found that project size and lifetime influenced on- boarding. Conclusion: Empirical decision support can contribute to a more effective onboarding process in OSS projects. Mentor sup- port in critical stages can accelerate the process, but project maturity is also a significant factor that increases the effect of onboarding.
Defining an Open Source Software Trustworthiness Model Davide Taibi
This presentation show the results of my PhD thesis.
Modern society depends on large-scale software systems of astonishing complexity. Because the consequences of their possible failure are so high, it is vital that software systems should exhibit a trustworthy behavior.
Trustworthiness is a major issue when people and organizations are faced with the selection and the adoption of new software. Although some ad-hoc methods have been proposed (see for instance OpenBQR, OpenBRR and QSOS), there is not yet general agreement about the software characteristics contributing to its trustworthiness.
Therefore, this work focuses on defining an adequate notion of trustworthiness of Open Source Software products and artifacts and identifying a number of factors that influence it to provide both developers and users with an instrument that guides them when deciding whether a given program (or library or other piece of software) is “good enough” and can be trusted in order to be used in an industrial or professional context.
More details on www.taibi.it
Open source software development refers to software with source code that is made available to the public with a license that allows users and developers to study, change, and improve the design of the software. The document outlines the history and rise of open source development, comparing it to the traditional closed source model. It describes how open source works through a community-based development process and lists some key advantages like customizability and lower costs compared to proprietary software. Examples of popular open source applications, operating systems, and programming languages are provided.
Have you ever used an open source project? Of course you have, but have you made any contributions yourself? Filed a bug report? Submitted a patch? Have you ever started your own OSS project, or taken a closed/private project public? What licenses should you use? How do you manage contributions? How do you encourage contributors and get work done? In this talk we'll go over the basics of OSS: how to get involved, how to start a project, how to manage contributions. We'll discuss project lifecycles, legal CYA tips, and how to keep projects moving. You'll see the inner workings of real OSS projects, and learn how to be a better OSS user and producer.
Presented at Jfokus 2015
Guy Martin, Senior Strategist for Samsung's Open Source Group, and Shawn Briscoe, Director of Open Source Strategic Services at Black Duck Software, present on how to incorporate open source as an element of your corporate strategy, focusing on practical advice, as well as using Samsung's open source group as a case study for how to begin to shift your company's culture to be more accepting of not only consuming, but contributing to open source communities.
"IBMs Open Source Strategy" by Adam Jollans @ eLiberatica 2009eLiberatica
This is a presentation held at eLiberatica 2009.
http://www.eliberatica.ro/2009/
One of the biggest events of its kind in Eastern Europe, eLiberatica brings community leaders from around the world to discuss about the hottest topics in FLOSS movement, demonstrating the advantages of adopting, using and developing Open Source and Free Software solutions.
The eLiberatica organizational committee together with our speakers and guests, have graciously allowed media representatives and all attendees to photograph, videotape and otherwise record their sessions, on the condition that the photos, videos and recordings are licensed under the Creative Commons Share-Alike 3.0 License.
Your company is using open source, even if you don’t know it. On average, enterprise organizations are utilizing 30% open source within their code bases, and industry leaders often report up to 80% of their software is open source. More importantly, they treat open source as a strategic asset, deliberately investing in open source as a brand differentiator and as a means of thwarting the competition, getting to market faster, and attracting the best talent.
Does your company have an open source strategy? Now is the time to ask this question, because more than likely your competitors do.
This 2014 All Things Open presentation by Samsung's Guy Martin and Black Duck Software's Shawn Briscoe, covers:
- Key dimensions of a comprehensive open source strategy
- Important business issues and intelligent decisioning
- How to mitigate legal and operational risk
- The value of aligning open source stakeholders towards the larger mission of corporate success
- An understanding of the role community dynamics play in a successful initiative
- Samsung – a real world case study
[heavy content] This guide explains how to make proper use of different software forms. Particularly, the guide stresses that open source software is an essential part of software development ecosystem. It outlines its evolutionary role and challenges that are faced by the software industry. The guide should help IT managers to build sound software strategies. It also signals where are growth points for a forward looking and proactive participation in the technology community.
Open Source Licenses / A presentation By Dr. Kalyan C Kankanala
Contact Us for Intellectual Property Services
BananaIP Counsels
Regd Office
No.40,3rd Main Road,JC Industrial Estate,
Kanakapura Road,Bangalore – 560 062.
Email: contact@bananaip.com
Telephone: +91-80-26860414 /24/34
Open Innovation and Opensource SoftwarePradyot Sahu
The document discusses open innovation and open source software. Open innovation involves using innovations created by others through processes, products, or knowledge. It is characterized by purposeful knowledge inflows and outflows, organic growth of innovation, and reliance on outside innovators. Open source software development is a form of open innovation where the intellectual property is openly available and projects involve collaboration. However, open innovation does not always involve making internal components openly available as with systems like IBM PCs.
There are hundreds of open source licenses. Most developers don't take the time to read or understand them, but can you continue to ignore them? We have seen a rise in litigation around open source license over the last 10 years. And, in the last 12 months we have seen the first examples of OSS copyright trolls that are taking developers to court in an attempt to monetize GPL violations.
This presentation covers: How OSS licenses are enforced;
What are the main types of OSS licenses; How to identify them;
and what steps you need to take to ensure you are complying.
We cover use case scenarios and do a "deep dive" on the most used licenses today and how to understand them
Fundamentals of Free and Open Source SoftwareRoss Gardler
Introduction to the OSS Watch Business
and Sustainability Models Around Free and Open Source Software. this presentation doesn't deal with the business models, it introduces FOSS and the key licence types.
GNU GPL, LGPL, Apache licence Types and DifferencesIresha Rubasinghe
The document discusses various open source software licenses including the GNU GPL, LGPL, and MsPL. It compares the different versions and terms of these licenses and provides examples of business models for open source software such as dual licensing and third party support services. The last section addresses combining open source license types and how some like the GPL and LGPL are compatible while others like different GPL versions may not be.
The document discusses how to properly license open source software to avoid legal issues. It recommends: 1) picking the right license for your project; 2) including attribution, license notices, and the full text of the license in your source code; and 3) using a contributor license agreement to assign copyrights of contributions to the project owner. Failure to follow proper licensing can result in losing control of your code, patents, trade secrets or even your company to legal issues. The presentation provides tips and examples of how to properly implement licensing.
Introduction to Open Source Hardware, OSHWA and Open Hardware SummitDrew Fustini
The document provides an overview of open source hardware, including definitions of open source, examples like Arduino, required documentation for electronics projects, licenses, and resources like the Open Hardware Summit and Open Source Hardware Association. It discusses open hardware principles, certification, and the use of Linux on open hardware boards and single-board computers.
"Open Source licensing and software quality" by Monty Michael Widenius @ eLib...eLiberatica
This is a presentation held at eLiberatica 2009.
http://www.eliberatica.ro/2009/
One of the biggest events of its kind in Eastern Europe, eLiberatica brings community leaders from around the world to discuss about the hottest topics in FLOSS movement, demonstrating the advantages of adopting, using and developing Open Source and Free Software solutions.
The eLiberatica organizational committee together with our speakers and guests, have graciously allowed media representatives and all attendees to photograph, videotape and otherwise record their sessions, on the condition that the photos, videos and recordings are licensed under the Creative Commons Share-Alike 3.0 License.
Open Source as IT and Business StrategyKarim Baïna
Open source as IT and Business Strategy for emergent countries. Morocco situation with regards to open source. How an emergent country may benefit from adpting open source software. How an emergent country can be prapared to oss transitiion. Examples of developed countries and emergent countries having adopted open source software within their IT strategy. Business models of open source.
Transforming IT with an Open Source StrategyInnoTech
This document summarizes several case studies of companies that implemented Hortonworks' open data platform solutions. It describes Mercy Medical System's goal of creating a single patient record across its health system and how Hortonworks helped achieve that. It also outlines how Progressive Insurance uses Hortonworks to ingest sensor data to power usage-based insurance, and how Western Digital uses it to gain insights from manufacturing test data to improve product quality. Finally, it discusses a home improvement chain's need for a customer golden record and targeted marketing, which Hortonworks enabled.
symfony: An Open-Source Framework for Professionals (PHP Day 2008)Fabien Potencier
This document provides an overview of the symfony open-source framework. It discusses that symfony is a PHP framework created by Sensio based on their 10 years of experience. It was built for professional websites and complex applications. The document outlines key symfony concepts like its use of the MVC pattern and organization into modules. It also highlights symfony's open-source license and documentation as well as its developer community and support offerings.
112 - The Role of Mentoring and Project Characteristics for Onboarding in Ope...ESEM 2014
Context: Onboarding is a process that helps newcomers become integrated members of their organisation. Successful onboarding programs can result in increased performance in conventional organisations, but there is little guidance on how to onboard new developers in Open Source Software (OSS) projects. Goal: In this study, we examine how mentoring and project characteristics influence the effectiveness and effi ciency of the onboarding process. We study a collaboration program involving a total of nine Open Source Software projects and more than 120 students from dfferent universities around the world as part of Facebook’s Education Modernization Program. Method: We use quantitative measurements of source code repositories, issue tracking systems, and discussion fora to examine how newcomers become contributing members of their OSS projects. Results: We found that developers receiving deliberate onboarding support through mentoring were more active at an earlier stage than developers entering projects through conventional means. Also, we found that project size and lifetime influenced on- boarding. Conclusion: Empirical decision support can contribute to a more effective onboarding process in OSS projects. Mentor sup- port in critical stages can accelerate the process, but project maturity is also a significant factor that increases the effect of onboarding.
Defining an Open Source Software Trustworthiness Model Davide Taibi
This presentation show the results of my PhD thesis.
Modern society depends on large-scale software systems of astonishing complexity. Because the consequences of their possible failure are so high, it is vital that software systems should exhibit a trustworthy behavior.
Trustworthiness is a major issue when people and organizations are faced with the selection and the adoption of new software. Although some ad-hoc methods have been proposed (see for instance OpenBQR, OpenBRR and QSOS), there is not yet general agreement about the software characteristics contributing to its trustworthiness.
Therefore, this work focuses on defining an adequate notion of trustworthiness of Open Source Software products and artifacts and identifying a number of factors that influence it to provide both developers and users with an instrument that guides them when deciding whether a given program (or library or other piece of software) is “good enough” and can be trusted in order to be used in an industrial or professional context.
More details on www.taibi.it
Open source software development refers to software with source code that is made available to the public with a license that allows users and developers to study, change, and improve the design of the software. The document outlines the history and rise of open source development, comparing it to the traditional closed source model. It describes how open source works through a community-based development process and lists some key advantages like customizability and lower costs compared to proprietary software. Examples of popular open source applications, operating systems, and programming languages are provided.
Have you ever used an open source project? Of course you have, but have you made any contributions yourself? Filed a bug report? Submitted a patch? Have you ever started your own OSS project, or taken a closed/private project public? What licenses should you use? How do you manage contributions? How do you encourage contributors and get work done? In this talk we'll go over the basics of OSS: how to get involved, how to start a project, how to manage contributions. We'll discuss project lifecycles, legal CYA tips, and how to keep projects moving. You'll see the inner workings of real OSS projects, and learn how to be a better OSS user and producer.
Presented at Jfokus 2015
Guy Martin, Senior Strategist for Samsung's Open Source Group, and Shawn Briscoe, Director of Open Source Strategic Services at Black Duck Software, present on how to incorporate open source as an element of your corporate strategy, focusing on practical advice, as well as using Samsung's open source group as a case study for how to begin to shift your company's culture to be more accepting of not only consuming, but contributing to open source communities.
"IBMs Open Source Strategy" by Adam Jollans @ eLiberatica 2009eLiberatica
This is a presentation held at eLiberatica 2009.
http://www.eliberatica.ro/2009/
One of the biggest events of its kind in Eastern Europe, eLiberatica brings community leaders from around the world to discuss about the hottest topics in FLOSS movement, demonstrating the advantages of adopting, using and developing Open Source and Free Software solutions.
The eLiberatica organizational committee together with our speakers and guests, have graciously allowed media representatives and all attendees to photograph, videotape and otherwise record their sessions, on the condition that the photos, videos and recordings are licensed under the Creative Commons Share-Alike 3.0 License.
Your company is using open source, even if you don’t know it. On average, enterprise organizations are utilizing 30% open source within their code bases, and industry leaders often report up to 80% of their software is open source. More importantly, they treat open source as a strategic asset, deliberately investing in open source as a brand differentiator and as a means of thwarting the competition, getting to market faster, and attracting the best talent.
Does your company have an open source strategy? Now is the time to ask this question, because more than likely your competitors do.
This 2014 All Things Open presentation by Samsung's Guy Martin and Black Duck Software's Shawn Briscoe, covers:
- Key dimensions of a comprehensive open source strategy
- Important business issues and intelligent decisioning
- How to mitigate legal and operational risk
- The value of aligning open source stakeholders towards the larger mission of corporate success
- An understanding of the role community dynamics play in a successful initiative
- Samsung – a real world case study
[heavy content] This guide explains how to make proper use of different software forms. Particularly, the guide stresses that open source software is an essential part of software development ecosystem. It outlines its evolutionary role and challenges that are faced by the software industry. The guide should help IT managers to build sound software strategies. It also signals where are growth points for a forward looking and proactive participation in the technology community.
10 Reasons To Use Open Source Software-Defined NetworkingVala Afshar
The document discusses reasons to use open source software-defined networking (SDN), including that open source code has better quality than proprietary code according to surveys. It also notes that open source allows for rapid innovation, greater security as transparency improves code, and participation in a collaborative development community. Additional benefits mentioned are greater choice, interoperability, and lower costs compared to proprietary solutions.
This document provides an overview of open source software and its adoption in education. It discusses the history and key people involved in open source software development like Richard Stallman and Linus Torvalds. The document argues that open source software provides benefits to education like cost savings, collaboration, and allowing older hardware to run new software. It recommends that schools adopt open source software for academic and financial reasons.
This document summarizes legal and other issues related to the use of open source software. It defines key terms like proprietary software, open source software, and freeware. It discusses and compares licensing terms for proprietary vs open source software. It notes advantages and disadvantages of each for issues like cost, modifications, standards, and support. It provides guidance on sharing and procuring software following best value practices in Massachusetts.
This document summarizes strategies and considerations for adopting open source software at NASA. It discusses areas like licensing, redistribution, open source ecosystems, community involvement versus help desk support models, intellectual property, and responsiveness. The document advocates for building communities around NASA's open source projects to encourage contributions from multiple parties.
A seminar presentation on Open Source by Ritwick Halder - a computer science engineering student at Academy Of Technology, West Bengal, India - 2013
Personal Website - www.ritwickhalder.com
This document discusses open source tools for big data analytics. It introduces Hadoop, HDFS, MapReduce, HBase, and Hive as common tools for working with large and diverse datasets. It provides overviews of what each tool is used for, its architecture and components. Examples are given around processing log and word count data using these tools. The document also discusses using Pentaho Kettle for ETL and business intelligence projects with big data.
We’re all trying to find that idea or spark that will turn a good project into a great project. Creativity plays a huge role in the outcome of our work. Harnessing the power of collaboration and open source, we can make great strides towards excellence. Not just for designers, this talk can be applicable to many different roles – even development. In this talk, Seasoned Creative Director Sara Cannon is going to share some secrets about creative methodology, collaboration, and the strong role that open source can play in our work.
The impact of innovation on travel and tourism industries (World Travel Marke...Brian Solis
From the impact of Pokemon Go on Silicon Valley to artificial intelligence, futurist Brian Solis talks to Mathew Parsons of World Travel Market about the future of travel, tourism and hospitality.
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.
The document discusses the history and development of open licensing and copyright. It covers early copyright laws from the 1700s, the creation of various open licenses like the GPL and Creative Commons licenses in the late 20th century, and debates around balancing open sharing of content with author rights and commercial interests. Key events discussed include the establishment of copyright, the free software movement launched by Richard Stallman, and the growth of Creative Commons which now has over 100 million works licensed under its schemes.
This document provides an overview of Ortus Solutions, an established software development firm that specializes in mobile and web application design and development. It has created over 250 web development tools and is an open source software publisher. The document discusses open source vs proprietary software and the history of open source adoption. It also covers various open source licenses like MIT, Apache 2.0, GPL, LGPL, MPL and their differences. Finally, it discusses strategies for monetizing open source software through services, subscriptions and commercial versions.
This document discusses open source software and open source business models. It begins with an introduction to open source software, including definitions and licenses. It notes the growth of open source and benefits such as lower costs. However, it also identifies challenges for open source like the lack of a "whole product" and professional services. The document then analyzes the differences between proprietary and open source business models. It proposes crossing the adoption chasm by focusing on the "whole product" and targeting customer needs rather than just the software. Overcoming barriers will also help drive more widespread open source adoption.
The document summarizes a debate on open source versus proprietary software. It discusses definitions of open source software, popular open source licenses, and advantages of open source such as customizability, security, and lower costs. Open source is gaining adoption in government and enterprise due to benefits like avoiding vendor lock-in, lower costs, and higher quality from community contributions. Surveys find increasing enterprise adoption rates, with over 50% of new software to be open source in the next 5 years. Microsoft is also increasingly supporting open source.
This document provides information about open source software including definitions, history, licenses, examples of leading open source projects, and comparisons to other software types. It discusses the open standard requirements for technologies to be considered open source and defines the key aspects of open source licenses including free redistribution, availability of source code, ability to create derivative works, and non-discrimination terms. The document also outlines some pros and cons of the open source model.
This document discusses open source software. It defines open source as software with source code that is freely available and may be redistributed and modified. The criteria for open source include availability of source code, allowing derivatives, free redistribution, and non-discriminatory licensing. Some advantages are availability of source code to learn from, freedom from vendor lock-in, ability to fix bugs and customize. Examples given are operating systems like Linux and Android as well as applications like Firefox, LibreOffice, and Blender. Common open source licenses are discussed including the GPL and LGPL.
This presentation introduces open source software and aims to shed light on why you should care. We’ll highlight what you can or can’t do with it (licensing), and the pros/cons for businesses and individuals.
This document provides an introduction to open source software. It discusses the history of open source beginning with software sharing at MIT in the 1970s. It describes Richard Stallman founding the Free Software Movement in response to proprietary software taking over. The Open Source movement began in the late 1990s. Today, open source software is widely adopted due to benefits like community support, transparency, reliability, and lower costs compared to proprietary software.
The document discusses open source software, including its history, definitions, common licenses, and popular packages. It provides facts about open source usage, outlines how Richard Stallman and Linus Torvalds helped establish open source concepts. The benefits are listed as cost savings, increased users, scalability, longevity, and innovation due to collaboration. Popular licenses mentioned are GPL, LGPL, BSD and Apache. Development tools highlighted are Linux, Android, MySQL, PHP and Python.
5 Steps to Ensuring Compliance in the Software Supply Chain: The Harman Case ...Black Duck by Synopsys
Harman designs, manufactures and markets premier audio, visual, infotainment and integrated control solutions for the automotive, consumer and professional markets.
One of Harman’s biggest challenges when supplying its systems is ensuring it can prove its code complies with applicable license terms. The code must also be free of security and quality risks that could impact the integrity of the finished products.
But what happens when the code is open source? While software developed in-house can be closely monitored, software that comes in through third parties is harder to track. How can Harman accurately report on operational and legal risks for components and projects it didn’t develop?
Join this presentation from Alyssa Harvey Dawson, Vice President Legal, Global Intellectual Property at Harman, and Black Duck Software, covers:
- Current open source trends
- An in-depth review of popular licenses (including GPL)
- Harman's take on open source compliance
- The impact of security and technical risks beyond compliance
This document provides an overview of open source software including its definition, history, freedoms, development model, licenses, security considerations, and advantages/disadvantages. Open source software gives users the freedom to use, modify, and share the software. It originated in the 1980s with Richard Stallman's GNU project. There are various business models for open source including support/services. Popular licenses include the GPL, MPL, Apache, and BSD licenses which have different terms regarding modifications and redistribution. While open source is not inherently more secure, its transparency and community review can improve security.
Open Source software can be found everywhere, from WiFi routers to the largest web sites on the Internet. This presentation looks at how it all got started and what it can mean for you.
The document defines open source software and provides examples. Open source refers to software whose source code is publicly available and can be modified and shared by anyone. Key advantages are the availability of source code, quality from community involvement, and lower costs compared to proprietary software. Popular open source applications, operating systems, and programming languages are listed as examples, including Android, Linux, PHP, and Python. The document also discusses open source development and licensing models.
The document provides an introduction to free and open source software (FOSS). It discusses the history and definitions of free software and open source software. It compares proprietary software to FOSS and outlines some of the key benefits of FOSS like zero acquisition costs, freedom to modify and distribute, and avoiding vendor lock-in. The document also gives examples of popular FOSS technologies and discusses career opportunities in FOSS.
Open source software is growing, especially in IoT, but there is little understanding of license obligations. This presentation provides best practices for using open source software safely and effectively. It discusses open source licenses including GPL, LGPL, MIT and their terms. It emphasizes the importance of compliance to avoid liability issues seen in court cases. Developers must understand which licenses are acceptable and how to identify and address license requirements for all code used.
The document provides an overview of a 3-day open source workshop being conducted by Luciano Resende from the Apache Software Foundation. Day 1 will cover topics on open source, licenses, communities and how to get involved in Apache projects. Day 2 focuses on hands-on development, setting up environments and tools. Day 3 is about mentoring expectations and working on project proposals. The workshop aims to educate participants and help them get involved in open source.
Open source refers to software whose source code is publicly accessible and can be modified. The open source movement began in the 1980s. Open source provides benefits to businesses like security, quality, customization, and cost savings. It allows for collaboration and access to source code. Open source software is different from proprietary software in that its code is open while proprietary code is closed. Open source benefits businesses through security, quality, freedom, customization, flexibility, support options, and auditability while reducing costs. Though starting with software, open source now represents a set of collaborative values.
The document discusses open source software and how companies can generate revenue from open source business models without traditional licensing fees. It describes several common business models including support and services, loss leaders to promote other products, customization services, and brand licensing. The document also discusses other motives for companies beyond direct revenue, such as using the free infrastructure of open source development and indirect revenues from related products. It notes that programmers are motivated by technological and learning benefits from the feedback of large, open communities rather than direct economic benefits from companies.
Similar to The Hitchhikers' Guide to Free and Open Source Software Development (CompCon 2013) (20)
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
A Comprehensive Guide to DeFi Development Services in 2024Intelisync
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...alexjohnson7307
Predictive maintenance is a proactive approach that anticipates equipment failures before they happen. At the forefront of this innovative strategy is Artificial Intelligence (AI), which brings unprecedented precision and efficiency. AI in predictive maintenance is transforming industries by reducing downtime, minimizing costs, and enhancing productivity.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
7. PUBLIC CODE PRESENCE IS
ATTRACTIVE TO
POTENTIAL
EMPLOYERS
support companies can hire what they see …
Hardware vendors have a big market for FOSS devs so that foss will work on their devices.
8. PUBLIC CODE PRESENCE IS
THE BEST CV EVA
Bitbucket
Gitorious
CloudForge
Google Code
CodePlex
Launchpad
GitHub
SourceForge
23. WHY?
“DO” OPEN SOURCE
SKILL UP
Try out new ideas.
Try out new technology.
Try out development, unstable versions.
Do things you don’t do “during the day”.
It’s exhausting
27. QUALITY
“If you have enough
eyeballs all bugs
are shallow.”
Linus’ Law
(actually pre-dates him)
28. CHOICE AND TRUST
No need to trust software vendor.
Choice to fix yourself.
Right to fork if disagree.
Can contribute.
It’s healthy to question your own work!
It’s healthy to freely collaborate!
PRACTICAL terms
57. AUTOMATICALLY GRANTS AUTHOR
EXCLUSIVELY RIGHT TO:
To produce copies or reproductions to sell or distribute.
Create derivative works.
To perform or display the work publicly;
To transmit, import or export the work.
This is the essence of why licenses matter.
58. AUTOMATICALLY GRANTS AUTHOR
EXCLUSIVELY RIGHT TO:
To produce copies or reproductions to sell or distribute.
Create derivative works.
To perform or display the work publicly;
To transmit, import or export the work.
NO ONE ELSE CAN DO THESE THINGS
WITHOUT THE AUTHOR’S PERMISSION
This is the essence of why licenses matter.
59. AUTOMATICALLY GRANTS AUTHOR
EXCLUSIVELY RIGHT TO:
To produce copies or reproductions to sell or distribute.
Create derivative works.
To perform or display the work publicly;
To transmit, import or export the work.
NO ONE ELSE CAN DO THESE THINGS
WITHOUT THE AUTHOR’S PERMISSION
If they do, the author can sue.
This is the essence of why licenses matter.
61. ORIGINAL SOFTWARE
FREEDOMS (~1976)
* The freedom to run the program, for any purpose.
* The freedom to study how the program works, and adapt
it to your needs.
* The freedom to redistribute.
* The freedom to improve the program, and release your
improvements (and modified versions in general)
Access to the source code is a precondition.
(obviously)
62.
63. OPEN SOURCE DEFINITION
1. Free Redistribution
2. Source Code
3. Derived Works
4. Integrity of The Author's Source Code
5. No Discrimination Against Persons or Groups
Things that are explicitly stated.
64. OPEN SOURCE DEFINITION
1. Free Redistribution
~ as in beer -- no royalties or fees
2. Source Code
3. Derived Works
4. Integrity of The Author's Source Code
5. No Discrimination Against Persons or Groups
Things that are explicitly stated.
65. OPEN SOURCE DEFINITION
1. Free Redistribution
~ as in beer -- no royalties or fees
2. Source Code
~ not obfuscated or require preprocessor, translator, etc
3. Derived Works
4. Integrity of The Author's Source Code
5. No Discrimination Against Persons or Groups
Things that are explicitly stated.
66. OPEN SOURCE DEFINITION
1. Free Redistribution
~ as in beer -- no royalties or fees
2. Source Code
~ not obfuscated or require preprocessor, translator, etc
3. Derived Works
~ can be remixed
4. Integrity of The Author's Source Code
5. No Discrimination Against Persons or Groups
Things that are explicitly stated.
67. OPEN SOURCE DEFINITION
1. Free Redistribution
~ as in beer -- no royalties or fees
2. Source Code
~ not obfuscated or require preprocessor, translator, etc
3. Derived Works
~ can be remixed
4. Integrity of The Author's Source Code
~ rename your version
5. No Discrimination Against Persons or Groups
Things that are explicitly stated.
68. OPEN SOURCE DEFINITION
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
Need to be specified because they’ve been challenged
69. OPEN SOURCE DEFINITION
6. No Discrimination Against Fields of Endeavor
~ eg. commercial use or “values” (genetic research)
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
Need to be specified because they’ve been challenged
70. OPEN SOURCE DEFINITION
6. No Discrimination Against Fields of Endeavor
~ eg. commercial use or “values” (genetic research)
7. Distribution of License
~ applies to next person down, but not next after that
8. License Must Not Be Specific to a Product
9. License Must Not Restrict Other Software
10. License Must Be Technology-Neutral
Need to be specified because they’ve been challenged
71. OPEN SOURCE DEFINITION
6. No Discrimination Against Fields of Endeavor
~ eg. commercial use or “values” (genetic research)
7. Distribution of License
~ applies to next person down, but not next after that
8. License Must Not Be Specific to a Product
... except if being repackaged and redistributed
9. License Must Not Restrict Other Software
10. License Must Be Technology-Neutral
Need to be specified because they’ve been challenged
72. OPEN SOURCE DEFINITION
6. No Discrimination Against Fields of Endeavor
~ eg. commercial use or “values” (genetic research)
7. Distribution of License
~ applies to next person down, but not next after that
8. License Must Not Be Specific to a Product
... except if being repackaged and redistributed
9. License Must Not Restrict Other Software
10. License Must Be Technology-Neutral
~ platform or “style of interface”
Need to be specified because they’ve been challenged
75. LIABILITY
Giving away for free (as in beer)
does not exempt
from being sued.
“This program comes with
ABSOLUTELY NO WARRANTY”
lifesaving
landing aircraft
76. OPEN SOURCE
PHILOSOPHISING
Traditional FOSS projects have
strong technical focus
and tend to avoid philosophy.
There are dedicated channels for
talking about FOSS philosophy and principles.
In more modern projects there is a resurgence in
interest if you learn some background.
Aaron Schwartz
86. BUT SRSLY ...
Completely PRIVATE
Product
v.
INDIVIDUAL
Completely FREE
community that emphasises the individual over the company
vs.
company presents a facade
87. One of most important messages of this talk!
Beautiful bouquet that is humanity
89. COMMUNITY CULTURE
IS NOT SCIENCE
You can not independently derive this stuff.
... and no one expects you to.
Do your research and listen.
Follow the precedent.
93. PROJECT VARIABLES
• What’s
its scope?
• What’s
• Technology
its profile?
• How
big is it?
• How
old is it?
• Where
• How
in its lifecycle it is?
active is it?
Andrew Tridgell says: spend a couple of weekends or whatever
94. PROJECT VARIABLES
• Technology
• What’s
its scope?
• Who?
• What’s
its profile?
• How
well organised is it?
• How
big is it?
• How
is it structured?
• How
old is it?
• How
are decisions made?
• Where
• How
does it communicate? • How active is it?
in its lifecycle it is?
Andrew Tridgell says: spend a couple of weekends or whatever
96. PROJECT VARIABLES
What’s its scope?
[Linux Kernel .. .. some niche script]
What’s its profile?
[Python .. .. some widget]
97. PROJECT VARIABLES
How old is it?
FOSS Projects are hard to kill.
Where in its lifecycle it is?
[Alpha .. .. Established]
Where in its story arc it is?
[Surging .. Stable .. Dying]
samba died twice
dead cat bounce
98. PROJECT VARIABLES
How big is the codebase?
How big is the program/application?
[Twitter .. .. ]
Sometime big codebase on small application
is a good thing.
99. PROJECT VARIABLES
How big is the community?
What kind of people are in the community?
[technical, organisational, social, experimental ...]
103. PROJECT VARIABLES
How active is it?
[17K emails/month .. .. couple of patches/year]
Faster moving is less tolerant.
Bigger can be more tolerant.
104. WELCOMING COMMITTEE
Projects might have someone whose role is
to guide new people.
Apache have a whole system.
The project leader might give you
all the time in the world
for a brand new project.
There will probably be nothing at all.
this week, we found a big in plug in
made a patch
it was pushed and released in about 15 minutes
110. PROJECT GOVERNANCE
Formal
Constitution
Office holders, Board or Steering committee
Annual election
(Debian; Gnome)
Not-for-profit “Software Foundation”
(Apache SF, Python SF, Django SF)
Usually happens when big enough to involve
money and lawyers.
Office holders, “official” membership
common pattern
111. PROJECT GOVERNANCE
Serious v. Not (silly)
Vast majority of projects are side-projects.
Generally side-projects are less serious
but not necessarily.
Is someone basing their career on it?
112. ROLES
There is usually identifiable author or leader.
Is there an identifiable team?
What roles are there?
What roles aren’t there?
113. ROLES
BDFL
Benevolent Dictator/s For Life
More commonly used in this era.
Usually original author/s.
Though there are exceptions.
Dictates final decisions, arbitrage and ends disputes.
Project leader for so long
115. ROLES
System Admin (servers, etc)
Website
Artwork
Licenses
Answering Questions
Newb wrangling
(we were all newbs once, we’re all newbs about most things ever, it’s just a phase)
Karen/Russ, django users
116. GETTING
INVOLVED
How many people use version control regularly/proficiently?
101 stuff ... most of are self-taught in most areas, worth glossing over.
117. START SMALL
A lot of people’s FOSS careers
start with a
one character
patch.
(particularly to big, old, established projects)
You don’t have to “prove” your mad-coding-skillz
or change the world in your first commit,
moreover you certainly shouldn’t.
If you know everything else I’m going to talk about here, but still aren’t involved:
Particularly to big, old, established projects
Goes against our instinct
118. START SMALL
Projects hate:
Big, unexplained patches
from people unknown to the community.
Not impressive.
Big old projects may dismiss out-of-hand.
“dropping bombs”
“drive by shootings”
Even if it’s good code -- it’s just not done that way.
It’s got to be consumable by the project.
122. WHAT IS
VERSION CONTROL?
Writing code is easy,
constructing programs is hard.
Many people
working on same codebase is hard.
Solution: take small, logical, incremental steps.
in the form of ...
123. ALWAYS SMALL
Always take the time to
break up your patch into the
smallest, logical unit.
Easier to understand for everyone
(committer, future-you).
Easier to revert.
Rule of thumb: what you may need to revert.
125. DIFF/PATCH
The tiny step is called a: patch
Small, logical, incremental steps.
Official terms: diff and patch.
These were the original tools that were used.
Atomic unit of code development.
Patch originally written by Larry Wall
Tapes, TAR in the beginning,
actually learning SCM takes years
126. DIFF/PATCH
Put code changes into standardised format.
Standard is: “unified format”
(or “unidiff” or “-u”)
$ diff -u ...
Atomic unit of code development.
Tapes, TAR in the beginning,
actually learning SCM takes years
130. UNIDIFF
A PATCH! any unidiff scm will be able to “APPLY” this
you can write these by hand if you want
can be reversed (or “reverted”)
some examples without original source
136. The patch/s are then “sent*” to the project.
*what this means varies.
Atomic unit of code development.
Tapes, TAR in the beginning,
actually learning SCM takes years
137. COMMITTING/INTEGRATING
Code change is then
committed or integrated
in to a version of project.
Though it’s normal for patches to be rejected.
Your patch might directly conflict with someone else’s work.
this is known as a merge-conflict
and usually needs human arbitrage to fix.
139. SEND/MERGE/COMMIT/
PUSH/PULL-REQUEST
... sent* to the project ...
This is where projects become so divergent
own research needs to be done to on this process.
A lot of project use multiple integration methods.
Atomic unit of code development.
Tapes, TAR in the beginning,
actually learning SCM takes years
140. PATCH SUBMISSION:
LINUX KERNEL EXAMPLE
Very strong rules.
Very clear guidelines.
https://www.kernel.org/doc/Documentation/
SubmittingPatches
5,000 word piece of documentation
which is strongly adhered to.
141. PATCH SUBMISSION:
LINUX KERNEL EXAMPLE
Patches to Linux Kernel are submitted by email.
They get a lot of email:
lkml.org/lkml/2013/
20-25 emails an hour, depending where in the world
150. CENTRALISED
VERSION CONTROL
FIRST GENERATION SCM
+
-
Provides development history
Manages files individually
Only one person editing at a time
No merge capability
eg, SCCS (1972), RCS (1982 free and more evolved)
rcs 1982
151. CENTRALISED
VERSION CONTROL
CVS (CONCURRENT VERSIONS SYSTEM)
+
+
-
Parallel development
Merge & conflict resolution (based on diff/patch)
Poor rename and directory support
Poor branch merging
Most operations require contacting centralised server
Dominated FOSS 1991 to 2005.
Use can still be found.
1990
152. CENTRALISED
VERSION CONTROL
SUBVERSION (SVN)
+
+
-
‘CVS done right’
Project-wide revisions
Each developer has ‘checkout’
Most meta-data is only stored on central server
Committing require contacting central server
Very commonly used before new generation.
Still commonly used.
153. WHAT IS SOURCE CODE
MANAGEMENT (SCM)?
Where is your MASTER codebase repository?
154. WHAT IS SOURCE CODE
MANAGEMENT (SCM)?
Where is your MASTER codebase repository?
Since early 2000s
DISTRIBUTED
Everyone gets a ‘clone’:
+ entire codebase
+ entire revision history
159. DISTRIBUTED
VERSION CONTROL
BAZAAR (BZ)
MERCURIAL (HG)
DARCS
MONOTONE (peer-to-peer)
GIT
Since great Distributed Version Control wars of ~2005
started in the 90s, blew out ’02-05 when linux switched to not GIT (bitkeeper)
160. Currently has a lot of support and momentum.
People say it’s complicated.
TAKE CARE MENTALLY VISUALISING STATE OF CODE
necessarily complicated!
install git
161. WHAT IS A GIT REPOSITORY?
Any file tree with the special /.git directory
~ delete and ceases to be
~ can put anywhere and it will try and figure out
162. WHAT FILES ARE IN A
GIT REPOSITORY?
Explicitly add and rm files to/from repository
can put in any dir, but won’t know until you tell it.
163. WHAT FILES ARE IN A
GIT REPOSITORY?
Explicitly add and rm files to/from repository
Be specific:
$ git add hello.txt
Or general:
$ git add .
can put in any dir, but won’t know until you tell it.
164. WHAT FILES ARE IN A
GIT REPOSITORY?
You can explicitly tell git to ignore the existence of certain files
listing files to be ignored in:
.gitignore
This can be per directory.
Gotcha: .gitignore won’t work on files
you’ve already added.
166. GIT CLONE
Find an open source repository.
~ all revision history
~ entire working codebase
167. GIT CLONE
Find an open source repository.
$ git clone https://github.com/jquery/jquery.git
~ all revision history
~ entire working codebase
168. GIT CLONE
Find an open source repository.
$ git clone https://github.com/jquery/jquery.git
~ all revision history
~ entire working codebase
169. GIT CLONE
Find an open source repository.
$ git clone https://github.com/jquery/jquery.git
~ all revision history
~ entire working codebase
170. GIT CLONE
Find an open source repository.
$ git clone https://github.com/jquery/jquery.git
~ all revision history
~ entire working codebase
171. GIT CLONE
Find an open source repository.
$ git clone https://github.com/jquery/jquery.git
The the code is yours. All yours.
~ all revision history
~ entire working codebase
172. MAKE CHANGES
FORK
If you’re going to make changes then fork the project.
Only make changes to your own tree.
Forking used to be an anathema.
181. GIT WORKFLOW
1. Make code changes.
Study your newly created patches/hunks.
(debug, debug, check, check, proof, proof)
2. “Stage” patches/hunks
(using $ git add or GUI tool)
3. “Commit” staged changes to the repository.
182. GIT WORKFLOW
1. Make code changes.
Study your newly created patches/hunks.
(debug, debug, check, check, proof, proof)
2. “Stage” patches/hunks
(using $ git add or GUI tool)
3. “Commit” staged changes to the repository.
(using $ git commit -m “handy mandatory message”)
186. VERSION CONTROL
BASICS
Rule #0:
Assume everything you commit is
FINAL and FOREVER
Rule #1:
NEVER commit your PASSWORDS
or any other sensitive or personal settings or information.
187. VERSION CONTROL
BASICS
Rule #:
Don’t commit buggy code.
Way to burn trust and respect.
Rule #:
Atomic changes. That is: SMALL, logical changes.
Break up feature in to a bunch of smaller patches.
Drive-by patches are universally despised.
whole weekend
188. VERSION CONTROL
BASICS
Rule #:
Explain yourself.
Be terse, clear and explain why change is necessary.
Rule #:
The committer’s time is probably more valuable than yours.
Being fewer of them it’s probably true.
196. COMMITS/PULL REQUESTS
Committed patches
may then be “pulled” in to a version of project.
They usually don’t do this automatically.
You ask the “upstream” to accept your
commit using a pull-request
197. COMMITS/PULL REQUESTS
Committed patches
may then be “pulled” in to a version of project.
They usually don’t do this automatically.
You ask the “upstream” to accept your
commit using a pull-request
pull-requests are regularly not accepted.
(it’s not personal).
198.
199.
200. CONTRIBUTING
“STYLE”
Learn the “style” of the existing project.
Phrasing, structure, etc.
There will probably be rules. Follow them. eg: PEP8
If in doubt: copy
Don’t make up a new style, you’ll look like a fool -- ASK!
NOW you have TOOLS to COMMUNICATE and CONTRIBUTE
TOO BIG: RKM learnt in weekend, core within a month or two.
But noone on earth doing for linux kernel -- drive by shootings, gotta know you, trust you -LINUXCON LAST WEEK
201. CONTRIBUTING
COMMUNICATE
Shallow and Often
.
NOW you have TOOLS to COMMUNICATE and CONTRIBUTE
TOO BIG: RKM learnt in weekend, core within a month or two.
But noone on earth doing for linux kernel -- drive by shootings, gotta know you, trust you -LINUXCON LAST WEEK
202. CONTRIBUTING
COMMUNICATE
Don’t be out on a limb!
.
NOW you have TOOLS to COMMUNICATE and CONTRIBUTE
TOO BIG: RKM learnt in weekend, core within a month or two.
But noone on earth doing for linux kernel -- drive by shootings, gotta know you, trust you -LINUXCON LAST WEEK
203. SAY
THANK YOU
Occasionally send an email or make a post saying:
“Thanks!”
No matter how big or famous a project,
there’s usually more criticism than thanks.
It’s nice to be grateful :)
205. DON’ T ASK ME
NOW you have TOOLS to COMMUNICATE and CONTRIBUTE
TOO BIG: RKM learnt in weekend, core within a month or two.
But noone on earth doing for linux kernel -- drive by shootings, gotta know you, trust you -LINUXCON LAST WEEK
206. Growing Open Source Seeds
How (Not) To Build An
OSS Community
Kenneth Reitz
* Hello
* Enjoying PyCon? Food Coma?
* Talk about something near & dear: community
Questions?
github.com/kennethreitz
Thanks.
Questions?
@daniellindsley
https://github.com/toastdriven
Running an open source project
209. EXISTING PROJECTS
Do you actually want help?
“My Precious”
Let others in.
Consider the benefits of help!
All the things you no longer have to think about.
210. EXISTING PROJECTS
Think about what needs to be done.
Write a post about how other people can do.
If you want help, be specific.
Explain exactly what and how.
Write a list.
Make tasks and issues.
211. EXISTING PROJECTS
INSTALLATION and DEPENDENCIES
For the love of humanity ...
Ensure it’s possible to compile/install!
er, documentation?
Write it down as you’re doing it.
212. EXISTING PROJECTS
TEST DATA
For the love of humanity ...
Give us something to play with!
JSON, XML, Sqlite3, scripts ... anything ...
213. GOOD LEADERSHIP
Don’t REJECT or REVERT without an explanation.
Contact the contributor before you do it.
Don’t let them find out publicly first.
It’s gutting to have something rejected, but there’s usually
a good reason -- explain it! It makes it OK.
218. EXISTING PROJECTS
BURNOUT
Take time off.
Ignore everything except security issues.
NOW you have TOOLS to COMMUNICATE and CONTRIBUTE
TOO BIG: RKM learnt in weekend, core within a month or two.
But noone on earth doing for linux kernel -- drive by shootings, gotta know you, trust you -LINUXCON LAST WEEK
219. EXISTING PROJECTS
BE NICE
If someone leaves:
Thank, don’t bitch
Don’t bitch about open source project
without contacting owners, reporting bug
(random blog post!)
>> if anyone you know does this call them out on it.
NOW you have TOOLS to COMMUNICATE and CONTRIBUTE
TOO BIG: RKM learnt in weekend, core within a month or two.
But noone on earth doing for linux kernel -- drive by shootings, gotta know you, trust you -LINUXCON LAST WEEK
220. LICENSES
Don’t want to go too deep on licenses.
It’s boring as batshit
If you care, you care a lot.
222. LICENSES
Original samba license:
Copyright (C) Andrew Tridgell 1992.
Permission to use, copy and distribute this software is given to anyone who
wants to, for NON-PROFIT only. You may not charge for this software or any
derivatives of it without first contacting the Author.
223. LICENSES
OSI lists 63 approved licenses, 9 as 'widely used'
GNU lists 81 free software licenses plus 28 non-free licenses
225. LICENSES
GPL V2
pre-GPLv3 (2007)
FOSS Licenses were much simpler.
75%+ projects were GPL.
If you liked a company, you would license as LGPL.
Number of other licenses, notably:
BSD (Berkely)
LGPL:
● Allows linking with proprietary programs
● Also used to avoid inter-project licensing problems
226. LICENSES
GPL V3 (2007)
Written to address:
● Internationalisation and clarification of legal language
● Stronger patent provisions
● Prevention of hardware restrictions (“tivoisation”)
● Optional clauses to aid license interoperability
● DMCA avoidance (“effective technological measure”)
It is a very good license. Arguably too good.
There has been a trend away from GPL.
It would be impossible for apple to comply with the GPLv3 license requirements on iPad and
iPhones unless they license devices' security systems as same.
GPLv3 licensed software will not get in to any app store. full stop.
227. LICENSES
COMPATIBILITY
Probably not fun.
~15% of all repositories had license files
~25% of those have the license only
mentioned in the Readme file
Read more: Armin Ronacher (author of Flask), Late July, 2013
Can tell because people like Apple and Google don’t want a bar of it.
228. LICENSES
POST-GPL
Interesting Times
Most popular: GPL
Apache Software License 2.0 (ASL2)
BSD
(with additional clauses)
(do whatever you like, just don’t sue me, even close source)
MIT
(do whatever you like, just don’t sue me)
229. LICENSES
Mongrel: popular ruby web server
Zed Shaw
Under one of “please don’t sue me” licenses.
Later regretted decision.
Until recently “Twitter” used it (on top of Apache).
230. LICENSE:
ZED SHAW
“Open source to open source,
corporation to corporation.
If you do open source,
you’re my hero and I support you.
If you’re a corporation,
let’s talk business.”
232. TOOLS
Learn to use:
Text Editor
(pick a good one, learn to use it well)
Source Control Management (SCM)
(eg: git)
These take YEARS to learn!
233. TOOLS
Learn to use:
Issue tracker
(not as obvious as it seems)
IRC
Mailing-lists
“Design decision needed”/“close” v. “feedback”
fields you should and shouldn’t fill in
234. TOOLS
Learn to use:
Command Line (CLI)
(eg: bash)
grep (or ack) and find
Regular Expressions
(aka: regex)
NOW you have TOOLS to COMMUNICATE and CONTRIBUTE
TOO BIG: RKM learnt in weekend, core within a month or two.
But noone on earth doing for linux kernel -- drive by shootings, gotta know you, trust you -LINUXCON LAST WEEK
236. SAYING: I DON’T KNOW
Harry Kroto
On feeling stupid:
Everyone does.
Everyone is about most things.
The “best” leverage this
to their advantage
(usually very humble.)
HE ... was
IT’S a CONTINUUM
237. ASK/LISTEN
Rule of Thumb:
stuck for ½ hour.
Go to: IRC, mailing-list
Don’t agonise, spare yourself the pain!
Often:
~ experienced people can see/feel you struggling (but seldom say anything)
~ so, in short term you feel like gumby BUT: learn something, might actually look clever
~ in medium term: your corpus is building faster
238. ASK/EXPLAIN
State as
simply as possible.
State it up front.
Time is precious: be terse
terse
təәrs/
adjective
1. sparing in the use of words; abrupt.
"a terse statement"
synonyms:
brief, short, to the point, concise, succinct, crisp, pithy, incisive,
No fluffy language, no big explanation.
BE CORDIAL
Just get to the core of it.
240. TURN UP!
Decisions are made
by the people
who turn up.
Hackerspaces
User Groups
Conferences
Congratulations you are already here.
Connect and develop.
242. CONTRIBUTING
COMMUNICATE
Find the venues to do so.
Mail-list
Might be several!
IRC
Issue Tracker
Wiki
NOW you have TOOLS to COMMUNICATE and CONTRIBUTE
TOO BIG: RKM learnt in weekend, core within a month or two.
But noone on earth doing for linux kernel -- drive by shootings, gotta know you, trust you -LINUXCON LAST WEEK
243. BEING INVOLVED
Real world is not uni.
Flexible
FOSS is really flexible.
Young projects can turn on a dime for your idea.
Envisioning and implementing all the fine
details is expensive for new projects.
245. DO WHAT YOU SAY
YOU’RE GOING TO DO
But, if you can’t
communicate!
FOSS people are spectacularly
understanding.
246. Don’t get disheartened.
All mistakes will
eventually be washed clean
by time and entropy.
Communities are very robust.
247. INTERESTING
TIMES
Stream-lined ability to contribute/communicate.
Culture is changing: tech is becoming mainstream.
Re-learning old lessons.
Not just chicks, it’s older, multicultural.
248. INTERESTING
TIMES
Stream-lined ability to contribute/communicate.
Culture is changing: tech is becoming mainstream.
Re-learning old lessons.
Demographic imbalance is being addressed.
Not just chicks, it’s older, multicultural.
250. INTERESTING
TIMES
Stream-lined ability to contribute/communicate.
Culture is changing: tech is becoming mainstream.
Re-learning old lessons.
Demographic imbalance is being addressed.
Copyright is being questioned.
Patent-wars.
WATCH THIS SPACE
251. CONCLUSION
There will always be some form of
“Open Source”.
People like us will make it happen.
This is the version we’ve currently got and it’s changing.
253. Contributors: Be Cordial
•
Keep all interactions with a maintainer as
respectful as possible.
•
They have likely donated a significant
amount of time and energy into their project.
•
They don’t owe you a moment of their time.
254. Maintainers: Be Cordial
•
You have the crucial responsibility of being
immensely thankful to all contributors.
•
•
•
They are the lifeblood of your project.
Ignore non-constructive feedback.
Some people just take things too seriously.
255. Maintainers: Be Cordial
•
Be careful with the words you chose.
Contributors sometimes take what you say
very personally.
•
•
Take the opportunity to educate the user.
•
A little bit of kindness goes a long way.
This could be their first ever interaction with
an open source project.
256. Sustainability
•
Sustainability is one of the biggest
challenges of open source.
•
•
Everyone has a limited amount of time.
It’s easy to become the bottleneck of
your own projects.
258. Learn to Say No
•
•
Saying ‘No’ is extremely difficult.
•
If you say yes often, your project will be
ruined. Tragedy of the Commons.
People ask for crazy features. They send
seemingly practical pull requests. They
are trying to help.
But it’s HOW YOU SELL IT ...
261. Focused Purpose
Move together or be torn apart by momentum.
* Be careful not to turn it into an end-all unless you’re sure it can be
* Spin off advanced/specialized functionality as a plugin that builds on top
262. Documentation
Just because you built it
doesn’t mean they will come.
* Except for rare situations (absolute need or so sexy!), without this, no one will use it
* Case in point: It’s why many of you know about Flask but virtually no one knows about Itty
* Lack of docs means most people will get frustrated & move on
263. Communication
Will make or break you.
* This goes along with focus
* People want to know it’s actively developed on, what the future holds, how to get help, how
they can help
* IRC
* Mailing lists
* Website
264. Make Contribution Easy
It’s the only way you’ll get any contribution at all.
* GH/BB model of fork & pull req
* Define **how** others can contribute
* I suck at this one
265. Listen
Graciously accept both positive &
negative feedback.
* You should consider yourself a success when you acquire haters
* Remember there are lots of happy people who are quietly using the software
* I’m super-thin-skinned, so I struggle with this one nightly