Neoito — Software licensing
•
3 gostaram•211 visualizações
Open source licenses are licenses that comply with the Open Source Definition — in brief, they allow software to be freely used, modified, and shared. To be approved by the Open Source Initiative (also known as the OSI), a license must go through the Open Source Initiative's license review process.
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (10)
Semelhante a Neoito — Software licensing
Semelhante a Neoito — Software licensing (20)
Mais de Neoito
Mais de Neoito (14)
Último
Último (20)
Neoito — Software licensing
- 1. Software Licensing Abhilash Anandan Business Analyst Neoito
- 2. AllA DISCLAIMER I am not an open source or free software expert Just to be sure, hire a lawyer All information in this presentation is based on my research and understanding of licenses. The Open Source Initiative and Free Software Foundation have nothing to do with the presentation
- 3. Guys, meet Webbink. Mark Webbink. (He’s a lawyer. He said something.) 3
- 4. 4
- 5. 5
- 6. Guess what the whole world said? That’s what he said. 6
- 7. OK! 7
- 8. The Google Translate app can repeat anything you say in up to NINETY LANGUAGES from German and Japanese to Czech and Zulu Tip Don’t wait till the end of the presentation to give the bottom line. Reveal your product or idea (in this case a translation app) up front. 8
- 9. QUICK FACT 9
- 10. HOW MANY LISTED SOFTWARE LICENSES ARE THERE? 10
- 12. Timeline 1987 2007 1987 Beerware License 1988 MIT License 2004 Apache License 2007 GPL License 2012 Mozilla License 12
- 13. Licenses to Know ➔ BSD ➔ GPL ➔ LGPL ➔ MIT License ➔ Apache License 2.0 13
- 14. Meet the BSD License Examples ➔ React ➔ Chromium ➔ D3 ➔ nginx ➔ Scala Can ➔ Commercial Use ➔ Modify ➔ Distribute ➔ Place Warranty Cannot ➔ Hold Liable Must ➔ Include Copyright ➔ Include License 14
- 15. Meet the GPL License Examples ➔ WordPress ➔ Joomla ➔ MariaDB ➔ FreeDOS Can ➔ Commercial Use ➔ Modify ➔ Distribute ➔ Place Warranty ➔ Use Patent Claims Cannot ➔ Hold Liable ➔ Sublicense Must ➔ Disclose Source and State Changes ➔ Include Copyright ➔ Include License and Install Instructions 15
- 16. Meet the LGPL License. Examples ➔ 7 - Zip ➔ Qt ➔ VLC Media Player ➔ GTK+ Can ➔ Commercial Use ➔ Modify ➔ Distribute ➔ Place Warranty ➔ Use Patent Claims Cannot ➔ Hold Liable ➔ Sublicense Must ➔ Disclose Source and State Changes ➔ Include Copyright ➔ Include License and Install Instructions 16
- 17. Meet the MIT License. Examples ➔ Angular ➔ Gitlab ➔ Sass ➔ Meteor ➔ Node.js Can ➔ Commercial Use ➔ Modify ➔ Distribute ➔ Sublicense ➔ Private Use Cannot ➔ Hold Liable Must ➔ Include Copyright ➔ Include License 17
- 18. Meet the Apache License Examples ➔ Android ➔ NativeScript ➔ Docker ➔ TypeScript ➔ Less Can ➔ Commercial Use ➔ Modify ➔ Distribute ➔ Place Warranty ➔ Use Patent Claims ➔ Sublicense Cannot ➔ Hold Liable ➔ Use Trademark Must ➔ Include Notice and State Changes ➔ Include Copyright ➔ Include License 18
- 20. THE CONTENT OF A LICENSE CAN BE ANYTHING AS LONG AS THE INTENTION IS CLEAR 20
- 21. BEERWARE LICENSE Note These types of licenses are called “Informal Licenses” and the license is a GPL Compatible Informal License.. 21
- 22. 22
- 23. So, basically, what I’m saying is Do what you want with the code Apache License Do what you want with the code and I should be credited but it’s not my fault if I or someone screws it up. MIT License Do what you want with the code but always use GPL even if you modify it and it’s not my fault if I or someone screws it up. GPL License 23