Open ivanov opened 1 year ago
Isabela - Meeting times
Min - meetings
Rick - Suggested standing topics: Review list of JEPS, JEP process until stable.
[Frederic] Incubator organization
[Frederic]Markdown syntax evolution: addition of MermaidJS inJupyterLab and nbconvert.
Zach -
Who is going to JupyterCon?
Frederic
Johan
Eric
Min
Sylvain
[NEXT ACTIONS]
Batch of JEPs for Mar 13 to April 12
Open Under Consideration
Proposed list of JEPs to update status (Smaller team to curate)
Abandoned, Withdrawn, and Rejected PEPs
Accepted PEPs (accepted; may not be implemented yet)
[Frederic] Incubator - open PR to update the incubator process to align with the new governance and mentioning the process is obsolete and will be revised by the SSC
[Frederic] Markdown syntax evolution - open JEP for it
[Paul+anyone else] Look at what Python does for PEPs to align the JEP process with that
[Johan] Creating jupyter standard GitHub organization (with sync with Carol)
[Zach]
[Johan] Plan to call for a vote on the Reviewed JEP Process by end of the week
Start reviewingReviewed JEP process
Rick: For labels, is it possible to make them not conflict
Zack: what happens to the JEP JEP - do we make a new one, or update the old one
PEPs have “superseded by” “replaces”
Last edited
Stick to whatever python does, and do that
Nick: look at XMPP model
Discuss having the protocol documentation in its own repository (and where)
Start reviewingKernel handshaking pattern proposal
Race condition
Kernel provisioners are doing this same pattern
How do we transition from one to the other
Keep this information in the kernelspec
Zach
Grab some domains?
events.jupyter.org
Let’s keep this reserved for “events” as in social events, not schemas/protocols.
protocol.jupyter.org
schemas.jupyter.org
Move events to this new URI.
Who has the authority to make these domains
Thanks @ivanov!
Attendees
[Paul] How to include and encourage more asynchronous participation in SSC activities / meetings
https://github.com/jupyter/software-steering-council-team-compass/issues/2
Johan: pinging everyone on every PR seems like overkill
Prefer to keep it for votes
Zach: there’s not one single channel that we know everyone should be watching
Github’s tough
Google groups might be it - but no confirmation that someone’s seen it
Maybe gitter / slack channel
Zach - is new gitter painful
Discord server?
Private vs public conversations
Not private, but more internal communication -
Try something out
[Johan] What level of granularity do we want to give to jupyter-standards repositories?
[Johan] Initial documentation of kernel protocol injupyter-standards
[Johan]Kernel JSON schema JEP
[Zach] schema.jupyter.org subdomain
Went to the EC office hours to discuss this topic
Need to determine governance around this subdomain.
Who has the authority to publish schemas here?
Does every new schema require a JEP (hopefully not…)
Will submit a JEP this week.
Add some namespace to schema URIs to help address the issue of publishing serious stuff too soon, e.g. /ratified/, /experimental/, …
Require “versioning” in all URIs.
[Paul] did JEP improvements vote start from last week?
[Johan] another JEP:handshake pattern
Main disagreement about what level of detail on the impact we should have in the JEP
Gateway is not using the connection files
This proposal is closer to what they are using
Kernel Handshake JEP discussion (30 minutes)
(5 minutes)PyPI Organizations - Rick, Security
(10 minutes) subdomain and repo for schemas under jupyter.org
Heads up: lots of follow up conversations on the notebook format
Shepherd discussion
Software Steering Council Meeting in person next week at JupyterCon
None
None
Minimal attendance, no discussion/decisions today.
No decisions made on Carol’s proposal yet. The EC will meet and decide whether there is merit in changing the process or not. In case there isn’t, nothing changes and the existing process remains. In case the EC finds there is more discussion to be had on this topic, the conversation will continue by sending a member of the EC to the SSC calls.
None
Frederic:
All:
JEP to review (to prepare discussion for modifying their status) from simple to hard:
Add text-based diagram in markdown cells: https://github.com/jupyter/enhancement-proposals/pull/101
$schema in nb format: https://github.com/jupyter/enhancement-proposals/pull/97
Kernel Optional Features https://github.com/jupyter/enhancement-proposals/pull/92
Markdown flavor JEP: https://github.com/jupyter/enhancement-proposals/pull/99
Markdown based format: https://github.com/jupyter/enhancement-proposals/pull/103
Vote need on https://github.com/jupyter/enhancement-proposals/pull/66
Discussion on the JEP JEP Is the SSC the best vessel for validating the JEP? Carol proposed that the EC should be involved in the process.
Status of schema publication JEP: https://github.com/jupyter/enhancement-proposals/pull/108
[Frederic] Should we migrate more packages to jupyter standards? I was thinking nbformat and jupyter_ydoc would make sense.
[Frederic] I would like to push forward the JEPs resulting from the notebook format workshop. What would be the best path to prioritize them:
Add text-based diagram in markdown cells: https://github.com/jupyter/enhancement-proposals/pull/101
$schema in nb format: https://github.com/jupyter/enhancement-proposals/pull/97
Markdown flavor JEP: https://github.com/jupyter/enhancement-proposals/pull/99
Markdown based format: https://github.com/jupyter/enhancement-proposals/pull/103
Side note for the Markdown flavor I would like to spin up a Markdown test for the supported syntax (started work at https://github.com/jupyterlab/benchmarks/pull/97) - jupyter-standards org look like a good place
Follow-up: send in the e-mail to the council with a list of the JEP from simplest to hardest.
[Johan] Kernel Optional Features https://github.com/jupyter/enhancement-proposals/pull/92
None
Vote on Kernel handshaking pattern
Nbformat place - GitHub jupyter-standards?
JEP discussion / review
Set up of the schema website
Discussion about the SSC organization
June 19 is a US bank holidy, the meeting was adjourned until next week.
Visibility of activities.
Vote status
Kernel handshaking pattern proposal https://github.com/jupyter/enhancement-proposals/pull/66
→ Vote is closed and the JEP was accepted
→ Ensued discussion about the JEP and possible withdrawal with another JEP.
Add text-based diagram in markdown cells: https://github.com/jupyter/enhancement-proposals/pull/101 Discussion should this be a core feature or an extension one? → Will ping the SSC to vote to achieve the quorum
$schema in nb format: https://github.com/jupyter/enhancement-proposals/pull/97
→ Will ping the SSC to vote to achieve the quorum
Kernel Optional Features https://github.com/jupyter/enhancement-proposals/pull/92
→ Vote is closed and the JEP was accepted
Standard domain status
Afshin will look at the DNS rights this week
None
US public holiday (4th of July)
None
None
THis is Labor Day in the US, the meeting was cancelled.
Quick follow-up on synchronous meeting discussion from last week
Two threads on the Team Compass—let’s comment there
https://github.com/jupyter/software-steering-council-team-compass/issues/5
https://github.com/jupyter/software-steering-council-team-compass/issues/7
More discussion on how to improve participation in Jupyter SSC.
We’re seeing low participation from folks on the SSC
This is blocking us from making progress on reviewing JEPs.
Previously we discussed having a monthly synchronous to ensure all members.
The hope was that meeting in person would help develop trust/relationship between members and improve the efficiency of the council.
This is still under open discussion. There are many pros/cons to this approach. This discussion is happening in parallel to the broader discussion on how to improve participation.
No matter the results of the synchronous meeting discussion, we need to be better at asynchronous communication/work.
How do we improve this?
Vocalize some expectations and get folks to agree. This doesn’t need to be written into governance docs—it’s self-imposed by the council; a little peer pressure ;).
Regular check-ins on the google group.
Define minimum expectations
Every member needs to subscribe to and actively respond to:
SSC Google Group
SSC Team Compass repo
JEP repo
Expect, at a minimum, to spend 2 hours/week on SSC duties.
The synchronous meeting offers a good opportunity to budget this time while spending some good time with fellow council members.
If you can’t meet these expectations, you might need to evaluate if you have enough bandwidth for this council.
There is enough traffic on the channels above to spend two hours/week.
How do we use the synchronous working meeting effectively?
Spent the hour exploring Github projects as a way to organize SSC tasks and help team members align their efforts.
This was Labor Day in the US, the meeting was canceled.
Before moving any JEPs forward, we need to do two things:
-
Reach out to Carol to make sure she sees the merging standards/foundation proposal.
Add more details to SSC role expectations
Move Johan’s JEP into voting phase.
Announcement
The previous point raises a good point: should we not use https://github.com/jupyter-standards/ and move everything under https://github.com/jupyter/ following https://github.com/jupyter/governance/pull/174
Follow-up from last week
Voting period
Abstention - discussion about solution:
Adding a minimal non-abstain vote to avoid a JEP passing with
ridiculous vote enforcing the SSC members to get educated to
reduce the number of abstention
Some members point out that it will not lift the concern of having
a decision passed without a strong confidence.
Always enforce simple majority
Issue is that abstention is identical to no for the final results
Iterate with the subproject council to get a vote status (that could still be abstain)
Discussion to add new JEP states: 'superseded' and 'active'
No counter arguments
Async or sync discussion
We will keep a hybrid approach with non-mandatory sync meeting. But
votes and discussions should be reported on the issues.
Clarify restart to mean restart in-place
Zach Sailer, Apple, Server
Frederic Collonval, QuantStack, JupyterLab
Afshin T. Darian, QuantStack, EC (observing)
Johan Mabille, QuantStack, Kernels
Zach
Zach
Frederic
Gabriel Fouasnon, Jupyter Accessibility Sylvain Corlay, Voilà Johan Mabille, Kernels Zach Sailer, Server
kernel_info
request on the shell; but if the shell is busy, e.g. paused on a breakpoint or executing a long job, you have to wait for a long time
2024 meeting minutes
The meeting notes are edited via google docs during the meeting (edit link for SSC members). Each meeting's notes can then be added as a comment to this issue.
Table of content