Add. personal vision statment

3 files changed, 26 insertions, 1 deletions

diff --git a/ci-arch.html b/ci-arch.html
index df2f82a..056caea 100644
--- a/ci-arch.html
+++ b/ci-arch.html
@@ -21,7 +21,9 @@
 </header>
 <nav id="TOC">
 <ul>
-<li><a href="#introduction">Introduction</a></li>
+<li><a href="#introduction">Introduction</a><ul>
+<li><a href="#vision-for-ci">Vision for CI</a></li>
+</ul></li>
 <li><a href="#requirements">Requirements</a><ul>
 <li><a href="#very-hard-requirements">Very hard requirements</a></li>
 <li><a href="#hard-requirements">Hard requirements</a></li>
@@ -56,6 +58,10 @@
 <p>This document goes into more detail of how the new CI system should work, without (yet) discussing which replacement is chosen. A meta architecture if you wish.</p>
 <p>It is assumed as of the writing of this document that future CI will build on and deploy to containers orchestrated by Kubernetes.</p>
 <p>An important change is that we aim to change things so that as much as possible, all software deployments are to containers orchestrated by Kubernetes</p>
+<h2 id="vision-for-ci">Vision for CI</h2>
+<p>This is Lars’s personal opinion, for now, but it’s based on discussions with various people while at WMF. It’s not expected to be new, radical, or controversial, compared to status quo.</p>
+<p>In the future, CI at WMF serves WMF, its developers, and the Wikipedia movement by making software development more productive, more confident, and faster. The cycle time of changes (the time from idea to running in production) is short: for a trivial change, as little as five minutes. At the same time, the safety and security of production is protected: malicious changes do not get deployed, mistakes are rare, and can easily be fixed or the problematic change reverted.</p>
+<p>Production here means all the software needed to run all the sites (Wikipedias in different languages, Commons, etc), as well as supporting services, including tooling and services that supports development.</p>
 <h1 id="requirements">Requirements</h1>
 <p>This chapter lists the requirements we have for the CI system and which we design the system to fulfil.</p>
 <p>Each requirement is given a semi-mnemonic unique identifier, so it can be referred to easily.</p>
diff --git a/ci-arch.mdwn b/ci-arch.mdwn
index 6f9fd2f..c78a7ee 100644
--- a/ci-arch.mdwn
+++ b/ci-arch.mdwn
@@ -49,6 +49,25 @@ An important change is that we aim to change things so that as much as
 possible, all software deployments are to containers orchestrated by
 Kubernetes
 
+## Vision for CI
+
+This is Lars's personal opinion, for now, but it's based on
+discussions with various people while at WMF. It's not expected to be
+new, radical, or controversial, compared to status quo.
+
+In the future, CI at WMF serves WMF, its developers, and the Wikipedia
+movement by making software development more productive, more
+confident, and faster. The cycle time of changes (the time from idea
+to running in production) is short: for a trivial change, as little as
+five minutes. At the same time, the safety and security of production
+is protected: malicious changes do not get deployed, mistakes are
+rare, and can easily be fixed or the problematic change reverted.
+
+Production here means all the software needed to run all the sites
+(Wikipedias in different languages, Commons, etc), as well as
+supporting services, including tooling and services that supports
+development.
+
 # Requirements
 
 This chapter lists the requirements we have for the CI system and
diff --git a/ci-arch.pdf b/ci-arch.pdf
index b172410..9542224 100644
--- a/ci-arch.pdf
+++ b/ci-arch.pdf