From d852617668b401568473c42c8a2f2ab50ec0e6a4 Mon Sep 17 00:00:00 2001 From: Jason Grout Date: Tue, 5 Sep 2023 10:33:10 -0600 Subject: [PATCH] Make the joint EC/SSC responsibility language the same in both EC and SSC docs There were small differences in the wording, this makes the wording exactly the same to avoid confusion. --- software_steering_council.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/software_steering_council.md b/software_steering_council.md index 58976621..5490c865 100644 --- a/software_steering_council.md +++ b/software_steering_council.md @@ -23,12 +23,14 @@ The SSC is responsible for the following: ### Shared responsibilities with the Executive Council -The SSC and EC share the responsibility for: +The EC and SSC share responsibility for approving: - Changes to the Jupyter Governance model. - Creation of new Jupyter Subprojects. - Removal of Subprojects from Jupyter. +In these decisions, each body will [vote](decision_making.md) independently and the change will be approved only if both bodies approve. + ## Membership SSC members are representatives from Jupyter Subprojects that wish to assist the community in sharing information across projects and participate in decision-making that affects many stakeholders in the Jupyter ecosystem. Any Subproject council member is eligible to represent the Subproject on the SSC. While not ideal, one person may serve as the SSC representative for more than one Subproject. In this case, a representative may cast one vote for each Subproject they represent in SSC decisions.