11 posters · 1980 to 2019
Software practice
The texts that shape how software is written and shared: the GNU Manifesto, the GPL, the Open Source Definition, the Agile Manifesto, Semantic Versioning and more.
-
Software practice
RFC 761: The Robustness Principle
Jon Postel, 1980
The philosophy chapter of the 1980 TCP specification, which ends with the principle: be conservative in what you do.
Print from A2
-
Software practice
The GNU Manifesto
Richard Stallman, 1985
Richard Stallman’s 1985 call for support to write GNU, a complete Unix-compatible system that everyone may share and change.
Print from A2
-
Software practice
GNU General Public License, Version 2
Free Software Foundation, 1991
The Free Software Foundation license of 1991 letting anyone copy, change and share a program, provided derived works keep it.
Print from A2
-
Software practice
What is Free Software? The Free Software Definition
Free Software Foundation, 1996
The GNU Project’s criteria for free software: the four freedoms to run, study and change, redistribute, and share changes.
Print from A2
-
Software practice
Manifesto for Agile Software Development
Kent Beck and 16 others, 2001
Four values for developing software, stated in 2001 by seventeen people who met at Snowbird, Utah.
Print from A3
-
Software practice
PEP 20: The Zen of Python
Tim Peters, 2004
Nineteen aphorisms by Tim Peters on the principles behind the design of the Python language.
Print from A3
-
Software practice
The Open Source Definition
Open Source Initiative, 2007
The ten criteria that the distribution terms of a software license must meet to be called open source.
Print from A3
-
Software practice
The Twelve-Factor App
Adam Wiggins, 2011
A methodology of twelve factors for building software-as-a-service apps, drawn from experience with hundreds of apps on Heroku.
Print from A1
-
Software practice
Semantic Versioning 2.0.0
Tom Preston-Werner, 2013
Rules and requirements that dictate how MAJOR.MINOR.PATCH version numbers are assigned and incremented, with a grammar and a FAQ.
Print from A2
-
Software practice
Conventional Commits 1.0.0
Conventional Commits contributors, 2019
A specification for structuring commit messages so that tools can derive changelogs and semantic version bumps from them.
Print from A3
-
Software practice
Keep a Changelog 1.1.0
Olivier Lacan, 2019
Guiding principles for a changelog written for humans: one entry per version, grouped types of changes, latest first.
Print from A2
