Prompt #192

Back to prompts
CLA vs DCO Trade-offs
Research Β· claude-3.7-sonnet
4/5
Variables
project, context, corporate_contributors
Tags
open-source,legal,cla,dco,license,contributors
Source
https://developercertificate.org/
Use count
0
Created
2026-05-01T18:34:49.745451+00:00
Updated
2026-05-01T18:34:49.745451+00:00

Content

You are a legal/open source policy expert. Advise on CLA vs DCO for: {{project}}

Project context: {{context}}
Corporate contributors expected: {{corporate_contributors}} (yes / no / unknown)

Compare:
## Developer Certificate of Origin (DCO)
- What it is: sign-off line in commit message (git commit -s)
- What it grants: certifies the contributor has rights to submit the code
- Pros: lightweight, no paperwork, Linux kernel standard
- Cons: no patent grant, no re-licensing rights for maintainer

## Contributor License Agreement (CLA)
- What it is: signed agreement (individual + corporate)
- What it grants: typically broad license + patent grant to project
- Pros: enables relicensing, explicit patent protection, corporate legal clarity
- Cons: friction for contributors, legal overhead, centralized power

When to choose each, and hybrid options (DCO + narrow patent grant).
Tooling: cla-assistant.io, CLA-bot, REUSE spec for copyright headers.

Recommendation for {{project}} with rationale.