Browse Source

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
changes/26/411526/1
Clint Byrum 2 years ago
parent
commit
d2e35099da
1 changed files with 27 additions and 0 deletions
  1. 27
    0
      proposals/README.rst

+ 27
- 0
proposals/README.rst View File

@@ -1 +1,28 @@
1 1
 Add proposals for Architecture WG collaboration here.
2
+
3
+These 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
+
23
+As long as the proposal is on-topic for OpenStack, we will merge it
24
+and begin work to either accept it and gather support for working on
25
+it, improve the proposal, or reject it. The ultimate goal is to move
26
+the proposal out of here into backlog or active. The proposal should be
27
+ammended with next-steps before or while it is moved to backlog or active.
28
+Rejected proposals will be moved to rejected.

Loading…
Cancel
Save