Advertisement
*
Reproduction permitted for personal use only. For reprints and reprint permission, contact reprints@wistechnology.com.

Open source software: Is it really and truly free?

Computer source code is freely available from many originators. Software developers have access to this source code, and they may use and modify it, owing no money to the originators. This “open source” software, however, carries restrictions. Typically, there are licenses that travel with it, containing various restrictions on its use and dissemination. That means that based on the license terms, the developer often has no right to charge a royalty or other fee for selling software that embodies the open source code, among other restrictions.

Open source software therefore is not the same thing as code that is in the "public domain." Software in the public domain means that there is no copyright, patent or trade secret protection for the source code, and that it is available for the taking without any restrictions. In contrast, open source software is still protected under copyright and sometimes patent laws, and may carry certain licensing restrictions.

In short, open source software is not "free." A better way to look at it is to say that the software carries with it certain "freedoms" that software owners typically would not permit others to enjoy. For example, typical software owners prohibit any copying or modification to the software, deny access to source code, restrict the number of machines on which the software may be loaded or the number of users, etc. Open source software owners, in contrast, encourage dissemination and improvements on their work, but only based on their licensed terms.

Open source criteria

The Open Source Initiative, a California 501(c) 3 corporation, is an organization recognized by the open source code community. OSI has outlined certain criteria with which a software should comply to be considered an “open source” software:
Advertisement
• The code must be redistributed freely and the license should not require payment of any royalty or other fee for such sale or redistribution.

• The program must include the source code, or it must be easily available, such as by downloading via the Internet at no cost.

• The license must allow for modifications and creation of derivative works, which must be distributed according to the terms of the original software license.

• The license must permit distribution of the modified source code, although it could require that the modified source code be distributed under a different name or version number.

• The license must not discriminate against persons or groups.

• The license must not restrict use of the source code in any given field.

• The terms attached to the source code must apply to everyone to whom the open source code is distributed and such practice should not be required to execute additional licenses.

• The rights must not depend on the program being specific to a product.

• The license must not place restrictions on other software that is distributed with the licensed software.

• The license must not be predicated on any individual technology or style of interface.

A more detailed list of the criteria listed above is available at OSI's website. The OSI lists the various licenses that it has determined are compliant with these principles. Many other licenses also exist, although they are not officially recognized by the OSI as “open source” software under its definition.

Know what you're getting

Companies employing software developers may have a policy requiring that no open source software be used, especially for products sold to third parties, given the risks of using such code. By using open source software in its products, even a few lines of code, the company might be subject to the license's requirement to give away its products for free.

The company might also be sued for infringement by someone claiming that the code in the open source software violated that person's copyright or patent. Because the company's developer did not create the code, there is no easy way to verify whether it is wholly original versus a copy of some other code.

Yet, there are advantages in working with open source software - most obviously, open source software has no financial charge for its use, and it has a community of developers behind it who are constantly improving on the code.

So, a flat ban may be outdated in today's world. Companies should develop a policy on acceptable uses of open source software to gain from the ingenuity behind open source software while managing and understanding ownership rights and risks.

Previous articles by Deborah Wilcox

Making deals with evolving technologies in mind

Deborah Wilcox: “Inline” intellectual property raises legal issues

Deborah Wilcox: The press vs. Google: Copyright cases to watch

Deborah Wilcox: Is your business domain at risk?

Deborah Wilcox: Are consumers confused by search engine ads?

Deborah A. Wilcox is a lawyer and co-chair of intellectual property litigation at Baker and Hostetler, LLP, in Cleveland. She is a graduate of the University of Wisconsin-Madison Law School and regularly handles copyright, trademark, and e-commerce litigation. She can be reached at dwilcox@bakerlaw.com.

The opinions expressed herein or statements made in the above column are solely those of the author and do not necessarily reflect the views of Wisconsin Technology Network, LLC.

WTN, LLC accepts no legal liability or responsibility for any claims made or opinions expressed here.

Comments

Richard responded 1 year ago: #1

Yes, if you develop software, you should be careful. Most companies aren't in that business, and even the ones that are use open source in appropriate areas. I note that this Web site is running PHP and Apache on FreeBSD, all open source products:

Server: Apache/2.0.59 (FreeBSD) mod_ssl/2.0.59 OpenSSL/0.9.8d mod_python/3.2.10 Python/2.4.3 DAV/2 SVN/1.2.3

James Kreilich responded 1 year ago: #2

Open Source is playing a very valuable service in the educational domain (maybe not in WI), which saves the taxpayer $$$$ and the students $$$$. Please see, for
example, Pulanski Technical College - http://pulaskitech.edu - in North Little Rock, AK.

They have LOWERED the cost to the Student and Taxpayer by using Open Office software tools in their coursework requirements. http://pulaskitech.edu/ by NOT requiring the student to own/buy MS license to do course work. The student has an extra $100 or so to get additional training.

Erik Phelps responded 1 year ago: #3

I've always advised clients to evaluate open source software the same way they would evaluate another software product/tool to solve a particular problem. Just think about the way it plays out ...

Obviously, an open source product won't "cost" any out of pocket money in the first instance, but the lack of formal support infrastructure and a regular release schedule, which would typically come with a commercial software package, would weigh in the other direction and may require other "expenses." For example, your company may have to increase staff to manage support issues if you don't have a third party to rely upon for that type of support, or you may need to have a development staff of your own to make changes/upgrades to the product.

Things that also tend to cut the other way would be concerns over intellectual property issues, as most open source products do not come with any IP warranties or indemnification and while it may never matter, it is a risk factor to be considered in the initial acquisition process. Additionally, if you are using an open source product in a larger development project, the license requirements that may obligate you to share some of your code may be unacceptable. You may also have other compatibility, security, reliability, supportability, and other issues that you will probably have to vet yourself. With certain things, this may not matter, and in some instances the support available for the open source app may well be more responsive and flexible than that available for a commercial product from a poor vendor, so I'm not suggesting that these considerations will always weight in one direction or the other.

The bottom line is that the only way to make an informed choice about whether a particular open source product is the right choice for you and your company is to fully understand the open source license terms and conditions and to understand your own business requirements, needs, and priorities. In doing this, you will need to READ and UNDERSTAND the open source license - and be careful because there are a lot of folks who also decide to "tinker" with licenses such as the Apache license, the GPL, etc., making material changes, or combining provisions from various licenses to create their own.

In today's day and age, a flat prohibition on the use of any open source products strikes me as both short-sighted and self-limiting in ways that don't make much sense. Informed and thoughtful choices about when, where, and how to use open source products can be made with the right information and expertise.

Erik Phelps

Open-Source User responded 1 year ago: #4

Open-source software is plenty free. Open-source licenses give away rights without adding any restrictions that are not already granted by copyright law.

A lot of people seem to think that open-source licenses are like contracts. They are not - they are all based on copyright law. Without the open-source license, you would not be able to use someone else's code at all without paying for it.

As we know from the current recording industry situation, copyright infringement is considered by our government and industry to be stealing. Infringing on open-source licenses is, therefore, stealing. Stealing is wrong. It is absurd that companies that steal other people's code act like they are being wronged by open-source licenses and advocates.

Furthermore, licensing issues are not unique to open-source software. If you buy a license to commercial code that does not include re-distribution rights, and then re-distribute it, you are in just as much trouble. Or more.

Neil responded 1 year ago: #5

[quote] The developer often has no right to charge a royalty or other fee for selling software that embodies the open source code, among other restrictions.[quote]


This is not wholly accurate. Under the most prevalent "Free" licence, the GPL v2 (now updated to v3), a distributor is permitted to charge a fee for the distribution of object code, but not a royalty. This fee can be be any sum. However, for distribution of source code, the fee is capped.

Certain licences may prohibit charging a distribution fee or a royalty, but, I would not see this as occuring "often."

-Add Your Comment

Name:
E-mail:

Comment Policy: WTN News accepts comments that are on-topic and do not contain advertisements, profanity or personal attacks. Comments represent the views of the individuals who post them and do not necessarily represent the views of WTN Media or our partners, advertisers, or sources.

WTN Media cannot accept liability for the content of comments posted here or verify their accuracy. If you believe this comment section is being abused, contact edit@wistechnology.com.

Advertisement
Advertisement

-More Stories

WTN Media Presents