-
Notifications
You must be signed in to change notification settings - Fork 71
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
Conversation
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).
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 |
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 <[email protected]>
There was a problem hiding this 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.
There was a problem hiding this 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.
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. |
I made a PR to add it to the table of contents: #119 |
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.
(cf. governance.md)
Votes
@afshin
@blink1073
@Carreau
@damianavila
@ellisonbg
@fperez
@ivanov
@jasongrout
@jhamrick
@minrk
@mpacer
@parente
@rgbkrk
@Ruv7
@SylvainCorlay
@takluyver
@willingc