1
0
mirror of https://github.com/github/choosealicense.com synced 2024-12-22 12:50:24 +01:00

Merge branch 'gh-pages' into patch-1

This commit is contained in:
Mike Linksvayer 2019-03-26 20:03:46 -07:00 committed by GitHub
commit 2e9ffdf950
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
6 changed files with 45 additions and 4 deletions

View File

@ -14,8 +14,10 @@ task :test do
Rake::Task['spec'].invoke Rake::Task['spec'].invoke
HTMLProofer.check_directory('./_site', HTMLProofer.check_directory('./_site',
check_html: true, check_html: true,
enforce_https: true,
validation: { ignore_script_embeds: true }, validation: { ignore_script_embeds: true },
url_swap: { %r{https://choosealicense.com} => '' }, url_swap: { %r{https://choosealicense.com} => '' },
url_ignore: [%r{https://github.com/github/choosealicense.com/edit/gh-pages/_licenses/}],
hydra: { max_concurrency: 10 }, hydra: { max_concurrency: 10 },
check_img_http: true).run check_img_http: true).run
end end

39
_licenses/0bsd.txt Normal file
View File

@ -0,0 +1,39 @@
---
title: BSD Zero Clause License
spdx-id: 0BSD
description: The BSD Zero Clause license goes further than the BSD 2-Clause license to allow you unlimited freedom with the software without requirements to include the copyright notice, license text, or disclaimer in either source or binary forms.
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. You may take the additional step of removing the copyright notice.
using:
- PickMeUp: https://github.com/nazar-pc/PickMeUp/blob/master/copying.md
- smoltcp: https://github.com/m-labs/smoltcp/blob/master/LICENSE-0BSD.txt
- Toybox: https://github.com/landley/toybox/blob/master/LICENSE
permissions:
- commercial-use
- distribution
- modifications
- private-use
conditions: []
limitations:
- liability
- warranty
---
Copyright (c) [year] [fullname]
Permission to use, copy, modify, and/or distribute this software for any
purpose with or without fee is hereby granted.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.

View File

@ -4,7 +4,7 @@ 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. 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. Replace [project] with the project organization, if any, that sponsors this work. 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: using:

View File

@ -5,7 +5,7 @@ hidden: false
description: A permissive license similar to the <a href="/licenses/bsd-2-clause/">BSD 2-Clause License</a>, but with a 3rd clause that prohibits others from using the name of the project or its contributors to promote derived products without written consent. description: A permissive license similar to the <a href="/licenses/bsd-2-clause/">BSD 2-Clause License</a>, but with a 3rd clause that prohibits others from using the name of the project or its contributors to promote derived products without written consent.
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 [project] with the project organization, if any, that sponsors this work. 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: using:
- d3: https://github.com/d3/d3/blob/master/LICENSE - d3: https://github.com/d3/d3/blob/master/LICENSE

View File

@ -9,7 +9,7 @@ how: Insert the license or a link to it along with a copyright notice into your
note: It is recommended to add a link to the license and copyright notice at the top of each source file, example text can be found at https://oss.oracle.com/licenses/upl/. note: It is recommended to add a link to the license and copyright notice at the top of each source file, example text can be found at https://oss.oracle.com/licenses/upl/.
using: using:
- WebLogic Kubernetes Operator: https://github.com/oracle/weblogic-kubernetes-operator/blob/master/LICENSE - WebLogic Kubernetes Operator: https://github.com/oracle/weblogic-kubernetes-operator/blob/master/LICENSE.txt
- Oracle Product Images for Docker: https://github.com/oracle/docker-images/blob/master/LICENSE - Oracle Product Images for Docker: https://github.com/oracle/docker-images/blob/master/LICENSE
- Oracle Product Boxes for Vagrant: https://github.com/oracle/vagrant-boxes/blob/master/LICENSE - Oracle Product Boxes for Vagrant: https://github.com/oracle/vagrant-boxes/blob/master/LICENSE

View File

@ -19,7 +19,7 @@ See our [appendix](/appendix/) for a table of all of the licenses cataloged in t
{: .bullets} {: .bullets}
* Open Source Initiative's FAQ on [Which Open Source license should I choose to release my software under?](https://opensource.org/faq#which-license) * Open Source Initiative's FAQ on [Which Open Source license should I choose to release my software under?](https://opensource.org/faq#which-license)
* Free Software Foundation's [advice on how to choose a license](https://www.gnu.org/licenses/license-recommendations.en.html) * Free Software Foundation's [advice on how to choose a license](https://www.gnu.org/licenses/license-recommendations.html)
* [The Legal Side of Open Source](https://opensource.guide/legal/), an Open Source Guide covering licensing and related issues * [The Legal Side of Open Source](https://opensource.guide/legal/), an Open Source Guide covering licensing and related issues
## Help us improve it ## Help us improve it