From f636caf1b3cd8ef2c0ee7a0b79ce694be07acd0a Mon Sep 17 00:00:00 2001
From: Martyn Welch <martyn.welch@collabora.com>
Date: Tue, 21 Jul 2020 15:44:04 +0100
Subject: [PATCH] Remove design process document

We are moving the contents of apertis-designs over to the website. This
workflow will therefore be obsolete. Delete it now.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>
---
 content/guidelines/design_process.md | 32 ----------------------------
 1 file changed, 32 deletions(-)
 delete mode 100644 content/guidelines/design_process.md

diff --git a/content/guidelines/design_process.md b/content/guidelines/design_process.md
deleted file mode 100644
index b311fc66d..000000000
--- a/content/guidelines/design_process.md
+++ /dev/null
@@ -1,32 +0,0 @@
-+++
-date = "2016-12-19"
-weight = 100
-
-title = "Design Process"
-
-aliases = [
-    "/old-wiki/Guidelines/Design_process"
-]
-+++
-
-  - The design documents live in the
-    [apertis-designs](https://git.apertis.org/cgit/apertis-designs.git)
-    git repository.
-  - They are written in [hotdoc](https://github.com/hotdoc)
-  - …and published on <https://docs.apertis.org/>
-  - …with the long term aim of being moved to designs.apertis.org
-
-When writing a design document:
-
-1.  [Clone](https://git-scm.com/docs/git-clone) the
-    [apertis-designs](https://git.apertis.org/cgit/apertis-designs.git)
-    git repository.
-2.  [Work in a branch](https://git-scm.com/docs/git-branch) on your new
-    document (or if you're updating an existing document).
-3.  Create a file for the document in the /docs directory.
-      - If you are updating an existing document, update its version
-        number and edit it in place (don't create a new copy of it)
-4.  The document is reviewed in Phabricator following a similar process
-    to code review
-5.  Once you’ve incorporated review comments and the changes have been
-    approved by the reviewer, merge the branch to master
-- 
GitLab