From d9ef7fb6994acdb62b012249f76f583671e1b5d3 Mon Sep 17 00:00:00 2001
From: Chloe Kudryavtsev <toast@toastin.space>
Date: Tue, 26 Mar 2019 16:57:31 -0400
Subject: [policy] How to update policies and others?

---
 modules/Policies/pages/update.adoc | 12 ++++++++++++
 1 file changed, 12 insertions(+)

(limited to 'modules/Policies/pages/update.adoc')

diff --git a/modules/Policies/pages/update.adoc b/modules/Policies/pages/update.adoc
index e69de29..a534159 100644
--- a/modules/Policies/pages/update.adoc
+++ b/modules/Policies/pages/update.adoc
@@ -0,0 +1,12 @@
+= Updating Policies
+Not everything is set in stone.
+In fact few things are.
+If and when a policy (or any other internal detail, including the internal governance model) needs to be updated, there needs to be a documented procedure.
+
+In order to update a policy, an actionable proposal must be made.
+This proposal shall be made in the form of a fork to the developer handbook, with the proposal made within it.
+Ask project members, admins and others for their opinions before submitting the proposal.
+Whenever the proposal is deemed (by the author) to be mature, it may be put to the xref:voting.adoc[Vote].
+If the proposal fails, collect information on why it failed, update (in the same branch) and resubmit, unless you objected to the failure and involved the Base team.
+
+TIP: Do not squash commits - keep full history.
-- 
cgit v1.2.3

