From 1d5851b7e1b85754573320b173bb1a59e74d790d Mon Sep 17 00:00:00 2001 From: Mark McLoughlin Date: Sat, 16 May 2015 06:11:56 -0700 Subject: [PATCH] Outline the approval process Taken from here: http://lists.openstack.org/pipermail/transparency/2015-May/000029.html --- README.rst | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/README.rst b/README.rst index 0c27eab..1b66e48 100644 --- a/README.rst +++ b/README.rst @@ -1,4 +1,29 @@ +-------------------------------------------- +The OpenStack Foundation Transparency Policy +-------------------------------------------- + This repository contains the OpenStack Foundation Transparency Policy. See https://wiki.openstack.org/wiki/Governance/Foundation/TransparencyCommittee for more details. + +Approval Process +---------------- + +With proposed changes to the policy, the process would roughly be: + +#. Someone proposes the changes by checking out the git repo, editing + the document, and running the git-review command line too. +#. Discussion of the changes would happen through the gerrit web + interface, with people able to propose changes in line. +#. The author would respond to that discussion, mostly likely making + amendments, and uploading those new reviews to gerrit. +#. The proposal would be discussed in a committee meeting. +#. Eventually, the committee members would individually vote +1 on the + proposal. +#. The proposal would be presented to the board, showing the diff, and + the end result. Perhaps several changes would be proposed to the + board at once. +#. Each change that is approved by the board is then merged into the + repo using the gerrit web interface by either the foundation board + chair or the committee chair.