Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 55.4k
    • Issues 55.4k
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1.6k
    • Merge requests 1.6k
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #15899
Closed
Open
Issue created Sep 13, 2016 by Sankar சங்கர்@psankar

CLA support

CLA Support

Many projects nowadays want to have a (Contributors License Agreement) CLA signed for safeguarding the project and the contributors from patent, ownership or other legal issues. I request gitlab to provide native support for CLAs. Once such a system is in place, project owners can create a CLA (which could be added as a file, as part of the sources, CLA.md), contributors could accept/sign it digitally.

Any PRs opened will not be merged until the contributors agree to the CLA. This can become an automated system (somewhat like CI testing before merging).

The CLA could be on a per-project basis. A list of people who have signed the CLA could be recorded as part of the metadata so that the subsequent PRs from them need not be shown the CLA dialogs again.

Some examples of CLA systems in action are: https://cla-assistant.io/ and http://clahub.com/

Instead of relying on these external systems, I want to use only gitlab for all my FOSS project needs. This will be an excellent value addition.

Edited Sep 02, 2020 by 🤖 GitLab Bot 🤖
Assignee
Assign to
Time tracking