From f7e6fb12ca708b1f8eb63e1203fecf66e1afaa55 Mon Sep 17 00:00:00 2001
From: Kristian Klausen <kristian@klausen.dk>
Date: Sat, 13 Nov 2021 13:20:41 +0100
Subject: [PATCH] Update CoC link

The file was moved when we started publishing the documents with GitLab
Pages[1][2] to https://terms.archlinux.org.

[1] https://gitlab.archlinux.org/archlinux/service-agreements/-/merge_requests/16
[2] https://gitlab.archlinux.org/archlinux/infrastructure/-/commit/d7d4ecbce125da6a6eb8b3685ed5dca9dd4e80fb
---
 README.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.rst b/README.rst
index a0b72b4..3d23315 100644
--- a/README.rst
+++ b/README.rst
@@ -180,7 +180,7 @@ Here are some guidelines:
   to the RFC process.
 - **Civility and respect:** Like all other discussions that happen in the Arch
   Linux community, RFC discussions are governed by our `Code of Conduct
-  <https://gitlab.archlinux.org/archlinux/service-agreements/-/blob/master/code-of-conduct.md>`_.
+  <https://terms.archlinux.org/docs/code-of-conduct/>`_.
   Creating an RFC is a laborious project. Commenting on an RFC should be done
   with respect and empathy for the hard work that the author has put into it.
 - **Avoid scope creep:** You should make suggestions on how the RFC can be
-- 
GitLab