Multiple choiceQuestion 1 · Recall
Loading…
By the end you can explain why copyright legislation applies to software, distinguish between the main licence categories (FSF/GPL, OSI/MIT/Apache, shareware, commercial), and justify a licence choice for a given scenario.
Code is intellectual property — it's a creative work fixed in a tangible medium (source files, binaries). Without copyright:
Copyright automatically applies the moment you write code (in most jurisdictions, including UK). You don't need to register it — though registration helps enforcement.
What copyright protects: the expression (your actual code, structure, comments). What it doesn't: ideas, algorithms, functionality, interfaces (these may be patentable instead — a different regime).
Copyright (in software)
The exclusive legal right of the creator (or their employer) to copy, distribute, modify, and publicly perform/display a software work. Others need a licence to do any of these.
A software licence is a legal document that says: "I (the copyright holder) give you permission to do X, Y, Z with my code, under conditions A, B, C."
Without a licence, all rights are reserved — no one else can legally use, copy, or modify your code.
Cambridge focuses on four licence families:
Copyleft
A licence condition requiring that modified or extended versions of the software be distributed under the same licence terms. "Share and share alike." GPL is the classic example.
1. FSF / GNU (Free Software Foundation)
2. OSI-approved (Open Source Initiative)
3. Shareware
4. Commercial / Proprietary
Worked example: Example: Choosing a licence for a new project
You're releasing a Python library for data visualisation. You want: