Chapter 2. The MIT, BSD, Apache, and Academic Free Licenses

The MIT and BSD Licenses were two of the earliest open source licenses. Because these licenses are relatively straightforward and illustrate some of the basic principles of open source licensing, they are described here first. The MIT (or X), BSD, and Apache Licenses are classic open source licensing software licenses and are used in many open source projects. The most well-known of these are probably the BSDNet and FreeBSD Unix-like operating systems and the Apache HTTP Server.

These licenses, as applied to the original licensed code, allow that code to be used in proprietary software and do not require that open source versions of the code be distributed. Code created under these licenses, or derived from such code, may go "closed" and developments can be made under that proprietary license, which are lost to the open source community. For the same reason, however, these licenses are very flexible and compatible with almost every form of open source license.

Tip

If you're interested in licenses that keep code from being used in proprietary software, look ahead to Chapter 3.

The Academic Free License is a somewhat more elaborate license, embodying many of the same provisions found in the MIT, BSD, and Apache Licenses; in addition, it includes certain clauses addressing the application of patent rights to open source software.

The MIT (or X) License

The MIT License, the simplest license in this book, begins as follows:

Copyright (c) <year> <copyright holders>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The <year> and <copyright holder> tags obviously refer to the date of publication of the code and the person in whom copyright is vested, which is generally going to be the creator of the code. This part of the license essentially surrenders all of the rights that the copyright holder typically receives, including, as discussed in the previous chapter, the exclusive right to commercially exploit the work and to develop derivative works from the work. In addition, the licensee may, but need not, permit its own licensees to exercise these same rights.

This grant of rights is subject to two conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

And:

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. [all caps in original]

The first of these two conditions is almost universal in open source licensing and serves the straightforward and necessary purpose of alerting future users of the work of the restrictions on it. (Copyright laws used to require that copyrighted works carry an explicit notice in published forms to receive copyright protection.) The second of the two conditions provides the warranty disclaimer described in the previous chapter.

Get Understanding Open Source and Free Software Licensing now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.