From 49de4f09c3cbcd7caf38f3cfbc369794677a87d2 Mon Sep 17 00:00:00 2001 From: Rob Hirschfeld Date: Thu, 9 Apr 2015 14:22:29 -0500 Subject: [PATCH] Add missing details for 2015A.A3 (Designated Sections) To help facilitate discussion, I took a pass at creating the rules under the missing A3 section. My top goal was to allow BOTH the high level descriptions that the Board reviews and encourage TC to provide detailed information to guide community contributors. Change-Id: I6eb1c16e58472ffb907eee8b0cc031bc28a1c077 --- process/2015A.rst | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/process/2015A.rst b/process/2015A.rst index 1c93ca2c..d7310ee4 100644 --- a/process/2015A.rst +++ b/process/2015A.rst @@ -77,6 +77,19 @@ A2. Community Groups Tests into Capabilities A3. PTLs Recommend Changes to Designated Sections + 1. Designated Sections will not be removed without being deprecated in the + previous Guideline. + 2. Designated Sections will not be added without being advisory in the + previous Guideline. + 3. DefCore coordinates with technical leadership to define advisory sections + for projects that have advisory or required capabilities. + 4. Designated Sections may be sufficiently defined for Guidelines using + general descriptions that outline the intent of the technical leadership. + 5. DefCore will present A3.4 descriptions to the Board for approval. + 6. Technical leadership may, but is not required to, provide more specific + details describing the Designated Sections for a project. + 7. Designated sections will be included in the JSON Guideline. + A4. DefCore Committee identifies required capabilities 1. DefCore uses Board approved DefCore scoring criteria to evaluate