This document discusses and compares several popular open source licenses: GPL, LGPL, BSD, Apache, MIT, and Creative Commons. It provides an overview of each license including when it was created, what rights it provides (e.g. sharing/modifying source code, patent rights), and restrictions (e.g. requiring attribution, sharing modifications). The goal is to help people understand the different options for licensing open source work.
Be Innovative with Copyright - Introduction to Open Source Business Models Haggen So
The recent popularity of sharing economy businesses demonstrates the innovation in exercising different strategies in property rights can lead to further increase the efficiency in the market. Open Source Business Models are similar to the sharing economy in the area of copyright. I am going to briefly introduce the different licences including Free and Open Source Licences and Creative Commons Licences. Examples of interesting business models built around these licences will then be presented.
Some concept of open source and how do you step into open source ....More about git and github..Notes at the bottom of each presentation is provided ............USE Mircrsoft PowerPoint for viewing
Be Innovative with Copyright - Introduction to Open Source Business Models Haggen So
The recent popularity of sharing economy businesses demonstrates the innovation in exercising different strategies in property rights can lead to further increase the efficiency in the market. Open Source Business Models are similar to the sharing economy in the area of copyright. I am going to briefly introduce the different licences including Free and Open Source Licences and Creative Commons Licences. Examples of interesting business models built around these licences will then be presented.
Some concept of open source and how do you step into open source ....More about git and github..Notes at the bottom of each presentation is provided ............USE Mircrsoft PowerPoint for viewing
Partner Mauricio Uribe continued the two-part, comprehensive discussion on open-source software and third-party vendors. The presentation focused on a more detailed exploration of the topic and strategic implications for various scenarios.
Speakers: Mauricio Uribe
tranSMART Community Meeting 5-7 Nov 13 - Session 2: Herding CatDavid Peyruc
tranSMART Community Meeting 5-7 Nov 13 - Session 2: Herding Cats: Managing Open Source Projects and Communities
Peter Rice, Imperial College London
Bioinformatics in academia was an early adopter of the open source approach to software projects, after first trying commerialisation and proprietary approaches. A selection of projects highlights the issues that arose and how they were successfully resolved.
A review of open source project models, licenses and how they are linked. Also a look into counter intuit locks that can be used to enforce open source models or to prevent malicious intents.
Slides from a talk held at JavaForum 2018-11-21 in Gothenburg and TDBI 2018-11-29 in Stockholm.
Design, Build,and Maintain the Embedded Linux PlatformSZ Lin
Using open source software to build an embedded Linux platform from scratch.
Building an embedded Linux platform is like a puzzle; placing the suitable software components in the right positions will constitute an optimal platform. However, selecting suitable components is difficult since it depends on different application scenarios. The essential components of an embedded Linux platform include the bootloader, Linux kernel, toolchain, root filesystem; it also needs the tools for image generation, upgrades, and testing. There are abundant resources in the Linux ecosystem with these components and tools; however, selecting the suitable modules and tools is still a key challenge for system designers.
Partner Mauricio Uribe continued the two-part, comprehensive discussion on open-source software and third-party vendors. The presentation focused on a more detailed exploration of the topic and strategic implications for various scenarios.
Speakers: Mauricio Uribe
tranSMART Community Meeting 5-7 Nov 13 - Session 2: Herding CatDavid Peyruc
tranSMART Community Meeting 5-7 Nov 13 - Session 2: Herding Cats: Managing Open Source Projects and Communities
Peter Rice, Imperial College London
Bioinformatics in academia was an early adopter of the open source approach to software projects, after first trying commerialisation and proprietary approaches. A selection of projects highlights the issues that arose and how they were successfully resolved.
A review of open source project models, licenses and how they are linked. Also a look into counter intuit locks that can be used to enforce open source models or to prevent malicious intents.
Slides from a talk held at JavaForum 2018-11-21 in Gothenburg and TDBI 2018-11-29 in Stockholm.
Design, Build,and Maintain the Embedded Linux PlatformSZ Lin
Using open source software to build an embedded Linux platform from scratch.
Building an embedded Linux platform is like a puzzle; placing the suitable software components in the right positions will constitute an optimal platform. However, selecting suitable components is difficult since it depends on different application scenarios. The essential components of an embedded Linux platform include the bootloader, Linux kernel, toolchain, root filesystem; it also needs the tools for image generation, upgrades, and testing. There are abundant resources in the Linux ecosystem with these components and tools; however, selecting the suitable modules and tools is still a key challenge for system designers.
4. GPL
• GNU General Public License
• Linking libraries and Copyleft
• V1 (circa 1989)
– Source Code
– Redistribution constraints based on linking
• V2 (circa 2004)
– Liberty or death
• V3 (circa 2007)
– Restricts patent payments for software
• Debate on whether static or dynamic linking
• Pros – Protects code from being stolen and used in proprietary
software
• Cons – Can’t allow open source software to accept add-ons that are
proprietary as it will have to adopt GPL
5. LGPL
• GNU Lesser General Public License
– Source code is made available
– Allows contributors to link with non-GPL and non-
open source libraries
– Copyleft
• Allows one to create proprietary software
using LGPL libraries without having to give up
the proprietary license.
6. BSD
• Distribute binaries with or without source code.
• If with source code, it should contain copyright
notice, conditions and disclaimer.
• If binary alone, documentation should capture it.
• OriginalBSD (1990) (4-clause)
• Modified BSD (1999) (3-clause)
• SimplifiedBSD (2-clause)
7. Apache
• 1.0
• 1.1 (2000)
• 2.0 (2004)
• Covers both patents and copyrights
• Perpetual worldwide rights (cannot be revoked)
• Royalty and charge-free patents
• Distribution requires a copy of Apache license to be
passed along
• Retain copy of original work
• Files modified are explicitly noted
• Proper credit should be given to contributors
8. MIT
• 1988
• Least restrictive
• Use source code or binary as you wish
• Retain the license
• Very similar to SimplifiedBSD
9. Creative Commons
• Matured in 2011
• Artistic and media works
• Copyright but allows people to redistribute as
long as you get credit
Bugs and quick fixes by the affected parties rather than waiting for a god fix from the original authors.
GPL allows the distributor to charge a reasonable fee to cover the mailing and production costs. All distributions of derived GPL work must have the GPL license passed along with the work.
Original BSDSC noticeBinary noticeCredit to organizationNo use of name without permissionModifiedBSDDrop #3SimplifiedBSDDrop #2 The good thing about the BSD License is that getting endorsements from previous contributors for your work can get you a great reputation. On the other hand you may miss out on being credited on a successful project because or the 3rd clause in this license
1.1 advertising dropped2.0 Link to copyright notice rather than in each file