The freedom team: GNU, Linux and communities

← Album index · Edizione italiana

TEAM 02 · 6 STICKERS

Code, licences, distributions and maintenance: free software brings together different roles. GNU, the Linux kernel and Debian are distinct projects built by many people.

Catalogue numbers, not a ranking. Skills are educational readings of the work, not personality judgements. Software is built by communities: every name also represents a network of collaborators.

STICKER 007 / 024 · 1983 · 1984

Portrait of Richard Stallman
Patafisik · CC BY-SA 4.0 · Wikimedia Commons

Richard Stallman

Software freedom advocate
GNU · Emacs · GCC

Contribution. Announced GNU in 1983 and began development in 1984. He wrote important tools and promoted the freedoms to run, study, modify and share software, along with copyleft.

Skill to learn. Connect technical design with users’ rights.

Legacy and context. GNU and the GPL are pillars of the free software ecosystem. Free software concerns freedom, not just price.

Read the card’s source

STICKER 008 / 024 · 1991 · 2005

Portrait of Linus Torvalds
Krd (photo)Von Sprat (crop/extraction) · CC BY-SA 4.0 · Wikimedia Commons

Linus Torvalds

Initiator and coordinator
Linux · Git

Contribution. Started the Linux kernel in 1991 and Git in 2005. The former manages resources and hardware; the latter tracks and combines code changes.

Skill to learn. Grow a project through distributed contributions.

Legacy and context. Linux is a kernel, not a complete system on its own. GNU, other components and communities make many distributions possible.

Read the card’s source

STICKER 009 / 024 · 1993

Portrait of Ian Murdock
Ilya Schurov , Computerra Weekly · CC BY-SA 2.0 · Wikimedia Commons

Ian Murdock

Community distribution founder
Debian

Contribution. Founded Debian in August 1993. The project organised software and volunteers around an openly developed distribution.

Skill to learn. Turn many packages into a shared project.

Legacy and context. Debian is an important base for other distributions. Credit includes maintainers, translators, security teams and users.

Read the card’s source

STICKER 010 / 024 · 1996–1998

Portrait of Bruce Perens
Friprog · CC BY-SA 3.0 · Wikimedia Commons

Bruce Perens

Shared criteria builder
Debian · DFSG · Open Source Definition

Contribution. Led Debian and contributed to the Debian Free Software Guidelines. He derived the Open Source Definition from them by removing Debian-specific references.

Skill to learn. Make the conditions of sharing explicit.

Legacy and context. Source availability alone does not make a licence free or open source.

Read the card’s source

STICKER 011 / 024 · 1997

Portrait of Eric S. Raymond
Erc_S_Raymond_and_company.jpg: jerone2 derivative work: Bilby (talk) · CC BY-SA 2.0 · Wikimedia Commons

Eric S. Raymond

Collaboration analyst
fetchmail · The Cathedral and the Bazaar

Contribution. Used the experience of fetchmail and Linux to describe open development models in The Cathedral and the Bazaar, presented in 1997.

Skill to learn. Study the process as well as the product.

Legacy and context. The essay made a style of collaboration visible. Its claims are debatable, testable interpretations, not universal laws.

Read the card’s source

STICKER 012 / 024 · 1990s–2000s

AC

Typographic card: no attributed portrait.

Alan Cox

Maintainer and integrator
Linux kernel · 2.2 series

Contribution. Was a major Linux kernel developer and maintained the 2.2 series. His work included integration, fixes and patch management.

Skill to learn. Continuity of maintenance.

Legacy and context. Reliable systems need maintainers, not just a founder. The roles described here are historical.

Read the card’s source

Connections between cards: Unix → BSD and GNU; GNU + Linux kernel + other components → distributions; languages + libraries + servers → web services. Arrows indicate historical and technical relationships, not a single code lineage.

Nominate a new sticker

Who is missing from this team? Suggest programmers from any country, including less-known contributors, with work and sources. You can also use this form to correct a card. Suggestions are reviewed by the editor and are not published automatically.

Name and email are optional. Details are used to review your nomination and follow up if needed; do not include sensitive data. Contact details are not intended for publication.

← Back

Thank you for your response. ✨

Browse the other teams

The roots: Unix, objects and networks · The freedom team: GNU, Linux and communities · The toolkit: languages and editors · Our shared network: the Web, data and collaboration

Leave a comment

Your email address will not be published. Required fields are marked *