summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorClint Byrum <clint@fewbar.com>2016-12-15 14:36:43 -0800
committerClint Byrum <clint@fewbar.com>2016-12-15 14:36:43 -0800
commitd2e35099da6098f648d7ed7fc040e48f6cb5fd06 (patch)
tree631f5bc78522226ac53c53c153bda8c1891c7e79
parentbe3afcb49db0833ad72b80b2bda5dc1c48cccdba (diff)
Add more structure and hints about the process
The docs are clear about our overall process as a group, but these are specific guides for those wanting to submit proposals. Change-Id: I485f80e96b8c3b68ec2c2bab6f941471bfe972e4
Notes
Notes (review): Code-Review+2: Thierry Carrez <thierry@openstack.org> Workflow+1: Thierry Carrez <thierry@openstack.org> Verified+2: Jenkins Submitted-by: Jenkins Submitted-at: Wed, 11 Jan 2017 08:34:25 +0000 Reviewed-on: https://review.openstack.org/411526 Project: openstack/arch-wg Branch: refs/heads/master
-rw-r--r--proposals/README.rst27
1 files changed, 27 insertions, 0 deletions
diff --git a/proposals/README.rst b/proposals/README.rst
index ebaf970..9186aab 100644
--- a/proposals/README.rst
+++ b/proposals/README.rst
@@ -1 +1,28 @@
1Add proposals for Architecture WG collaboration here. 1Add proposals for Architecture WG collaboration here.
2
3These are mostly free-form documents, that should answer a few base questions:
4
5 * What specifically do you think is in need of architectural design
6 work in OpenStack?
7
8 * What background supports your claim that there's need to spend
9 resources analyzing, designing, and changing OpenStack in this way?
10
11 * Do you have ideas for what the Architecture Working Group would do
12 with this proposal? This would generally be, but is not limited to,
13 some of the following things:
14
15 * Produce an accurate analysis on the current state of [topic].
16
17 * Produce a cross-project spec and/or community goal for OpenStack
18 to work to support findings.
19
20 * Find and integrate existing solutions from outside OpenStack via
21 drivers/plugins/etc.
22
23As long as the proposal is on-topic for OpenStack, we will merge it
24and begin work to either accept it and gather support for working on
25it, improve the proposal, or reject it. The ultimate goal is to move
26the proposal out of here into backlog or active. The proposal should be
27ammended with next-steps before or while it is moved to backlog or active.
28Rejected proposals will be moved to rejected.