Posts Tagged ‘open-source’
Open Source Software - The License Obligations
March 25th, 2009
Since there are several hundred thousand free, widely used, and well maintained open source packages on the internet, it makes perfect sense to leverage open source whenever possible. If you are a commercial software developer that depends on selling your own software in the marketplace, however, it is important to understand the legal obligations and the legal restrictions that come with your open source license.
The courts have ruled that violating the license obligations in open source is similar to copyright infringement. This means you do have to respect the license obligations when you use open source.
With most open source licenses, obligations and restrictions in the license only apply if you distribute the open source, i.e., you distribute the binaries associated with the open source inside the binaries that you ship to your customers. If you use the open source software only as a development tool, the obligations posed by the open source typically do not apply.
With most Open Source licenses, the typical obligations center on attribution, re-distribution as well as various restrictions.
Attribution refers to giving credit to the authors and contributors of the open source software.
The requirements can include all, some, or none of the following:
* do not remove copyrights or license text in the source code
* insure proper credit in the documentation
* do not use the open source authors names to endorse the commercial product without permission
* clearly mark if you make any changes to the open source
* if there is a requirement to redistribute the open source, clearly show in the documentation how to get the redistribution;
* in any advertising for the commercial product, acknowledge the open source component provider.
Re-distribution refers to making the open source and related components freely available, i.e., free of charge and available to the public. This is typically under the same license as the original open source and/or with a compatible license.
This can include the original open source, as well as any changes you make, and sometimes, any software “based on” the open source code. “Based on” is interpreted differently depending on the license.
Some licenses are viral in nature, and by some interpretations essentially force you to make all of your own commercial software that is linked to the open source software to also be given away free. These licenses are also called “copy-left” licenses, and pose the greatest threat to a commercial software company’s business model.
Restrictions depend on the license, but common restrictions include:
* do not make any modifications to the open source
* do not distribute this open source software without adding your own with additional software
* do not remove copyrights in the open source
* do not initiate patent claims against any of the contributors to the open source.
Violating these restrictions can cause the license to be terminated.
While there are over 100 unique licenses, the following discusses some of the common types:
The least restrictive licenses are public domain licenses, which are essentially no licenses at all. Source code provided in the Public Domain are free to use without restriction, i.e., you can use the source code without any attribution or re-distribution and you can make modifications and derivative works; and you can distribute any or all of the open source software as you see fit.
These are followed by MIT style licenses, so named, because these licenses follow a template created by MIT. In these licenses, the rights are similar to public domain. The only obligation is attribution, whcih satisfied by leaving the original copyrights that came with the open source software in place and also providing credit to the open source authors in the end user documentation.
The next common style is the BSD style licenses, which was originally created by the University of Berkeley. The 2nd version of this licenses is similar to the MIT license, with the additional attribution requirement that the commercial software provider cannot use the names of the open source provider as a product endorsement without explicit permission.
The first version of the BSD license also required that in any advertising done for the commercial product, there was an acknowledgement of the open source provider; however, the 2nd version of the BSD license is far more common.
The next common license style is from Apache, which is a large cooperative of open source contributors, with an extensive library of open source software. The Apache 1.1 licenses requirements are very similar to the BSD 2.0 license requirements.
The Apache 2.0 license adds that any modifications to the open source code must be clearly marked with a change log. The Apache 2.0 license also adds an important restriction, the patent non-assert clause, which essentially states that if you initiate patent litigation against any of the authors or contributors who helped create this open source, you can no longer use the open source.
The next common set of licenses is the Common Public License and its derivatives such as Eclipse Public License, IBM Public License, and the Mozilla Public License. These licenses all have similar obligations to the MIT license, but they also have additional obligations in attribution and redistribution.
The CPL license requires that the commercial software developer has to make the original CPL licensed open source code as well as any changes to that source code made by the commercial developer, available for free. In addition, the commercial software developer has to state in the end user documentation how the user can obtain this open source code along with the changes. Finally, the source code changes made by the commercial developer should be clearly marked. It is important to understand, that the CPL is not viral, ie, it does not contaminate the commercial software developer’s proprietary software.
The final common set of licenses are the GPL 2.0 and the LGPL v2.1 licenses, which together make up the majority of all of the open source code on the internet.
The GPL 2.0 license has all the same attribution and redistribution requirements as the CPL license above. However, the GPL also require any works based on those packages to be offered (redistributed) under the same “free to the public” terms. Most commercial software companies consider this an unacceptable license for commercial software, as it threatens their revenues.
The LGPL v2.1 license carries a similar obligation to the GPL 2.0 license but has a more restrictive definition of where the re-distribution obligation applies, which makes it friendlier to commercial companies then the GPL license. For example, any commercial software which is not statically linked to the LGPL licensed package does not require re-distribution.
However, the LGPL license also carries other obligations such as requiring the distributor of any package which includes the LGPL libraries to allow the end user to replace those libraries. This may cause support or packaging issues for the commercial software company.
There are also several dozen unique licenses for individual open source packages. While they can generally be classified as similar to one of the common licenses described above, they often have some unique requirement or feature that needs to be taken into account.
To summarize, open source licenses have requirements in attribution, redistribution, and they can have other requirements as well. Understanding the license obligations, and abiding by them, is the true cost of free open source. It is important to understand and manage these license obligations to avoid the risk of lawsuits and other legal issues.
Tags: web, software, data recovery, education, satellite
Tags: computer, law and software development, legal disadvantages of open source, license obligations of open source, open source governance policy, open-source, software-development
Posted in computer | Comments (0)
Locking Down Your Cloud?
November 24th, 2008
How important is your data? What would happen if it got into the wrong hands? Do you think you could recover quickly if it all vanished
View post:
Locking Down Your Cloud?
Tags: Mobile, software, reference, satellite, internet
Tags: affiliate, background, certification, dvd, microsoft, open-source, parallels, SEO, virtual-networking, web
Posted in RSS, SEO, affiliate, certification, computer, computing, dvd, email, hardware, software, technology, web | Comments (0)
Who Moved My Tools?
November 24th, 2008
With credit to Spencer Johnson and his book, Who Moved My Cheese?, who moved my tools? The tools I’m referring to are the software tools that we rely on every day. I’ve had a great time at NYSCATE so far, in the hands-on workshops that precede the regular conference
More here:
Who Moved My Tools?
Tags: internet, satellite, data recovery, hardware, web
Tags: archives, browser, Computers, computing, conferences, copyright, google-reader, internet, music-writerz, open-source, reading, tools, trails, web
Posted in RSS, Uncategorized, computer, computing, email, internet, software, technology, web | Comments (0)
