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

SSC meeting minutes 2024 #22

Open
gabalafou opened this issue May 6, 2024 · 18 comments
Open

SSC meeting minutes 2024 #22

gabalafou opened this issue May 6, 2024 · 18 comments

Comments

@gabalafou
Copy link
Contributor

gabalafou commented May 6, 2024

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:

  1. Save in .docx format
  2. Convert to markdown using pandoc:
    pandoc -o minutes.md minutes.docx
    
  3. Open the markdown file in a code editor and manually copy-paste into the GitHub comment form, removing empty sections and bullet points.
@gabalafou
Copy link
Contributor Author

Monday, Jan 8, 2024

The meeting was canceled due to the high number of participants not able to join.

@gabalafou
Copy link
Contributor Author

Monday, Jan 15, 2024

Attendees

  • Sylvain Corlay, Voilà
  • Frederic Collonval, JupyterLab
  • Gabriel Fouasnon, Jupyter Accessibility
  • Johan Mabille, Kernels

Agenda and minutes

  • Johan: JDC

  • Gabriel: This is a JupyterLab team council issue but I’m curious to discuss: Move jupyter-ui-toolkit in the JupyterLab organization (#227)?

    • Frédéric: I should push for the council to conclude the vote.
    • Sylvain: questions about deprecated bits that were deprecated.
    • Frederic: The package of components that got deprecated has a revival in the following repository: https://github.com/Adaptive-Web-Community/Adaptive-Web-Components
      The current issue is that the new version is based on a pre-release of the FAST meta package. So I did not switch to that package.
    • Question by Mike about the License and implication of vendoring the package. It is MIT-licensed; the license was copied and the reference to the origin was added to the repository.
  • Ian: JEP on Subshell

    • Question from Mike: is one implementation option easier for kernels to adopt? (We Have 1 JupyterLab and 100s of kernels)
      1. Single thread for all messages, kernel with multiple threads. Easier to implement in kernel, and JupyterLab. Small amount of work for Ian, but requires more work for consumers.
      2. Multiple threads to multiple websockets. More work for implementer, less work for consumer.

@gabalafou
Copy link
Contributor Author

Monday, Jan 22, 2024

Attendees

  • Gabriel Fouasnon, Jupyter Accessibility
  • Johan Mabille, Kernels
  • Zach Sailer, Server,
  • Itay Dafna, Netflix, Widgets

Decisions made

  • None

Action items

Agenda and minutes

  • schema.jupyter.org
    • Requirements for this repo mentioned previously (may not be an exhaustive list)
  • Merging of JupyterLab and Notebook

@gabalafou
Copy link
Contributor Author

gabalafou commented May 16, 2024

Monday 29 Jan 2024

Attendees

  • Itay Dafna, Widgets, Netflix

  • Johan Mabille, Kernels

  • Gabriel Fouasnon, Accessibility

  • Frederic Collonval, JupyterLab, WebScIT

Agenda and minutes

@gabalafou
Copy link
Contributor Author

Monday Feb 5, 2024

Attendees

  • Zach Sailer | Apple | Server

  • Gabriel Fouasnon, Jupyter Accessibility

  • Johan Mabille | QuantStack | Kernels

  • Ian Thomas | QuantStack

Agenda and minutes

@gabalafou
Copy link
Contributor Author

gabalafou commented May 16, 2024

Monday Feb 12, 2024

Attendees

  • Zach Sailer | Apple | Server

  • Ian Thomas | QuantStack

  • Itay Dafna | Netflix | Widgets

  • David Qui | AWS

  • Rick Wagner | SDSC

Agenda and minutes

  • 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.

@gabalafou
Copy link
Contributor Author

Monday Feb 19, 2024

No meeting due to low attendence

@gabalafou
Copy link
Contributor Author

Monday Feb 26, 2024

Attendees

  • Zach Sailer | Apple | Server

  • Johan Mabille | QuantStack | Kernels

  • Sylvain Corlay | QuantStack | Widgets

  • Gabriel Fouasnon |

  • Ian Thomas | QuantStack | N/A

Decisions made

Agenda and minutes

  • (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

@gabalafou
Copy link
Contributor Author

Monday Mar 4, 2024

Attendees

  • Zach Sailer | Apple | Server

  • Johan Mabille | QuantStack | Kernels

Action items

Agenda and minutes

@gabalafou
Copy link
Contributor Author

Monday Mar 11, 2024

Attendees

  • Gabriel Fouasnon | Quansight Labs | Jupyter Accessibility

  • Zach Sailer | Apple | Server

  • Johan Mabille | QuantStack | Kernels

  • Sylvain

  • Martin

  • Darian

Decisions made

  • None

Action items

  • Darian to circle back to EC with questions raised in today's meeting

Agenda and minutes

  • Recap of last week. Triaged old JEPs, closing with a note. But kept
    one open,
    #49
    about a new Jupyter.org website design

    • #49 has a lot of valuable research - was done by university
      design students who didn't already know what Jupyter was - so it
      has a valuable outside perspective
  • jupyter/governance Discussion of Linux Foundation Proposal
    #204

    • 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

@gabalafou
Copy link
Contributor Author

Monday Mar 25, 2024

Attendees

  • Jeremy

  • Sylvain

  • Darian

Agenda

Nobody else joined the call in the first 15 min - and we decided to
table it.

@gabalafou
Copy link
Contributor Author

Monday, Apr 1, 2024

Attendees

  • Zach Sailer

  • Gabriel Fouasnon

Action items

  • Gabriel to leave comment on #119

Agenda and minutes

@gabalafou
Copy link
Contributor Author

Monday, Apr 15, 2024

Attendees

  • Gabriel Fouasnon, Jupyter Accessibility

  • Zach Sailer, just observing

  • Johan Mabille, Kernels

  • Piyush Jain, just observing

Decisions made

  • 119 should be go from pre-proposal to JEP

Action items

  • Call for a vote 105 and 106

Agenda and minutes

  • 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)

  • #105
    and
    #106
    should be moved to the voting phase.

@gabalafou
Copy link
Contributor Author

Monday, Apr 22, 2024

Attendees

  • Jeremy Tuloup, Jupyter Frontends

  • Martin, Voilà

  • Darian, EC

Agenda and minutes

  • Discussions on the Linux Foundation proposal

@gabalafou
Copy link
Contributor Author

Monday, Apr 29, 2024

No meeting because no attendees

@gabalafou
Copy link
Contributor Author

Monday, May 6, 2024

Attendees

  • Jeremy Tuloup, Jupyter Frontends

  • Gabriel Fouasnon, Accessibility

  • Sylvain, widgets

Action items

  • 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

Agenda and minutes

@gabalafou
Copy link
Contributor Author

Monday, May 13, 2024

Attendees

  • Gabriel

  • Martin

  • Johan

  • Darian

Action items

  • 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

Agenda and minutes

  • 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?

@jasongrout
Copy link
Member

jasongrout commented Dec 9, 2024

The procedure used to copy the information from the Google Doc to this GitHub issue was:
Save in .docx format
Convert to markdown using pandoc:

@gabalafou, I've found the following websites useful in converting from google docs to markdown. For these, I just copy the section from google docs into one of these sites, then it converts that section to markdown. I think it's quite a bit easier than running pandoc for the simple conversion that we need.

HTML->Markdown conversion

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

No branches or pull requests

2 participants