Commit 3f452f20 authored by Iris Gorman's avatar Iris Gorman Committed by Dan Rhodes
Browse files

Updating product and IP handbook page

parent f0623554
Loading
Loading
Loading
Loading
+15 −15
Original line number Diff line number Diff line
---
title: "Product"
description: "Legal Product team page"
title: "Product and Intellectual Property"
description: "Legal Product and IP team page"
---

## Marketing

- Visit the [Marketing Guide: Collaborating with GitLab Legal](/handbook/legal/marketing-collaboration/), which covers amongst other things [Promotional Games](/handbook/legal/marketing-collaboration/#promotional-games) and [Media Consent and Model Release Requests](/handbook/legal/marketing-collaboration/#media-consent-and-model-release).
- Visit the [Marketing Guide: Collaborating with GitLab Legal](/handbook/legal/marketing-collaboration/), which covers amongst other things [Promotional Games](/handbook/legal/marketing-collaboration/#promotional-games) and [Publicity Waiver and Release](/handbook/legal/marketing-collaboration/#publicity-waiver-and-release)
- If the request is not addressed in the Marketing Guide, open a new [General Legal Issue](https://gitlab.com/gitlab-com/legal-and-compliance/-/issues/new?issuable_template=general-legal-template).
- For all materials requiring legal review, refer to the [Materials Legal Review Process](/handbook/legal/materials-legal-review-process).

## Patents

- Visit the [GitLab Patent Program](/handbook/legal/patent-program/) for information on how to participate in this initiative.
- Visit the [Guidelines for reviewing third-party patents](https://internal.gitlab.com/handbook/legal-and-corporate-affairs/legal-and-compliance/productguidance/#guidelines-on-reviewing-third-party-patents) (accessible to team members only).
- Visit the [Patent](/handbook/legal/patent-program/) page for information on GitLab's Patents and Patent Program, including how to participate.
- Visit the [Guidelines for reviewing third-party patents](https://internal.gitlab.com/handbook/legal-and-corporate-affairs/productguidance/#guidelines-on-reviewing-third-party-patents) (accessible to team members only).

## Trademark

- Visit [Brand Resources](https://design.gitlab.com/brand-overview/resources/) and [Trademark Guidelines](/handbook/marketing/brand-and-product-marketing/brand/brand-activation/trademark-guidelines/) for information about using GitLab's trademark.
- Visit [Brand Resources](https://design.gitlab.com/resources/) and [Trademark Guidelines](/handbook/marketing/brand-and-product-marketing/brand/brand-activation/trademark-guidelines/) for information about using GitLab's trademark.
- [Use of Third-party Trademarks in GitLab](/handbook/legal/policies/product-third-party-trademarks-guidelines/)
- [Trademarks at GitLab](/handbook/legal/trademarks-at-gitlab/)

## Cleanroom Development Process
## Cleanroom development process

- Visit this guidance (accessible to team members only) for further information on the [Cleanroom Development Process](https://internal.gitlab.com/handbook/engineering/cleanroom-development/).
- Visit this guidance (accessible to team members only) for further information on the [Cleanroom Development Process](https://internal.gitlab.com/handbook/legal-and-corporate-affairs/productguidance/#cleanroom-development-process).

## Using Open Source Software
## Using open source software

The guidance for using open source software has been updated to enable team members to comprehensively determine which open source license types are pre-approved (deemed acceptable) for use, and which require prior review by the Legal & Corporate Affairs team (as their use may be unacceptable).

@@ -47,31 +47,31 @@ Team members must ensure that we **comply with all requirements and restrictions

- [GitLab Licensing and Compatibility](https://gitlab.com/gitlab-org/gitlab-foss/blob/master/doc/development/licensing.md).
- For general information, see: [Google Open Source Program](https://opensource.google/documentation/reference) and [Licenses](https://opensource.google/documentation/reference/thirdparty/licenses)
- For requests related to use of third-party software or other questions related to the use of open source licenses, open a [Legal Issue](https://gitlab.com/gitlab-com/legal-and-compliance/-/issues/new?issuable_template=general-legal-template) and include any information relevant to the request.
- For requests related to use of third-party software or other questions related to the use of open source licenses, open a [legal issue](https://gitlab.com/gitlab-com/legal-and-compliance/-/issues/new?issuable_template=general-legal-template) and include any information relevant to the request.

## Contributor License Agreements
## Contributor license agreements

If you're contributing to an open source project on behalf of GitLab, you may be required to enter into a CLA. In accordance with the [Authorization Matrix Policy](/handbook/finance/authorization-matrix/#authorization-matrix-policy), Legal approval is required to you enter into a CLA on behalf of GitLab.
If you're contributing to an open source project on behalf of GitLab, you may be required to enter into a CLA. In accordance with the [Authorization Matrix Policy](https://internal.gitlab.com/handbook/company/authorization-matrix/), legal approval is required to you enter into a CLA on behalf of GitLab.

If you have the choice between a Corporate and Individual CLAs, opt for the Corporate CLA.

Follow these steps to obtain legal approval and enter into a CLA on behalf of GitLab:

1. Check the [Third-party CLA Tracker](https://docs.google.com/spreadsheets/d/106bLmkl6IofWN__iwnu0UwQZzdm5JvDf8qdLV_4DTh8/edit#gid=0) to verify whether there is already a CLA in place in respect of the project you want to contribute to.
1. If there's no CLA already in place listed in the [Third-party CLA Tracker](https://docs.google.com/spreadsheets/d/106bLmkl6IofWN__iwnu0UwQZzdm5JvDf8qdLV_4DTh8/edit#gid=0), open a new [Legal Issue](https://gitlab.com/gitlab-com/legal-and-compliance/-/issues/new?issuable_template=general-legal-template) in the [Legal and Compliance Project](https://gitlab.com/gitlab-com/legal-and-compliance/-/issues).
1. If there's no CLA already in place listed in the [Third-party CLA Tracker](https://docs.google.com/spreadsheets/d/106bLmkl6IofWN__iwnu0UwQZzdm5JvDf8qdLV_4DTh8/edit#gid=0), open a new [legal issue](https://gitlab.com/gitlab-com/legal-and-compliance/-/issues/new?issuable_template=general-legal-template).
1. Apply the `CLA` label to the issue.
1. Include details of the project you are contributing to, and add the CLA for approval, either as an attachment or a hyperlink, to the issue.
1. Legal will review the CLA, requesting additional information where necessary, and approve.
1. If an email address and/or account is required to enter into the CLA, the `cla_managers`[at] `gitlab.com` email address should be used. Access to this Google Group can be requested and granted via the issue if required.
1. Once Legal have confirmed approval of the CLA in the issue, you can proceed to enter into the CLA (using the `cla_managers`[at] `gitlab.com` email if one is required) and begin contributing to the project.

Contributions to a third-party project on behalf of GitLab should be made using your @gitlab.com email address. We are continuing to develop our policy and workflow around CLAs on behalf of GitLab contributors. [See related issue here](https://gitlab.com/gitlab-com/marketing/community-relations/opensource-program/general/-/issues/238). For any questions in the meantime, please post to the [#legal](https://gitlab.slack.com/app_redirect?channel=C78E74A6L) Slack channel.
Contributions to a third-party project on behalf of GitLab should be made using your @gitlab.com email address. Post any questions to the [#legal](https://gitlab.slack.com/app_redirect?channel=C78E74A6L) Slack channel.

Alternatively, if looking for information on contributing to GitLab see [here](https://about.gitlab.com/community/contribute/dco-cla/).

## Authorship Criteria

GitLab has established guidance to aid with determining authorship of academic papers developed at GitLab. This guidance is accessible to team membery only [here](https://internal.gitlab.com/handbook/legal-and-corporate-affairs/legal-and-compliance/productguidance/#authorship-criteria)
GitLab has established guidance to aid with determining authorship of academic papers developed at GitLab. This guidance is accessible to team members only [here](https://internal.gitlab.com/handbook/legal-and-corporate-affairs/productguidance/#authorship-criteria)

## GPL Cooperation Commitment