Stack proposal identification clarification.

simensen · simensen · commit 3d8781a1a58a · 2013-08-01T13:04:48.000-05:00
diff --git a/source/index.html b/source/index.html
@@ -178,7 +178,7 @@ <h2>
 
     <div class="row-fluid">
         <div class="span6">
-            <h3><a href="{{ site.url }}/specs/0/">0 Proposals</a> <span class="label">Draft</span></h3>
+            <h3><a href="{{ site.url }}/specs/0/">STACK-0 Proposals</a> <span class="label">Draft</span></h3>
             <p>
                 Specification for how community driven Stack proposals will be
                 written and managed.
@@ -188,7 +188,7 @@ <h3><a href="{{ site.url }}/specs/0/">0 Proposals</a> <span class="label">Draft<
             </div>
         </div>
         <div class="span6">
-            <h3><a href="{{ site.url }}/specs/1/">1 Core</a> <span class="label">Draft</span></h3>
+            <h3><a href="{{ site.url }}/specs/1/">STACK-1 Core</a> <span class="label">Draft</span></h3>
             <p>
                 Specification for writing and interacting with Stack middlewares
                 and applications.
@@ -200,7 +200,7 @@ <h3><a href="{{ site.url }}/specs/1/">1 Core</a> <span class="label">Draft</span
     </div>
     <div class="row-fluid">
         <div class="span6">
-            <h3><a href="{{ site.url }}/specs/2/">2 Authentication</a> <span class="label">Draft</span></h3>
+            <h3><a href="{{ site.url }}/specs/2/">STACK-2 Authentication</a> <span class="label">Draft</span></h3>
             <p>
                 Specification for authentication middlewares to follow in order
                 for applications and authorization middlewares to be able to
@@ -211,7 +211,7 @@ <h3><a href="{{ site.url }}/specs/2/">2 Authentication</a> <span class="label">D
             </div>
         </div>
         <div class="span6">
-            <h3><a href="{{ site.url }}/specs/3/">3 Authorization</a> <span class="label">Draft</span></h3>
+            <h3><a href="{{ site.url }}/specs/3/">STACK-3 Authorization</a> <span class="label">Draft</span></h3>
             <p>
                 Specification for authorization middlewares to follow in order
                 for applications and authentication middlewares to be able to
diff --git a/source/specs/0.md b/source/specs/0.md
@@ -1,6 +1,6 @@
 ---
 layout: spec
-title: 0 Proposals
+title: STACK-0 Proposals
 status: draft
 ---
 
@@ -22,3 +22,11 @@ interpreted as described in [RFC 2119](http://www.ietf.org/rfc/rfc2119.txt).
 
  * To define a workflow for community driven Stack proposals.
 
+
+### Identification
+
+ * Each proposal MUST have an identifier that MUST follow the format of
+   `STACK-{NUMBER}`. The number SHOULD just the next available number but it MAY
+   be a special number.
+ * Each proposal MUST have a descriptive name that either names the subject of
+   the proposal or otherwise succinctly defines the focus of the proposal.
diff --git a/source/specs/1.md b/source/specs/1.md
@@ -1,6 +1,6 @@
 ---
 layout: spec
-title: 1 Core
+title: STACK-1 Core
 status: draft
 ---
 
diff --git a/source/specs/2.md b/source/specs/2.md
@@ -1,6 +1,6 @@
 ---
 layout: spec
-title: 2 Authentication
+title: STACK-2 Authentication
 status: draft
 ---
 
diff --git a/source/specs/3.md b/source/specs/3.md
@@ -1,6 +1,6 @@
 ---
 layout: spec
-title: 3 Authorization
+title: STACK-3 Authorization
 status: draft
 ---
 
