diff options
Diffstat (limited to 'doc/development/licensing.md')
| -rw-r--r-- | doc/development/licensing.md | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/development/licensing.md b/doc/development/licensing.md index cb703e98264..02b6af6ee49 100644 --- a/doc/development/licensing.md +++ b/doc/development/licensing.md @@ -48,6 +48,27 @@ For all of the above, please include `--why "Reason"` and `--who "My Name"` so t More detailed information on how the gem and its commands work is available in the [License Finder README](https://github.com/pivotal/LicenseFinder). +## Getting an unknown or Lead licensed software approved + +We sometimes need to use third-party softwares whose license is not part of the Blue Oak Council +license list, or is marked as Lead-rated in the list. In this case, the use-case needs to be +legal-approved before the software can be installed. More on this can be [found in the Handbook](https://about.gitlab.com/handbook/legal/product/#using-open-source-software). + +To get legal approval, follow these steps: + +1. Create a new [legal issue](https://gitlab.com/gitlab-com/legal-and-compliance/-/issues/new?issuable_template=general-legal-template). Make sure to include as many details as possible: + - What license is the software using? + - How and where will it be used? + - Is it being vendored or forked, or will we be using the upstream project? + - Any relevant links. +1. After the usage has been legal-approved, allowlist the software in the GitLab project. + See [License Finder commands](#license-finder-commands) above. +1. Make sure the software is also recognized by Omnibus. Create a new MR against the [`omnibus-gitlab`](https://gitlab.com/gitlab-org/omnibus-gitlab) + project. Refer to [this MR](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/6870) + for an example of what the changes should look like. You'll need to edit the following files: + - `lib/gitlab/license/analyzer.rb` + - `support/dependency_decisions.yml` + ## Encryption keys If your license was created in your local development or staging environment for Customers Portal or License App, an environment variable called `GITLAB_LICENSE_MODE` with the value `test` needs to be set to use the correct decryption key. |