choosealicense.com/_licenses/bsd-3-clause-clear.txt

---
title: BSD 3-Clause Clear License
spdx-id: BSD-3-Clause-Clear

description: A variant of the <a href="/licenses/bsd-3-clause/">BSD 3-Clause License</a> that explicitly does not grant any patent rights.

how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders.

using:

permissions:
  - commercial-use
  - modifications
  - distribution
  - private-use

conditions:
  - include-copyright

limitations:
  - liability
  - patent-use
  - warranty

---

The Clear BSD License Copyright (c) [year] [fullname]

All rights reserved.

Redistribution and use in source and binary forms, with or without
modification,
are permitted (subject to the limitations in the disclaimer below) provided
that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.

* Neither the name of the copyright holder nor the names of its contributors
may be used to endorse or promote products derived from this software without
specific prior written permission.

NO EXPRESS OR IMPLIED LICENSES TO ANY PARTY'S PATENT RIGHTS ARE GRANTED BY
THIS LICENSE. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
add clear BSD 2015-08-19 16:14:26 -04:00			`---`
use SPDX license list 3.0 2017-12-29 14:30:08 -08:00			`title: BSD 3-Clause Clear License`
spdx-id required, nickname only for licenses with customary short names 2016-05-24 16:21:13 -05:00			`spdx-id: BSD-3-Clause-Clear`
add clear BSD 2015-08-19 16:14:26 -04:00
add missing descriptions, missing property, slight desc tweaks 2016-04-04 10:56:29 -07:00			`description: A variant of the <a href="/licenses/bsd-3-clause/">BSD 3-Clause License</a> that explicitly does not grant any patent rights.`
add clear BSD 2015-08-19 16:14:26 -04:00
Remove superfluous instruction from bsd-3-clause* 'how' field 2019-02-15 12:51:55 -08:00			`how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders.`
add clear BSD 2015-08-19 16:14:26 -04:00
make `using` required for new licenses 2017-05-30 14:17:13 -07:00			`using:`

rename/order license properties better reflect how licenses work and are structured grant (permissions) conditioned on (conditions) with limitations Permissions coming first combats mistaken but apparently widespread impression that licenses impose conditions, even such that without a license, there would be no conditions/work would be in the public domain. Requirements->Conditions emphasizes that they are pertinent if one wants to take advantage of permissions. Forbiddens->Limitations is more accurate: in most cases licenses don't give permission to hold licensors liable, in some cases to use licensors' trademarks or patents, but a licensee does not lose the permissions granted by the license if the licensee holds licensor liable, etc. Also emphasizes that there are limitatations on the license grant, not that the license imposes prohibitions. The most concise place to see both the rename and reorder is in _includes/license-overview.html I did not reorder the appearance of the groups of properties in license source files (.txt files in _licenses) as those orderings are not used to render anything on the webiste. Might do so later. 2016-03-01 13:33:15 -08:00			`permissions:`
add clear BSD 2015-08-19 16:14:26 -04:00			`- commercial-use`
			`- modifications`
			`- distribution`
			`- private-use`

sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 18:25:24 +01:00			`conditions:`
			`- include-copyright`

rename/order license properties better reflect how licenses work and are structured grant (permissions) conditioned on (conditions) with limitations Permissions coming first combats mistaken but apparently widespread impression that licenses impose conditions, even such that without a license, there would be no conditions/work would be in the public domain. Requirements->Conditions emphasizes that they are pertinent if one wants to take advantage of permissions. Forbiddens->Limitations is more accurate: in most cases licenses don't give permission to hold licensors liable, in some cases to use licensors' trademarks or patents, but a licensee does not lose the permissions granted by the license if the licensee holds licensor liable, etc. Also emphasizes that there are limitatations on the license grant, not that the license imposes prohibitions. The most concise place to see both the rename and reorder is in _includes/license-overview.html I did not reorder the appearance of the groups of properties in license source files (.txt files in _licenses) as those orderings are not used to render anything on the webiste. Might do so later. 2016-03-01 13:33:15 -08:00			`limitations:`
no-liability -> liability, warranty rename and add tag and associated descriptions fixes #412 2016-12-12 14:29:25 -08:00			`- liability`
Add "forbidden" property for "patent-use", mirroring "trademark-use", for the sorry licenses that explicitly do not grant any patent permissions 2016-02-28 12:10:23 -08:00			`- patent-use`
no-liability -> liability, warranty rename and add tag and associated descriptions fixes #412 2016-12-12 14:29:25 -08:00			`- warranty`
sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 18:25:24 +01:00
add clear BSD 2015-08-19 16:14:26 -04:00			`---`

run script/vendor-license-text 2019-07-09 14:08:08 -05:00			`The Clear BSD License Copyright (c) [year] [fullname]`
run vendor script 2018-08-11 14:11:55 -07:00
add clear BSD 2015-08-19 16:14:26 -04:00			`All rights reserved.`
simplify lines 2017-11-20 10:57:52 -08:00
Source SPDX HTML, wrap with pandoc to get closer to usable form 2017-11-19 13:49:31 -08:00			`Redistribution and use in source and binary forms, with or without`
run vendor script 2018-08-11 14:11:55 -07:00			`modification,`
			`are permitted (subject to the limitations in the disclaimer below) provided`
			`that the following conditions are met:`
simplify lines 2017-11-20 10:57:52 -08:00
run vendor script 2018-08-11 14:11:55 -07:00			`* Redistributions of source code must retain the above copyright notice, this`
			`list of conditions and the following disclaimer.`
simplify lines 2017-11-20 10:57:52 -08:00
run vendor script 2018-08-11 14:11:55 -07:00			`* Redistributions in binary form must reproduce the above copyright notice,`
			`this list of conditions and the following disclaimer in the documentation`
			`and/or other materials provided with the distribution.`
simplify lines 2017-11-20 10:57:52 -08:00
run vendor script 2018-08-11 14:11:55 -07:00			`* Neither the name of the copyright holder nor the names of its contributors`
			`may be used to endorse or promote products derived from this software without`
			`specific prior written permission.`
simplify lines 2017-11-20 10:57:52 -08:00
Source SPDX HTML, wrap with pandoc to get closer to usable form 2017-11-19 13:49:31 -08:00			`NO EXPRESS OR IMPLIED LICENSES TO ANY PARTY'S PATENT RIGHTS ARE GRANTED BY`
			`THIS LICENSE. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND`
run vendor script 2018-08-11 14:11:55 -07:00			`CONTRIBUTORS`
			`"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED`
			`TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR`
			`PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS`
			`BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR`
			`CONSEQUENTIAL`
			`DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR`
			`SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER`
			`CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,`
			`OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE`
			`USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.`