Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarified DCO and CLA requirements #1354

Merged
merged 4 commits into from
Oct 10, 2024
Merged

Clarified DCO and CLA requirements #1354

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c7806ca
Clarified DCO and CLA requirements
bensternthal Aug 14, 2024
f1997d4
Update IP_POLICY_GUIDANCE.md
bensternthal Oct 3, 2024
4ddb6e6
Update IP_POLICY_GUIDANCE.md
bensternthal Oct 3, 2024
5680778
Update IP_POLICY_GUIDANCE.md
bensternthal Oct 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 15 additions & 3 deletions governance/IP_POLICY_GUIDANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,15 +53,27 @@ All project websites need to have a [standard website footer][].

Each project must adopt either the [Developer Certificate of Origin (DCO)][DCO] or a Contributor License Agreement (CLA).

#### DCO

There are two options for implementing the DCO on your project:

1. By installing the [DCO bot](https://github.com/apps/dco)
2. By including the following in your repository:
1. Adding the DCO to your CONTRIBUTING.md file, [example](https://github.com/nodejs/node/blob/main/CONTRIBUTING.md)
2. Adding the DCO to your PR templates, [example](https://raw.githubusercontent.com/nodejs/node/main/.github/PULL_REQUEST_TEMPLATE.md)

The DCO Bot is the preferred method and is also recommended for projects that require strict enforcement.

#### CLA

The Board has pre-approved an [individual CLA][ICLA] and a [corporate CLA][CCLA].
Projects can choose to adopt either the individual CLA by itself or both the individual CLA and the corporate CLA without any further review.

If you need to use a different CLA, you must
[obtain an exemption from the board](#obtaining-an-exemption-from-the-board).

We are preparing additional guidance documentation on how to implement the DCO or a CLA, what infrastructure the foundation provides to help with this, what steps maintainers need to make when merging pull requests, and how to fix common issues that arise when using either solution.
CLAs are managed through [EasyCLA](https://docs.linuxfoundation.org/lfx/easycla).

To setup the CLA infrastructure until this additional documentation is ready, please [reach out to foundation staff](#getting-help).

## Obtaining an exemption from the Board

Expand All @@ -70,7 +82,7 @@ To do so, please [open an issue in the Cross Project Council repository](https:/

## Getting help

If you have a question about this policy or how to implement it, please reach out to [[email protected]](mailto:legal-questions@lists.openjsf.org).
If you have any questions about this policy or need assistance with its implementation, please contact the [OpenJS staff](mailto:operations@openjsf.org).

[IP Policy]: https://ip-policy.openjsf.org
[DCO]: https://developercertificate.org
Expand Down
Loading