This presentation discusses free and open-source software (FOSS) licensing and business models. It covers the categories of FOSS licenses including copyleft, weak copyleft, and permissive licenses. Common FOSS license requirements like providing source code and attribution are also reviewed. The presentation describes several FOSS business models such as dual licensing proprietary software under both FOSS and commercial licenses, open core licensing, and offering support services. Overall it provides an introduction to key concepts regarding FOSS licensing and how companies can generate revenue using FOSS.
Apache or GPL? MIT or BSD? These are just some of the licenses that attach to open source software. Do you know the important distinctions between them?
This presentation is an introduction to Free and Open Source Software Licensing and Business Models. An open-source license is a type of license for computer software and other products that allows the source code, blueprint or design to be used, modified and/or shared under defined terms and conditions. This allows end users to review and modify the source code, blueprint or design for their own customization, curiosity or troubleshooting needs.
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 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/
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
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.
Apache or GPL? MIT or BSD? These are just some of the licenses that attach to open source software. Do you know the important distinctions between them?
This presentation is an introduction to Free and Open Source Software Licensing and Business Models. An open-source license is a type of license for computer software and other products that allows the source code, blueprint or design to be used, modified and/or shared under defined terms and conditions. This allows end users to review and modify the source code, blueprint or design for their own customization, curiosity or troubleshooting needs.
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 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/
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
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.
Expert Lecture delivered at K. K. Wagh Polytechnic, Nashik (INDIA)
by,
Tushar B Kute (Asst. Professor, Sandip Institute of Technology and Research Centre, Nashik)
Session ID: SFO17-TR01
Session Name: Philosophy of Open Source
- SFO17-TR01
Speaker: Daniel Lezcano
Track:
★ Session Summary ★
What is the history and culture of Open Source?
New to Open Source? Always wondered why certain tools and processes are in place? Our presenters have experienced the good, bad and ugly of working with Open Source software and will share their wisdom and hard won tips.
---------------------------------------------------
★ Resources ★
Event Page: http://connect.linaro.org/resource/sfo17/sfo17-tr01/
Presentation:
Video:
---------------------------------------------------
★ Event Details ★
Linaro Connect San Francisco 2017 (SFO17)
25-29 September 2017
Hyatt Regency San Francisco Airport
---------------------------------------------------
Keyword:
http://www.linaro.org
http://connect.linaro.org
---------------------------------------------------
Follow us on Social Media
https://www.facebook.com/LinaroOrg
https://twitter.com/linaroorg
https://www.youtube.com/user/linaroorg?sub_confirmation=1
https://www.linkedin.com/company/1026961
Open source licenses can be more than a little confusing for those of us that just want to write a little bit of code. However, with open source components playing such a big part in the products that we create, open source licenses and compliance simply can’t be ignored.
We’ve compiled the one stop resource guide for working compliantly with open source components, including answers to FAQs about the most popular licenses in 2018. Read all about the hottest licensing trends that you need to be following and some predictions for 2019.
What is Open Source Software (OSS) and what is the idea behind it? What are examples for popular Open Source Software, what are the Advantages about using OSS, what are the disadvantages.
An introduction to open source softwareSanjuktaBanik
Open-source software (OSS) is computer software that is released under a license in which the copyright holder grants users the rights to use, study, change, and distribute the software and its source code to anyone and for any purpose.
Open source is always perceived as the distribution of the free software and its source code (so that the receiving party will be able to improve or modify it). The report includes the concept of various Revenue models used by open source vendors and identify challenge and issues they are facing. In this report I have tried to answer to few questions like: Indentifying the current revenue channels, and factor which differentiate different open source vendors; Analysis of trends in open source revenue models; Identifying the critical success factors for choosing an open source business strategy; Why a company might adopt an open-source model; How open-source licensing works; What business models might be usable for commercial open-source products and what special considerations apply to commercial products released as open source.
Expert Lecture delivered at K. K. Wagh Polytechnic, Nashik (INDIA)
by,
Tushar B Kute (Asst. Professor, Sandip Institute of Technology and Research Centre, Nashik)
Session ID: SFO17-TR01
Session Name: Philosophy of Open Source
- SFO17-TR01
Speaker: Daniel Lezcano
Track:
★ Session Summary ★
What is the history and culture of Open Source?
New to Open Source? Always wondered why certain tools and processes are in place? Our presenters have experienced the good, bad and ugly of working with Open Source software and will share their wisdom and hard won tips.
---------------------------------------------------
★ Resources ★
Event Page: http://connect.linaro.org/resource/sfo17/sfo17-tr01/
Presentation:
Video:
---------------------------------------------------
★ Event Details ★
Linaro Connect San Francisco 2017 (SFO17)
25-29 September 2017
Hyatt Regency San Francisco Airport
---------------------------------------------------
Keyword:
http://www.linaro.org
http://connect.linaro.org
---------------------------------------------------
Follow us on Social Media
https://www.facebook.com/LinaroOrg
https://twitter.com/linaroorg
https://www.youtube.com/user/linaroorg?sub_confirmation=1
https://www.linkedin.com/company/1026961
Open source licenses can be more than a little confusing for those of us that just want to write a little bit of code. However, with open source components playing such a big part in the products that we create, open source licenses and compliance simply can’t be ignored.
We’ve compiled the one stop resource guide for working compliantly with open source components, including answers to FAQs about the most popular licenses in 2018. Read all about the hottest licensing trends that you need to be following and some predictions for 2019.
What is Open Source Software (OSS) and what is the idea behind it? What are examples for popular Open Source Software, what are the Advantages about using OSS, what are the disadvantages.
An introduction to open source softwareSanjuktaBanik
Open-source software (OSS) is computer software that is released under a license in which the copyright holder grants users the rights to use, study, change, and distribute the software and its source code to anyone and for any purpose.
Open source is always perceived as the distribution of the free software and its source code (so that the receiving party will be able to improve or modify it). The report includes the concept of various Revenue models used by open source vendors and identify challenge and issues they are facing. In this report I have tried to answer to few questions like: Indentifying the current revenue channels, and factor which differentiate different open source vendors; Analysis of trends in open source revenue models; Identifying the critical success factors for choosing an open source business strategy; Why a company might adopt an open-source model; How open-source licensing works; What business models might be usable for commercial open-source products and what special considerations apply to commercial products released as open source.
The business of writing, owning, licensing and monetizing code has become more complicated due to the evolution of SaaS and the move to mobile, meaning a proliferation of apps and APIs. Proper awareness of how to own your code (or not), how to license it, how to allow others to subscribe to it, how to protect it and how monetize it is critical for every developer. IP and IT lawyer Brad Frazer will discuss these topics and more in a lively, interactive Code Camp session.
WELCOME TO, WEBASHA TECHNOLOGIES WHICH IS A CONSPICUOUS NAME AMONG LINUX TRAINING PROVIDERS OF COUNTRY
Our approach to training and development is designed to ensure that our trainees become capable of adopting up-to-date skills to work in today's modern, widest range of Industrial and Service sectors.
The training team of Webasha includes professionals who have more than 6 years experience in their respective fields. All the training sessions conducted are strictly based on the requirements of our client.
We design and deliver the best quality training to meet the changing and growing needs of the Professionals
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.
ipsr solutions ltd. is a complete IT service provider based at Kottayam, Kerala with branches at Trivandrum, Kochi, Thrissur, Kozhikode and Bangalore. We have also established a 100% subsidiary in the United Kingdom. We provide Training in Red Hat, Cisco, Microsoft, software Courses.
Introduction to Software Licensing is a powerpoint presentation that I made up to raise our company\'s awareness about the use of proprietary software and the laws involve in it.
F. Questier, Free and open source software, workshop for Lib@web international training program 'Management of Electronic Information and Digital Libraries', university of Antwerp, October 2015
Open Source Licensing Fundamentals for Financial ServicesFINOS
Andrew Hall, The Hall Law Firm: Open Source Licensing Fundamentals for Financial Services.
Andrew and Lena will address fundamental concepts of open-source licensing to assist executives in better understanding the benefits, obligations, restrictions, and risks involved in leveraging and contributing to open-source solutions and incorporating open-source licensing into commercial strategies.
The discussion will include: an overview of the different categories of open-source licenses (such as copyleft, prohibitive, and permissive); the obligations and restrictions commonly associated with the use of open-source software; the “copyleft,” “tainting,” or “viral” effect of copyleft licenses; community and private open-source license enforcement trends; and the adoption of open-source software and licensing in support of commercial product and service offerings.
JISC Webinar - An introduction to free and open source softwareJisc
http://www.jisc.ac.uk/events/2012/03/webinarfreeopensource
This webinar will introduce the ideas behind free and open source software, both for users and for developers. We will tour the basic licence types and discuss the development and membership of communities around free and open source software. We will also look at how to assess open source solutions that you may be considering.
So you've got an interesting project that you think should be open source. But what does that mean exactly and how do you go about doing it the right way? In this session we'll answer those questions and cover areas like licensing, intellectual property management, governance, developer/community infrastructure, and try to put you on the right track for a successful open source project. We'll also talk about the Jasig incubation program and how Jasig can help you deal with all these concerns.
Full screencast from the conference available at:
http://vimeo.com/10065332
Open source is a program in which the source code is available to the general public for use and/or modification from its original design free of cost.
Open source software are the once whose licenses are not restrictive and if gives us the freedom to use the program for any purpose, modify it and distribute it for further use without having to pay for it.
Business Models of Opensource and Free SoftwareFabernovel
This first research paper, distributed under the Creative Commons license, helps us to think about the open source business and faberNovel Consulting’s contribution to this community. Voluntarily educational, “Business models of open source software and free software" offers a common reference, a “tool box" to communicate about these models and to understand and adapt them.
Lightning Talk - Getting Students Involved In Open SourceGreat Wide Open
Lightning Talks are presented by Opensource.com
Chris Aniszczyk
Executive Director (interim)
Cloud Native Computing Foundation
Great Wide Open 2016
Atlanta, GA
March 17th, 2016
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
4. “Free” and “Open Source” Software
4
Free Software Foundation:
“Free Software” (four freedoms)
Open Source Initiative (OSI.org):
The “Open Source” Definition (ten requirements)
Also referred to a “OSS,” “FOSS,” and “FLOSS.”
FOSS License Examples:
GNU General Public License (GPL)
GNU Lesser General Public License (LGPL)
Mozilla Public License (MPL)
Eclipse Public License (EPL)
MIT and BSD Licenses
Apache Software License
5. Common usage of
“open source” and “FOSS”
5
Software made available:
1. to the public;
2. in source code form;
and
3. under a standard,
non-negotiated
license.
May be more accurately
referred to as “public
source” licensing
6. FOSS is not Public Domain
6
Public domain software is software:
1. That the copyright holder has explicitly
dedicated to the public; or
2. For which the copyright term has expired.
Public Domain software can be used without a
license and without restriction.
FOSS is licensed software that must be used
in accordance with the terms of the applicable
FOSS license(s).
7. How FOSS licensing differs from
commercial software licensing
7
FOSS Licensing Commercial Software Licensing
Software from many different licensors is
licensed to the general public under
standard, non-negotiable licenses.
Licensing terms are often negotiable
and vary by provider, customer,
purchased products and services, and
intended use.
Software is delivered in source form
and licensed for source or binary use.
Software is typically delivered in binary
form and licensed only for binary use.
Licenses generally permit modification,
subject to varying obligations and
restrictions.
Licenses typically include prohibitions on
reverse-engineering and modification
of the software.
Licenses generally permit royalty-free
redistribution of the software, subject to
varying obligations and restrictions.
Licenses typically prohibit or impose
royalty fees on redistribution of the
licensed software.
Licenses generally include explicit
disclaimers of warranty and liability for
downstream use of the software.
License may include warranties and
indemnification from the licensor.
Ownership interests in the software are
often distributed among many
contributors.
Ownership interest in the software is
typically consolidated in a single entity.
9. What is Copyleft?
9
Copyleft (aka viral or hereditary) licenses
require that software combined with the
copyleft software be made available to (a) in
source code form and (b) under the terms of
the same copyleft license.
Open-source licensing of proprietary software
can effectively preclude collecting license fees
for the combined software, but does not
prevenet revenue generation using the software.
10. Copyleft vs. Weak Copyleft
10
The precise scope of the copyleft effect depends on
the particular license, but copyleft licenses generally
fall into one of the two following categories.
(Strong) Copyleft: Examples include the General
Public License (GPL); Affero General Public License
(AGPL); Creative Commons Share-Alike Licenses
(CC-SA).
Weak Copyleft: Examples include the Lesser General
Public License (LGPL); Mozilla Public License (MPL);
Eclipse Public License (EPL); Common Public License
(CPL)
11. Licenses with a viral or hereditary effect where
derivative works must be licensed in source form
under the same copyleft license.
Examples: AGPL, GPL, EUPL, Creative Commons
Share-Alike (CC SA), Berkley DB (Sleepycat)
License
The viral effects of many copyleft licenses
(including the GPL) are triggered by distribution
of the copyleft software (aka are subject to the
“SaaS Loophole”)
Closed-source companies often strictly scrutinize
the use of copyleft software to avoid losing
exclusive rights to their proprietary software.
(Strong) Copyleft Licenses
11
12. Weak-Copyleft Licenses
Licenses that require modifications or
enhancements to (as opposed to derivative
works of) the weak-copyleft FOSS to be made
available (a) in source code form and (b) under
the terms of the same weak-copyleft license.
Often used for licensing software libraries.
Examples: LGPL, MPL, CPL, EPL, CDDL
As with copyleft FOSS licenses the viral effects of
most weak-copyleft FOSS licenses are triggered by
distribution of the weak-copyleft FOSS.
14
13. Weak-Copyleft Modifications
Use of weak-copyleft FOSS is often closely
scrutinized by closed-source companies to
ensure that sensitive proprietary code not
intended for public use or consumption is not
considered a modification (or equivalent term)
under the FOSS license, which typically depends
on whether the FOSS is:
1. Linked to (used as a library) or directly
combined with proprietary software; or
2. Dynamically linked or statically linked
to by the proprietary software.
15
14. Permissive Licenses
FOSS licenses that do not have a copyleft effect,
regardless of how the FOSS is used
Examples: BSD, MIT, Apache, Boost, Zlib/libping
As with copyleft and weak-copyleft licenses,
permissive licenses typically require some
combination of:
Acknowledging use of the FOSS;
Providing a copy of the license and copyright
notices included with software;
Attributing the FOSS to the author; and
Providing notice of modifications to the FOSS.
16
15. Copyleft, Weak Copyleft, and Permissive
17
Copyleft Weak Copyleft Permissive
Intended copyleft
scope
Derivative works of the
FOSS
Modifications or enhancements
to the FOSS
None
Imposes source
code obligations
on distributed or
hosted use of the
FOSS?
Nearly all distributions impose source code obligations,
regardless of modification. Some also impose source
obligations on hosted or other network uses of the FOSS.
Rarely
Attribution,
licensing,
disclaimer, or IP
notice obligations
Almost always
17. Common FOSS License Requirements
19
1. Providing corresponding source code
2. Providing acknowledgement, attribution
3. Providing IP notices and disclaimers
4. Identifying or providing access to
modifications to the FOSS
5. Patent grants and restrictions
6. Providing copies of proprietary materials
7. Granting additional use and distribution
rights
19. 21
FOSS Business Models
FOSS business models generally rely upon one
or more of the following strategies:
“Dual-licensing” of proprietary software;
“Open Core” or “Freemium” licensing of
proprietary software; and
Offering services relating to or in support of
the company’s or a third party’s FOSS-licensed
software.
20. FOSS Business Models:
Dual Licensing
Some companies offer the same software under either of a FOSS or
commercial license, a practice referred to as “dual licensing.” Examples of dual-
licensed products include MongoDB, MySQL, Java SE/EE, Berkeley DB, Wurfl,
Asterisk, Ext JS, Threaded Building Blocks, and iText.
The FOSS license selected for dual-licensing is typically a commercially
unfriendly license. Licensees that wish to incorporate the software into a
commercial product or service may need to take a commercial license in order to
avoid the undesirable effects of the FOSS license.
Alternatively, commercial licenses may provide access to product support or
customization services or include warranties and indemnification that are not
available under for the FOSS-licensed software.
Challenge: Third parties may be able to “fork” the software creating an
alternative implementation under the same or another FOSS license that is out of
the client’s control. Examples include MariaDB and Drizzle, which are forked
versions of Oracle’s dual-licensed MySQL product.
22
21. FOSS Business Models:
Open Core / Open Platform
Open Core/Freemium: Some companies offer standard
versions of certain products under a FOSS license, while
offering enhanced or “enterprise” versions of the software
under a commercial license. Examples include Sendmail
Sentrion, Sourcefire Snort, and Alfresco’s CMS software.
Open Platform: Some companies release a platform or
other software under a FOSS license and offer proprietary
plug-ins, extensions, modules, and add-ons under
commercial licensing terms. Examples include the Eclipse
platform (IBM), Android, Adobe Flex, and the Drupal,
Joomla, and Wordpress CMS platforms.
Challenge: Third parties are often able to offer competitive
commercial products and services for the same open
platform.
23
22. FOSS Business Models:
Offering Related Services
Some companies release proprietary software under a FOSS
license and offer related services for the software such as
customization, implementation, hosting, certification, and
support services. Examples of companies that have adopted
this model include Red Hat, IBM, MongoDB, Hewlett Packard,
and Microsoft.
Challenge: Third parties are often able to offer competitive
services. Companies adopting this or the open platform
strategy often assume that they will able to (i) provide
better companion products or services for software with
which they are intimately familiar, (ii) create market
advantages through, for example, release scheduling or
certification processes, or (iii) rely on their brand strength in
a competitive marketplace.
24
23. Other Benefits of
FOSS Licensing and Contributions
Companies choose to license their proprietary software under a FOSS license or
to contribute to existing FOSS project for many different reasons. Some of the
expected benefits more commonly cited include:
Increased adoption of the FOSS products or platforms for or through which
the company sells add-ons, plug-ins, content, or support services or for which
clients offer a premium or enterprise version under commercial terms;
Reduced engineering costs through crowd-sourced or cooperative
development or otherwise externalizing engineering costs by, for example,
“upstreaming” modifications to FOSS projects on which company relies;
Creating goodwill in the FOSS community, which can offer many different
benefits including benefits to developer recruiting and retention and resolving
FOSS-related disputes that may arise; and
Increased influence over the development roadmap for a FOSS project on
which the company relies.
25
24. 26
Presentation Overview
“Free” and “Open-Source” Software (FOSS)
Categories of FOSS Licenses
Common FOSS License Requirements
FOSS Business Models