Most people have at least heard of open source software by now—and even have a fairly good idea of what it is. Its own luminaries argue incessantly about what to call it—with camps arguing for everything from Free to Libre to Open Source and every possible combination of the above—but the one thing every expert agrees on is that it’s not open source (or whatever) if it doesn’t have a clearly attributed license. You can’t just publicly dump a bunch of source code without a license and say “whatever—it’s there, anybody can get it.” Due to the way copyright law works in most of the world, freely available code without an explicitly declared license is copyright by the author, all rights reserved. This means it’s just plain unsafe to use unlicensed code, published or not—there’s nothing stopping the author from coming after you and suing for royalties if you start using it. Further Reading In 2019, multiple open source companies changed course—is it the right move? The only way to actually make your code open source and freely available is to attach a license to it. Preferably, you want a comment with the name and version of a well-known license… Read full this story
- OPINION How NOT to Push a New Open Source License, Part 1
- OPINION How NOT to Push a New Open Source License, Part 2
- EXPERT ADVICE Open Source Licenses: Greater Rights, Different Responsibilities
- Navigating Open-Source Licenses Can Be Tough Task
- Free Software Foundation Hauls Cisco to Court for Open Source License Violations
- OPINION Open-Source Licensing: Here's What I've 'Noticed'
- Microsoft shares Kinect for Windows sample code under open source license
- Can GPLv3 Corral Open Source Licenses?
- Did VMware Flout Open Source License Terms?
- HP Slaps Open Source License on Unix File System
Open source licenses: What, which, and why have 300 words, post on arstechnica.com at February 24, 2020. This is cached page on X-Buy. If you want remove this page, please contact us.