of code. If it needs to be a bit bigger, it will be.
</li>
</ol>
+
+<p>
+In addition to these stated goals, we try our best to uphold the following
+values when considering contributions to the project:
+</p>
+
+<ul>
+ <li>
+ Never break configuration files or existing workflows. Breaking changes
+ require a major version bump (v4 → v5).
+ </li>
+ <li>
+ Keep mental complexity low: once you know i3’s key features, other features
+ should be easy to understand.
+ </li>
+ <li>
+ Only add features which benefit many people, instead of going to great
+ lengths to support rarely used workflows.
+ </li>
+ <li>
+ Only documented behavior is supported. Clear documentation is a requirement
+ for contributions.
+ </li>
+</ul>
</div>