diff options
| author | John Baldwin <jhb@FreeBSD.org> | 2023-02-13 19:59:03 +0000 |
|---|---|---|
| committer | John Baldwin <jhb@FreeBSD.org> | 2023-02-13 19:59:03 +0000 |
| commit | cd5040e60f2672d3ef24e8a57ba256382f680ef3 (patch) | |
| tree | 018d6c17daf1edff356f380e512cffa9fed99ef2 /website/content | |
| parent | 4d1de1c7246d147e1c428b542350695b8fedf84e (diff) | |
| download | doc-cd5040e60f2672d3ef24e8a57ba256382f680ef3.tar.gz doc-cd5040e60f2672d3ef24e8a57ba256382f680ef3.zip | |
Diffstat (limited to 'website/content')
| -rw-r--r-- | website/content/en/internal/software-license.adoc | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/website/content/en/internal/software-license.adoc b/website/content/en/internal/software-license.adoc index 6c74f191a5..45e9dc17b7 100644 --- a/website/content/en/internal/software-license.adoc +++ b/website/content/en/internal/software-license.adoc @@ -19,7 +19,6 @@ Unless a special exception is made, no existing BSD-licensed components may be r * 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: ** 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. |