Open gabalafou opened 6 months ago
The meeting was canceled due to the high number of participants not able to join.
Johan: JDC
Mike: posted on discourse with a hidden category for JDC.https://discourse.jupyter.org/t/2023-jupyter-distinguished-contributors-election-shepherds/23426
We should check with Chris Holdgraf on who sees these messages.
Gabriel: This is a JupyterLab team council issue but I’m curious to discuss: Move jupyter-ui-toolkit in the JupyterLab organization (#227)?
Ian: JEP on Subshell
Itay Dafna, Widgets, Netflix
Johan Mabille, Kernels
Gabriel Fouasnon, Accessibility
Frederic Collonval, JupyterLab, WebScIT
Zach Sailer | Apple | Server
Gabriel Fouasnon, Jupyter Accessibility
Johan Mabille | QuantStack | Kernels
Ian Thomas | QuantStack
schema.jupyter.org update
Looking to get some eyes on this work
Zach will take another pass at this PR, but would love some review in the meantime.
Zach Sailer | Apple | Server
Ian Thomas | QuantStack
Itay Dafna | Netflix | Widgets
David Qui | AWS
Rick Wagner | SDSC
Establish security manager groups for Jupyter GitHub orgs
The problem today is that it isn't always clear if the maintainers for subprojects are tracking the issues raised on the security. Further, the security subproject team doesn't have permission to raise security vulnerabilities on every subproject. It requires a lot of work for the team to
Related to vulnerability handling process
Rick and David are planning to write a process proposal for vulnerability handling. This would create a common way that all subprojects handle security issues that's clear for the community and easiest for the maintainers.
Once ready, someone from the SSC will champion this around the SSC to get buyin.
No meeting due to low attendence
Zach Sailer | Apple | Server
Johan Mabille | QuantStack | Kernels
Sylvain Corlay | QuantStack | Widgets
Gabriel Fouasnon |
Ian Thomas | QuantStack | N/A
Jupyter Schema: We moved the Github Pages pointer to a new \"stable\" branch. This allows us to merge and iterate ongoing work without having it deployed to the public, canonical URL.
stable
branch = published to schema.jupyter.org
main
branch = latest, ongoing work
(Gabriel) Question I would like us to end the meeting with: what do we need to communicate right now (if anything) with people outside this meeting?
For example, we have two major efforts that folks in this call have been pursuing, 1) subshell JEP and 2) schema repo bootstrapping.
Do the people that need to know about these things know about them?
How are we communicating today?
For these two specific efforts, we've pinged the "stakeholders" we identified for each. The hope would be to advertise
Rest of meeting was working session on https://github.com/jupyter/schema
Zach Sailer | Apple | Server
Johan Mabille | QuantStack | Kernels
Triaging old JEPs
Use a generic message to trigger a "time to close"
"We\'re working through old JEPs and closing proposals that are no longer active or may not be relevant anymore. Under Jupyter\'s new governance model, we have an active Software Steering Council who reviews JEPs weekly. We are catching up on the backlog now. Since there has been no active discussion on this JEP in awhile, I\'d propose we close it here (we\'ll leave it open for two more weeks in case you\'d like to revive the conversation). If you would like to re-open the discussion after we close it, you are welcome to do that too."
Commented on:
Emailed the EC and SSC about the website re-design JEP
Gabriel Fouasnon | Quansight Labs | Jupyter Accessibility
Zach Sailer | Apple | Server
Johan Mabille | QuantStack | Kernels
Sylvain
Martin
Darian
Recap of last week. Triaged old JEPs, closing with a note. But kept one open, #49 about a new Jupyter.org website design
design students who didn't already know what Jupyter was - so it has a valuable outside perspective
jupyter/governance [Discussion of Linux Foundation Proposal
We were confused by where the assets go... the c3 or the c6?
i. c3 doesn't take assets normally?
Darian will clarify this with EC.
[Gabriel] Question: hard deadlines ahead of us?
This issue is highest priority after new reps on EC and SSC are seated
Time frame seems like it will be a few months rather than a few weeks
Jeremy
Sylvain
Darian
Nobody else joined the call in the first 15 min - and we decided to table it.
Zach Sailer
Gabriel Fouasnon
Gabriel Fouasnon, Jupyter Accessibility
Zach Sailer, just observing
Johan Mabille, Kernels
Piyush Jain, just observing
Darian asks if anybody has any lingering questions (re: Linux Foundation).
Discussion about #119, one concern is a possible size limitation on the header that could be incompatible with the authentication token size (the auth token can grow indefinitely)
Jeremy Tuloup, Jupyter Frontends
Martin, Voilà
Darian, EC
No meeting because no attendees
Jeremy Tuloup, Jupyter Frontends
Gabriel Fouasnon, Accessibility
Sylvain, widgets
Gabriel to update SSC meeting minutes (last update Dec 4, 2023)
Sylvain to update SSC team compass list
Gabriel to email SSC to ask for input on #87 and #122
Sylvain to add comment on #122
[Gabriel] Let's take a few minutes to review the following JEP? Darian brought this up on April 29. (He said he has a colleague or knows someone interested in picking it up?) Parameterized kernel specs proposal #87
[Jeremy] For awareness, pre-proposal to incorporate jupyter-book as a Jupyter sub-project: https://github.com/jupyter/enhancement-proposals/issues/122
Gabriel
Martin
Johan
Darian
Gabriel to ask Zach if he can change the Zoom room
Johan: Send an email to the SSC mailing list for a potential private vote
Johan: open votes for #105 and #106
Can we use/update this SSC project board?
Can we change the Zoom room for this meeting to the main Jovyan room? Who can edit the calendar event?
2023 meeting minutes
Links to individual days in 2024
Monday, Jan 8, 2024 Monday, Jan 15, 2024 Monday, Jan 22, 2024 Monday 29 Jan 2024 Monday Feb 5, 2024 Monday Feb 12, 2024 Monday Feb 19, 2024 Monday Feb 26, 2024 Monday Mar 4, 2024 Monday Mar 11, 2024 Monday Mar 25, 2024 Monday, Apr 1, 2024 Monday, Apr 15, 2024 Monday, Apr 22, 2024 Monday, Apr 29, 2024 Monday, May 6, 2024 Monday, May 13, 2024
Original source
The original source for comments on this issue is a Google Doc. The procedure used to copy the information from the Google Doc to this GitHub issue was: