Change: title, metadata, add abstract

1 files changed, 32 insertions, 1 deletions

diff --git a/ci-arch.mdwn b/ci-arch.mdwn
index 275634c..281cc6e 100644
--- a/ci-arch.mdwn
+++ b/ci-arch.mdwn
@@ -1,5 +1,30 @@
+
 ---
-title: Future WMF CI architecture
+title: Thoughts on the architecture of a future WMF CI system
+author: Lars Wirzenius for WMF / Release Enginering
+date: work in progress, first draft being written
+abstract: |
+  The release engineering team is working on upgrading the WMF CI
+  system to be more modern. The existing CI system needs to be
+  replaced, since it relies on a customized version of Zuul, which
+  is long obsolete by upstream. The current upstream version of Zuul
+  is entirely different, so whatever happens, we need to make
+  significant, user-visible changes, and are taking advantage of the
+  opportunity to re-think the whole CI system from scratch to make
+  it server our various stakeholders better. This isn't change for
+  the sake of change, this is opportunistic redesign.
+
+  This document describes what we in the release engineering team are
+  thinking for the new CI system, and why. This is part of the second
+  phase of evaluation of new CI tooling. The first phase winnowed down
+  the potential options from several dozen to three. The second phase
+  looks as the options in more detail.
+
+  This document is in the middle of being written. Nothing is
+  finalized yet. Anything might change.
+
+  Feedback on this document is most welcome. Direct feedback to its
+  author or the RelEng team in general.
 ...
 
 
@@ -8,6 +33,12 @@ title: Future WMF CI architecture
 * CI WG plans replacement of its current WMF CI system with one of
   Argo, GitLab CI, Zuul v3.
 
+* We aim to do "continuous deployment", not only "continous
+  integration" or "continuous delivery". The goal is to deploy changes
+  to production as often and as quickly as possible, without
+  compromising on the safety and security of the production
+  environment.
+
 * This document goes into more detail of how the new CI system should
   work, without (yet) discussing which replacement is chosen. A
   meta-level architecture if you wish.