docs/choosealicense.com
docs/choosealicense.com
1
0
Fork 0
mirror of https://github.com/github/choosealicense.com synced 2024-06-30 23:53:02 +02:00
Code Issues Releases Wiki Activity
f28894d905
choosealicense.com/licenses/bsd-3-clause.txt

54 lines
2.1 KiB
Plaintext
Raw Normal View History

First pass at Jekylification * Move licenses to license template * Move home / about to page template * Move annotations to config file, included via annotations.js * Move license metadata to YML Front matter * Automate the presentation of license metadata * Move sidebar to include * Add _site to gitignore
2013-04-09 18:41:25 +02:00
---
layout: license
title: BSD (3-Clause) License
Group licenses together
2013-10-29 00:10:43 +01:00
family-title: BSD
hide-from-license-list: true
Use Absolute Permalinks This removes the deprecation warning about absolute permalinks. Absolute Permalinks will be the default as of Jekyll v1.1: http://jekyllrb.com/docs/upgrading/
2013-07-14 15:32:06 +02:00
permalink: /licenses/bsd-3-clause/
First pass at Jekylification * Move licenses to license template * Move home / about to page template * Move annotations to config file, included via annotations.js * Move license metadata to YML Front matter * Automate the presentation of license metadata * Move sidebar to include * Add _site to gitignore
2013-04-09 18:41:25 +02:00
single angle braces for links and curly braces for non-vars
2013-07-17 22:32:20 +02: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. Replace {organization} with the organization, if any, that sponsors this work.
First pass at Jekylification * Move licenses to license template * Move home / about to page template * Move annotations to config file, included via annotations.js * Move license metadata to YML Front matter * Automate the presentation of license metadata * Move sidebar to include * Add _site to gitignore
2013-04-09 18:41:25 +02:00
source: http://opensource.org/licenses/BSD-3-Clause
required:
- include-copyright
permitted:
- commercial-use
- modifications
- distribution
- sublicense
forbidden:
- no-liability
- trademark-use
---
No more interpolating <<
2013-07-17 18:57:57 +02:00
Copyright (c) [year], [fullname]
First pass at Jekylification * Move licenses to license template * Move home / about to page template * Move annotations to config file, included via annotations.js * Move license metadata to YML Front matter * Automate the presentation of license metadata * Move sidebar to include * Add _site to gitignore
2013-04-09 18:41:25 +02:00
All rights reserved.
licenses: pre-format bsd license texts The license text is shown as preformatted text; therefore we need to wrap it to a sane length (like 80 characters) to keep it readable. In addition, we must do any formatting or indentation in the source file. Both BSD licenses contain a list of conditions that should be indented like a list, with blank lines in between. We could also potentially number the clauses; FreeBSD does in its copy, but the OSI versions do not.
2013-06-15 10:33:30 +02:00
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
BSD licenses: bring back the list bullets
2013-07-19 03:15:18 +02:00
* Redistributions of source code must retain the above copyright notice, this
licenses: pre-format bsd license texts The license text is shown as preformatted text; therefore we need to wrap it to a sane length (like 80 characters) to keep it readable. In addition, we must do any formatting or indentation in the source file. Both BSD licenses contain a list of conditions that should be indented like a list, with blank lines in between. We could also potentially number the clauses; FreeBSD does in its copy, but the OSI versions do not.
2013-06-15 10:33:30 +02:00
list of conditions and the following disclaimer.
BSD licenses: bring back the list bullets
2013-07-19 03:15:18 +02:00
* Redistributions in binary form must reproduce the above copyright notice, this
licenses: pre-format bsd license texts The license text is shown as preformatted text; therefore we need to wrap it to a sane length (like 80 characters) to keep it readable. In addition, we must do any formatting or indentation in the source file. Both BSD licenses contain a list of conditions that should be indented like a list, with blank lines in between. We could also potentially number the clauses; FreeBSD does in its copy, but the OSI versions do not.
2013-06-15 10:33:30 +02:00
list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.
BSD licenses: bring back the list bullets
2013-07-19 03:15:18 +02:00
* Neither the name of the {organization} nor the names of its
licenses: pre-format bsd license texts The license text is shown as preformatted text; therefore we need to wrap it to a sane length (like 80 characters) to keep it readable. In addition, we must do any formatting or indentation in the source file. Both BSD licenses contain a list of conditions that should be indented like a list, with blank lines in between. We could also potentially number the clauses; FreeBSD does in its copy, but the OSI versions do not.
2013-06-15 10:33:30 +02:00
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
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.
Reference in New Issue Copy Permalink