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

Software Steering Council #103

Merged
merged 9 commits into from
Nov 14, 2021
Merged

Software Steering Council #103

merged 9 commits into from
Nov 14, 2021

Conversation

afshin
Copy link
Member

@afshin afshin commented May 28, 2021

The Software Steering Council

The scope of this PR is to describe the Software Steering Council, one of the main, high-level governance structures proposed for the new model as described in the JupyterCon 2020 presentation.

We feel that the Software Steering Council is useful and complete enough to move forward with now, so we are moving this to the voting phase. Please comment below if you have further items to discuss about the Software Steering Council.

For the time being, the existing Jupyter Steering Council will function as the "Executive Board" mentioned in this document. We are working toward another PR for the Executive Board to replace the Jupyter Steering Council.


This vote closes on November 12 (anywhere on Earth) or earlier if 14 or more members of the Steering Council have voted.

All votes are limited in time to 4 weeks after the voting phase begins. At the end of 4 weeks, the proposal passes if 2/3 of the votes are in favor (fractions of a vote rounded up to the nearest integer); otherwise the proposal is rejected and the PR is closed. Prior to the four-week limit, if at least 80% of the Steering Council has voted and 2/3 of the votes are in favor (fractions of a vote rounded up to the nearest integer), the proposal passes.

(cf. governance.md)


Votes

@afshin

  • YES
  • NO

@blink1073

  • YES
  • NO

@Carreau

  • YES
  • NO

@damianavila

  • YES
  • NO

@ellisonbg

  • YES
  • NO

@fperez

  • YES
  • NO

@ivanov

  • YES
  • NO

@jasongrout

  • YES
  • NO

@jhamrick

  • YES
  • NO

@minrk

  • YES
  • NO

@mpacer

  • YES
  • NO

@parente

  • YES
  • NO

@rgbkrk

  • YES
  • NO

@Ruv7

  • YES
  • NO

@SylvainCorlay

  • YES
  • NO

@takluyver

  • YES
  • NO

@willingc

  • YES
  • NO

@afshin afshin mentioned this pull request May 28, 2021
38 tasks
fperez added a commit to afshin/governance that referenced this pull request May 28, 2021
List security as an official area (this captures existing behavior) and put UX/design/research under the BoD PR (jupyter#103 - will be updated later).
@meeseeksmachine
Copy link

This pull request has been mentioned on Jupyter Community Forum. There might be relevant details there:

https://discourse.jupyter.org/t/governance-office-hours-meeting-minutes/1480/143

@meeseeksmachine
Copy link

This pull request has been mentioned on Jupyter Community Forum. There might be relevant details there:

https://discourse.jupyter.org/t/governance-office-hours-meeting-minutes/1480/147

Co-authored-by: Jason Grout <jasongrout@users.noreply.github.com>
@afshin afshin changed the title Draft: Software Steering Council Software Steering Council Oct 15, 2021
@fperez fperez self-requested a review October 16, 2021 00:05
Copy link
Member

@fperez fperez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the outcome of our collective work so I'm obviously +1 on it, happy to discuss further if there's new feedback.

Copy link
Member

@Carreau Carreau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for shepherding this ! Looking forward to it.

@afshin afshin added the vote An explicit vote is required from the decision making body for this repository label Oct 22, 2021
@afshin afshin added the decision made Used to tag any issue or PR for which a decision has been explicitly reached, by consensus or vote. label Nov 14, 2021
@afshin afshin merged commit 45cfb6d into jupyter:master Nov 14, 2021
@jasongrout
Copy link
Member

I just noticed that this PR does not add this new document to the table of contents, so it does not show up in the officially rendered governance website: https://jupyter.org/governance

Was that intentional? Are we planning on "revealing" this to the community in the governance webpage in concert with the other governing body?

@afshin
Copy link
Member Author

afshin commented Nov 17, 2021

I just noticed that this PR does not add this new document to the table of contents, so it does not show up in the officially rendered governance website: https://jupyter.org/governance

Was that intentional? Are we planning on "revealing" this to the community in the governance webpage in concert with the other governing body?

I overlooked this when I opened it and I don't think it was the intention of any of the other authors of the text.

@jasongrout
Copy link
Member

I overlooked this when I opened it and I don't think it was the intention of any of the other authors of the text.

I made a PR to add it to the table of contents: #119

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
decision made Used to tag any issue or PR for which a decision has been explicitly reached, by consensus or vote. vote An explicit vote is required from the decision making body for this repository
Projects
None yet
Development

Successfully merging this pull request may close these issues.