Open source contribution

Stage 1 · Lesson 3 of 7

Permissive and copyleft licences

How open source works

Licences come in two families. , such as MIT, BSD and Apache 2.0, let anyone use the code, even inside products (software whose code is kept private). The main condition is keeping the copyright notice.

Apache 2.0 also adds an explicit , a written permission to use any patents the contributors hold on that code. , such as the GPL, work the other way. If you software built from the code, you must release it under the same licence.

The AGPL extends that rule to software offered to users over a network, like a web app. LGPL and MPL are weaker copyleft: the rule covers only the library, or only the files that were changed, not the whole program. This matters when you pick projects, when companies decide what they can use, and later when you license your own work.

A question to check yourself, an AI practice session and 2 cheat sheet entries come with the full roadmap. Unlock

Resources for this stage

Start with

Keep handy

  • Plain-language comparison of MIT, Apache and GPL: what each lets you do

Also worth your time

Mark this stage as not done?