summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJorge O. Castro <jorgec@vmware.com>2019-08-13 22:17:05 -0400
committerJorge O. Castro <jorgec@vmware.com>2019-08-13 22:17:05 -0400
commit2aafed23fd81145a54bd787ada90f6338e2fda0f (patch)
tree296ec7e3097adbdea62a39481ed0ccb63306969e
parent2a8e825e0b3c349ae3eb94d433dd604620d9ca0f (diff)
Update bullets describing steering responsibilities
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
-rw-r--r--events/elections/2019/README.md23
1 files changed, 14 insertions, 9 deletions
diff --git a/events/elections/2019/README.md b/events/elections/2019/README.md
index ced2b3f2..1ec53155 100644
--- a/events/elections/2019/README.md
+++ b/events/elections/2019/README.md
@@ -11,17 +11,22 @@ member will serve a two (2) year term.
This election will shape the future of Kubernetes as a community and project.
While SIGs and WGs help shape the technical direction of the project, the
[Steering Committee Charter] covers the health of the project and community
-as a whole. Some examples of responsibilities to consider as you are deciding
+as a whole. Some direct responsibilities of steering members to consider as you are deciding
whether to run or who to vote for:
-- Define, evolve, and defend the vision, values, mission, and scope of the
- project.
-- Define and evolve project governance structures and policies, including how
- contributors become committers/maintainers, approvers, reviewers, members,
- etc.
-- Charter and refine policy for defining new community groups (including
- Special Interest Groups, Working Groups, and Committees), and establish
- transparency and accountability policies for such groups
+* Through the chartering review process, delegate ownership of, responsibility for
+ and authority over areas of the project to specific entities.
+* Define, evolve, and defend the non-technical vision / mission and the values
+ of the project.
+* Charter and refine policy for defining new community groups.
+ and establish transparency and accountability policies for such groups
+* Define and evolve project and group governance
+ structures and policies.
+* Act as a final non-technical escalation point for any Kubernetes repository
+* Request funds and other support from the CNCF (e.g. marketing, press, etc.)
+* Define and enforce requirements for community groups to be in good standing
+ such as having an approved charter.
+
For more context, please see the [current steering committee backlog] or a
previous [governance meeting video] which led to this whole process.