Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the joint EC/SSC responsibility language the same in both EC and… #179

Merged
merged 1 commit into from
Sep 5, 2023

Conversation

jasongrout
Copy link
Member

@jasongrout jasongrout commented Sep 5, 2023

Questions to answer ❓

Background or context to help others understand the change.

The wording of the joint EC/SSC responsibilities is slightly different between the EC and SSC docs, which may introduce confusion.

A brief summary of the change.

This aligns the wording between the docs to be identical.

What is the reason for this change?

To avoid confusion from slightly different wording between the two documents.

Alternatives to making this change and other considerations.

The process ❗

The process for changing the governance pages is as follows:

  • Open a pull request in draft state. This triggers a discussion and iteration phase
    for your proposed changes.
  • When you believe enough discussion has happened,
    move the pull request to an active state. This triggers a vote.
  • During the voting phase, no substantive changes may be made to the pull request.
  • The Executive Council and Software Steering Council will vote, and at the end of voting the pull request is merged or closed.

The discussion phase is meant to gather input and multiple perspectives from the community.
Make sure that the community has had an opportunity to weigh in on
the change before calling a vote. A good rule of thumb is to ask several Council
members if they believe that it is time for a vote, and to let at least one person review
the pull request for structural quality and typos.

I believe this is just a wording alignment and does not represent a shift in actual governance, and hence does not need a full vote.

… SSC docs

There were small differences in the wording, this makes the wording exactly the same to avoid confusion.
@jasongrout jasongrout requested a review from afshin September 5, 2023 16:57
@afshin
Copy link
Member

afshin commented Sep 5, 2023

Thank you!

@afshin afshin merged commit ddac4ac into jupyter:main Sep 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants