in restrictiveness. A real-world example is the Ubuntu project. The CLA leaves copyright with the contributor and allows the project to relicense the code but with a restriction based on the license the contribution was made under: 2.3 Outbound License Based on the grant of rights in Sections 2.1 and 2.2, if We include Your Contribution in a Material, We may license the Contribution under any license, including copyleft, permissive, commercial, or proprietary licenses. As a condition on the exercise of this right, We agree to also license the Contribution under the terms of the license or licenses which We are using for the Material on the Submission Date. Fedora The Fedora Project formerly required contributors to sign a CLA, either as an organization or as an individual. However, this was retired in 2011 and instead contributors must agree to the Fedora Project Contributor Agreement, which is not a license agreement and does not include assignment of copyright. Users Companies and projects that use CLAs include: .NET Foundation Apache Software Foundation Canonical Ltd Clojure Cloud Native Computing Foundation CyanogenMod Diaspora Digia/Qt Project Discourse Django Dojo Toolkit eBay Software Foundation, LLC Subsidiary of eBay Eclipse Elastic Facebook Go Google HashiCorp InfluxDB Joomla jQuery Kubernetes OpenBMC Python Meteor Microsoft MuseScore OpenMediaVault OpenStack Puppet Salesforce TiddlyWiki TLDR Pages Zend Technologies for Zend Framework (1.x series only) KDE KDE uses Free Software Foundation Europe's Fiduciary Licence Agreement of which (FLA-1.2) states in section 3.3: However, it is optional and every contributor is allowed not to assign their copyright to KDE e.V. See also Developer Certificate of Origin Project Harmony (FOSS group) References External links Contributor Licence Agreements from OSS Watch ContributorAgreements.org CLA assistant — enables contributors to sign CLAs from within a pull request Canonical (company) Computer law Copyright law Intellectual property law Licensing