summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoe Beda <joe.github@bedafamily.com>2018-03-18 09:29:20 -0700
committerJoe Beda <joe.github@bedafamily.com>2018-03-18 09:29:20 -0700
commit02b54b9de75f17a01cf06b21f6b7645971ab7ce8 (patch)
tree51a9f6f509745907eb4eee1838784e4675af02ce
parentae0ce91e0648ae8e3a0abc6ce22c33bcfea1a164 (diff)
Update TOC, remove versioning concerns
Signed-off-by: Joe Beda <joe.github@bedafamily.com>
-rw-r--r--keps/sig-contributor-experience/0005-contributor-site.md12
1 files changed, 3 insertions, 9 deletions
diff --git a/keps/sig-contributor-experience/0005-contributor-site.md b/keps/sig-contributor-experience/0005-contributor-site.md
index cd9410b6..4537973a 100644
--- a/keps/sig-contributor-experience/0005-contributor-site.md
+++ b/keps/sig-contributor-experience/0005-contributor-site.md
@@ -27,15 +27,11 @@ status: provisional
* [Goals](#goals)
* [Non-Goals](#non-goals)
* [Proposal](#proposal)
- * [User Stories [optional]](#user-stories-optional)
- * [Story 1](#story-1)
- * [Story 2](#story-2)
- * [Implementation Details/Notes/Constraints [optional]](#implementation-detailsnotesconstraints-optional)
* [Risks and Mitigations](#risks-and-mitigations)
* [Graduation Criteria](#graduation-criteria)
* [Implementation History](#implementation-history)
-* [Drawbacks [optional]](#drawbacks-optional)
-* [Alternatives [optional]](#alternatives-optional)
+* [Drawbacks](#drawbacks)
+* [Alternatives](#alternatives)
## Summary
@@ -105,6 +101,7 @@ The current generation scripts in the community repo haven't proven to be too mu
## Graduation Criteria
+
<!--
How will we know that this has succeeded?
Gathering user feedback is crucial for building high quality experiences and SIGs have the important responsibility of setting milestones for stability and completeness.
@@ -139,9 +136,6 @@ This is not preferred for a variety of reasons.
* **Quality standards.** The bar for the user facing site is higher than that of the contributor site.
Speed and openness of communication dominates for the contributor facing site.
Our bar here is the current pile of Markdown.
-* **Versioning and branching.** Much of the main user facing site is lined up on Kubernetes releases.
- This includes archived versions and branches as we lock down a release.
- None of this applies to the evergreen contributor facing site.
* **Different tooling.** We may want to create specialized preprocessors as part of the contributor site build process.
This could include integrating our current expansion of sigs.yaml into Markdown files.
It may also include recognizing specific patterns (KEP-N) and creating automatic linkages.