Recomendados
Recomendados
Más contenido relacionado
Similar a Exploring open source licenses
Similar a Exploring open source licenses (20)
Exploring open source licenses
- 1. Exploring open source licenses
- 2. Agenda • Why open source? • GPL • LGPL • BSD • Apache • MIT • Creative Commons • Questions
- 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
- 10. References • http://www.brighthub.com/computing/linux/articles/1 26127.aspx • http://en.wikipedia.org/wiki/GNU_General_Public_Lic ense • http://en.wikipedia.org/wiki/GNU_Lesser_General_Pu blic_License • http://en.wikipedia.org/wiki/BSD_licenses • http://en.wikipedia.org/wiki/Apache_License • http://en.wikipedia.org/wiki/MIT_License • http://en.wikipedia.org/wiki/Creative_Commons_licen se
- 11. Questions?
Notas del editor
- 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