From c9f98a49c3445005d877ca8a10942fc23ea98425 Mon Sep 17 00:00:00 2001 From: Chloe Kudryavtsev Date: Sun, 26 May 2019 12:48:37 -0400 Subject: Rename to "governance" --- modules/Policies/pages/update.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'modules/Policies/pages') diff --git a/modules/Policies/pages/update.adoc b/modules/Policies/pages/update.adoc index b11a618..db4bb3d 100644 --- a/modules/Policies/pages/update.adoc +++ b/modules/Policies/pages/update.adoc @@ -5,7 +5,7 @@ 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. +This proposal shall be made in the form of a fork to the governance document, 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. -- cgit v1.2.3