Index: website/content/en/internal/software-license.adoc =================================================================== --- website/content/en/internal/software-license.adoc +++ website/content/en/internal/software-license.adoc @@ -7,42 +7,49 @@ == Philosophy -The FreeBSD Project aims to produce a complete, BSD-licensed operating system allowing consumers of the system to produce derivative products without constraint or further license obligations. We invite and greatly appreciate the contribution of both changes and additions under the two-clause BSD license, and encourage the adoption of this license by other open source projects. Use of the BSD license is key to encouraging the adoption of advanced operating system technology, and on many notable occasions has been pivotal to widespread use of new technology. +The FreeBSD Project aims to produce a complete, BSD-licensed operating system allowing consumers of the system to produce derivative products without constraint or further license obligations. +We invite and greatly appreciate the contribution of both changes and additions under the two-clause BSD license, and encourage the adoption of this license by other open source projects. +Use of the BSD license is key to encouraging the adoption of advanced operating system technology, and on many notable occasions has been pivotal to widespread use of new technology. We accept however that compelling reasons exist to allow differently-licensed software to be included in the FreeBSD source tree. -We require any software under alternative licenses to be carefully isolated in the source tree so that it cannot contaminate BSD-only components. Such cautious management encourages licensing clarity and facilitates the production of BSD-only derivative products. +We require any software under alternative licenses to be carefully isolated in the source tree so that it cannot contaminate BSD-only components. +Such cautious management encourages licensing clarity and facilitates the production of BSD-only derivative products. -Unless a special exception is made, no existing BSD-licensed components may be replaced with differently-licensed software. We instead encourage FreeBSD and third party developers to seek the relicensing or reimplementation of critical components under the BSD license. Such would ease their more integral adoption into the FreeBSD operating system. +Unless a special exception is made, no existing BSD-licensed components may be replaced with differently-licensed software. +We instead encourage FreeBSD and third party developers to seek the relicensing or reimplementation of critical components under the BSD license. +Such would ease their more integral adoption into the FreeBSD operating system. == Policy -* The import of new software licensed under any licenses other than the BSD license and BSD-Like Licenses (as defined below) requires the prior approval of the FreeBSD Core Team. Requests for import must include: +* The import of new software licensed under any licenses other than the BSD license and BSD-Like Licenses, outlined below, requires the prior approval of the FreeBSD Core Team. Names in parenthesis represenbt the SPDX License Identifier. Requests for import must include: ** A list of features or bug fixes that the new version or patches contain, along with evidence that our users need those features. PRs or references to mailing list discussions are ideal forms of evidence. ** This process should be used for all software imports, not just those that require Core Team review. The mere existence of a new version does not justify an import of software to source or ports. ** A list of FreeBSD branches that may be affected. Expansions of scope require a new request to and approval from the FreeBSD Core Team. -* The Apache License 2.0 is acceptable for use in some cases. The Core Team must approve the import of new Apache License licensed components or the change of license of existing components to the Apache License. +* The Apache License 2.0 (SPDX: Apache-2.0) is acceptable for use in some cases. The Core Team must approve the import of new Apache License licensed components or the change of license of existing components to the Apache License. ** This license is approved for the following components: *** LLVM toolchain and (with LLVM Exceptions) runtime components. *** Subversion and its dependencies -* The BSD+Patent License is acceptable for use in some cases. The Core Team must approve the import of new BSD+Patent License licensed components or the change of license of existing components to the BSD+Patent License. +* The BSD 2-Clause plus Patent License (SPDX: BSD-2-Clause-Patent) is acceptable for use in some cases. The Core Team must approve the import of new BSD+Patent License licensed components or the change of license of existing components to the BSD+Patent License. ** This license is approved for the following components: *** EDK2 derived code related to UEFI functionality -* The Common Development and Distribution License (CDDL) is acceptable for use in some cases. The Core Team must approve the import of new CDDL licensed components or the change of license of existing components to the CDDL. +* The Common Development and Distribution License (SPDX: CDDL-1.1) is acceptable for use in some cases. The Core Team must approve the import of new CDDL licensed components or the change of license of existing components to the CDDL. ** This license is approved for the following components: *** DTrace *** ZFS filesystem including kernel support and userland utilities -* Historically, the phrase 'All Rights Reserved.' was included in all copyright notices. The BSD releases had it to comply with the Buenos Aires Convention of 1910 in the Americas. With the ratification of the Berne Convention in 2000, it became obsolete. As such, the FreeBSD project recommends that new code omit the phrase and encourages existing copyright holders to remove it. In 2018, the project updated its templates to remove it. +* Historically, the phrase 'All Rights Reserved.' was included in all copyright notices. The BSD releases had it to comply with the Buenos Aires Convention of 1910 in the Americas which was in force at the time of all of the BSD releases from Berkeley. With the ratification of the Berne Convention in 2000, it became obsolete. As such, the FreeBSD project recommends that new code omit the phrase and encourages existing copyright holders to remove it. In 2018, the project updated its templates to remove it. === Acceptable licenses -The following licenses are considered to be acceptable BSD-Like Licenses for the purpose of this Policy. They must be reproduced verbatim on any new code. Deviations or the use of any other license must be approved by the FreeBSD Core Team: +The following licenses are considered to be acceptable BSD-Like Licenses for the purpose of this Policy. +They must be reproduced verbatim on any new code. +Deviations or the use of any other license must be approved by the FreeBSD Core Team: -* The 2 clause version of the BSD license +* The 2 clause version of the BSD license (SPDX: BSD-2-Clause) .... /*- @@ -72,7 +79,7 @@ * [id for your version control system, if any] */ .... -* The 3 clause version of the BSD license +* The 3 clause version of the BSD license (SPDX: BSD-3-Clause) .... /*- @@ -104,7 +111,7 @@ * [id for your version control system, if any] */ .... -* The ISC License +* The ISC License (SPDX: ISC) .... /*- @@ -125,7 +132,7 @@ * [id for your version control system, if any] */ .... -* The MIT License +* The MIT License (SPDX: MIT) .... /*- @@ -152,3 +159,6 @@ * [id for your version control system, if any] */ .... + +* Third party software may use only the SPDX-License-Identifier +** See https://spdx.github.io/spdx-spec/[Annex D of SPDX Standard] for definition of standard SPDX-License-Identifier expressions used, how to interpret them and where to find the license text(s) that are applicable.