Does All Your Code Belong to Canonical?
Copyright assignment gone wild
If you believe everything you read on the Internet, then Canonical, the company behind the Ubuntu distribution, can't do anything right.
However, whatever the reasons, no sooner has the controversy over Ubuntu's contributions to GNOME and other FOSS projects quieted than people are questioning Canonical's contributor agreement, condemning it as a flawed document that misses the spirit of FOSS.
Under the Canonical Contributor Agreement, participants in Ubuntu's development agree to transfer the copyright in their work to Canonical. The controversy is not over the mere fact of the copyright assignment, which is common enough in FOSS development. It�s been been used by -- among others -- the GNU Project, OpenOffice.org, and the Free Software Foundation Europe's (FSFE) Fiduciary License Agreement.
In projects in which everyone is a volunteer, assigning copyright to a larger organization, rather than to individuals can make sense.
As FSFE's Shane M Coughlan told me several years ago, as projects grow in size, "it becomes more difficult to manage the copyright. Some authors might vanish due to accidents, death, or other factors. When it comes to making decisions about protecting the code, upgrading license, or other legal factors, it can become important to talk with copyright holders."
By contrast, in projects like the Linux kernel, in which there is no copyright assignment, managing copyright can potentially become difficult. For instance..."
Read the rest of this Canonical story at Datamation
- 1Linux Top 3: Network Security Toolkit, Untangle NG Firewall and IPFire
- 2Linux Top 3: Fedora 24, Peppermint 7 and Solus 1.2
- 3Linux Top 3: Alpine Linux 3.4, deepin 15.2 and Linux Lite 3.0
- 4Linux 4.7 Set to Boost Live Patching, Security and Power Management
- 5Linux 4.6 Charred Weasel adds USB 3.1 Support