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.

Sign up for GitHub

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

Jump to bottom

Weekly Dev Meetings: Jan-Jul 2021 #117

Closed
jasongrout opened this issue Jan 20, 2021 · 34 comments
Closed

Weekly Dev Meetings: Jan-Jul 2021 #117

jasongrout opened this issue Jan 20, 2021 · 34 comments

Comments

@jasongrout
Copy link
Contributor

jasongrout commented Jan 20, 2021 •
edited by afshin
Loading

Here is a record of the agenda/minutes for our weekly meeting. Everyone is welcome to join.

Let's avoid using this thread for discussion. If you'd like to discuss something in the minutes, open a separate issue and reference this thread.

Meeting Notes
@jasongrout
Copy link
Contributor Author

06 Jan 2021 Weekly Meeting

@jasongrout
Copy link
Contributor Author

13 Jan 2021 Weekly Meeting

  • Isabela

    • How is everyone?
    • #9335 first step PR for meeting accessible color contrast standards. I'm looking for review and/or next steps needed.
    • The JupyterLab accessibility meeting will be happening right after this. All are welcome!
    • The Jupyter community call is coming up in two weeks (Jan 26 (your timezone)). Sign up to share on the agenda. Does anyone want to share about 3.0?
    • I'm adding the proposed settings UI to the items for further discussion. Just want to check in about it.

  • Eric

  • Brian

    • Happy new years :-)
    • New RTC funding for QuantStack

  • Jason

  • Alex

    • Working on updating nbdime and git extensions to 3.0, the git extension work needs review and feedback. nbdime PR git PR
    • Settings UI work is still on my back burner, others are still welcome to jump in and start the work without me.

  • Discussion

@jasongrout
Copy link
Contributor Author

20 Jan 2021 Weekly Meeting

  • Alex

    • nbdime and git extension betas supporting 3.0 have been released
    • Elyra 2.0 should released in the coming days (supporting 3.0)

  • Isabela

    • January's community call is next Tuesday at 9am Pacific (your timezone)! Sign up on the agenda if you want to present.
    • JupyterLab accessibility meeting is next Wednesday!

  • Jason

    • Continuing to work on 3.0 regressions, cookiecutters, etc.

  • Martha

    • #9622 Accessibility PR for aria roles
    • #9487 Different accessibility PR, looking for feedback

  • Eric

  • jd41

    • brief update on directed acyclic graph-like notebook vs dataflow notebook (see last week's meeting)

  • Discussion

@Zsailer Zsailer pinned this issue Jan 20, 2021
@jasongrout jasongrout mentioned this issue Jan 21, 2021
Closed
4 tasks
@jasongrout
Copy link
Contributor Author

27 Jan 2021 Weekly Meeting

  • Isabela

    • How is everyone?
    • Is anyone interested in guest hosting a community call? It's probably good for sustainability if it isn't all known by one person.
    • JupyterLab accessibility meeting is directly after this one!
    • @jtpio and I are trying to help close the JLab 3.0 issue. Come join us!

  • Gonzalo

  • Jeremy:

  • Jason

    • A few more bugfixes for 3.0, which still need to be released (#9674 needs review still)

  • Eric

  • Discussion

@jasongrout
Copy link
Contributor Author

3 Feb 2021 Weekly Meeting

Discussion

  • Introductions
  • Status of Update for JLab 3.0 mimerender-cookiecutter-ts#21 ?
  • Keyboard shortcuts for moving cells (Add default shortcuts for moving cells jupyterlab#9031) (Krishna)
  • 4.0 Planning
    • Google Form Version
    • Please provide issues or a JEP (JupyterLab enhancement proposal) for each potential roadmap item
    • This will be due by the 17 Feb dev meeting so we can choose how to move forward with 4.0 planning
    • The goals of the planning process are:
      • Provide a way for developers to communicate, coordinate, and consolidate development of major features
      • Message to the public what major features we are working on for 4.0
      • Commit to developers working on features that they are in scope for 4.0
      • Establish a timeline for release phases (alpha, beta, rc, final)

@jasongrout
Copy link
Contributor Author

jasongrout commented Feb 10, 2021 •
edited by telamonian
Loading

10 Feb 2021 Weekly Meeting

Further Discussion

  • A part of making JupyterLab accessiblity efforts sustainable will be adding relevant tests to JupyterLab. There's nothing to show right now, but I wanted to give an early heads up since this will eventually affect all contributors. #9742 (Isabela)
  • How do people manage the high amount of issues? How do find the things that are relevant to you as they come in? (see also #9714)
  • Reminder that the 4.0 Planning items are due by next Wednesday. Please make sure each item has a link elaborating on that specific item (like to an issue, etc.)
  • How to not have RTC become a project collaboration problem
    • Hopefully this discussion can happen on the bi-weekly RTC call

@jasongrout
Copy link
Contributor Author

17 Feb 2021 Weekly Meeting

  • Survey Initiative [Layne, Luciano, Isabela, Brian, Tim]

    • Opening statement. Characterize threats. Why action needed? Ran survey to get info to guide actions. Half baked recommendation.
    • Aggregate survey trends.
    • Use cases by frequency. Satisfaction by use case versus competitive tools.
    • Git permissions for github.com/jupyter/surveys
      • From chat, submit pr and will be merged
    • Future: which user segments to learn more about?
      • [a] the disatisfied & disenchanted, [b] JupyterHub & collaborators, [c] pain area (e.g. scale, data wrangle) vs competition.
    • Future: keyword analysis of open text responses.

  • Isabela

    • February's Jupyter community call is next Tuesday, the 23rd at 9am Pacific (your timezone). You can find more info on the Jupyter Discourse. Hope to see you there!

  • Eric and Pierre

    • RTC Demo - Collaborative Notebook and FileEditor
      • Using Collaborative ModelDB
      • Collaborative Kernel Manager for next Monday
      • Multiuser with GitHub Authentication (pluggable)
    • PR on its way
      • Better to first align with other existing PR (cfr backwards compatibility + open to other CRDT libraries)?
      • Please join next Jupyter RTC meeting on Monday 22 Feb 12:30 EST (Local time) https://github.com/jupyterlab/rtc
        • Backwards compatible (events structure/content, uses existing collaborators classes) => Demo with LSP extension is planned.
        • Custom ModelDB for pluggable RTC algorithms
          • Automerge is used for now
          • Y.js can be added
      • Will also include
        • jupyterlab-iam (identity and access management) providing permissions on kernels for the collaborators
        • jupyterlab-observables-extension: to allow users to choose his collaboration provider

  • MJ

    • I just want to say thanks to you folks for the quick fix for the Cache-Control header issue #9762 I brought up last week.

Discussion

  • Status of file openers without content fetching: Allow file openers by to accept URLs jupyterlab#5885 and Add null fileformat jupyterlab#7596
  • Scipy 2021 Virtual Conference talk deadline: 22 Feb
    • Martha and Alex are planning to submit a tutorial
    • Alex submitting a talk about extensions (including lab 3.x extensions)
    • Layne might submit talk about survey findings
    • Max submitted a proposal about accessibility work in JupyterLab
    • Anyone else wanting to collaborate, please open an issue on the team compass
  • JLab 4.0 Planning items
    • Deadline extended to account for more info being available around the survey. To have a helpful discussion, all proposals need to have all columns filled out before next week's meeting (Wednesday the 24th).
    • Primary outcome for the roadmapping:
      • Commit to developers that something is in scope for 4.0
      • Communicate to public what we are planning for 4.0
      • Decide a timeline for release milestones (alpha, beta, rc, etc.)

@layne-sadler
Copy link

@jasongrout i followed through in submitting a scipy abstract.

@jtpio
Copy link
Member

jtpio commented Mar 5, 2021

24 Feb 2021 Weekly Meeting

  • Isabela
    • Congrats on closing the JupyterLab 3.0 issue! It makes me so happy to see that wrapped up. Special thanks to @jtpio for finishing the last to-dos.
    • Recent Jupyter survey data has been submitted as jupyter/surveys #7.
    • We need a private place to keep the emails collected for follow-up interviews. Can we get it in the rumored NumFocus-run Jupyter Dropbox?
      • We have official Google Drive shared drives through NumFOCUS, the team can work with Brian to get access.
  • Layne (2min)
    • Aggregated & ranked (pains, use cases, competitive str./weak) to facilitate roadmap decision making. Ranked pain points to help w roadmap #121 .
    • Comparing top use cases and competition indicates where to focus long term -> call for brainstorm on "documenting research."
  • Backport initial page load performance improvements to JL 1.2.x jupyterlab#9870

Jupyter roadmap discussion (Brian to attend starting at 9:15am)

Discussion

@jtpio
Copy link
Member

jtpio commented Mar 5, 2021 •
edited
Loading

03 Mar 2021 Weekly Meeting

Additional Discussion

  • JupyterLab 4.0 roadmap, continued

@jtpio jtpio mentioned this issue Mar 5, 2021
Open
@jtpio
Copy link
Member

jtpio commented Mar 22, 2021

10 Mar 2021 Weekly Meeting

@jtpio
Copy link
Member

jtpio commented Mar 22, 2021

17 Mar 2021 Weekly Meeting

Additional Discussion

  • JupyterLab 2.3.0 final?
  • Top level jupyterlab/.github repo? See conversation from last week about JupyterHub's repo - open a team compass issue. Question - can a repo override the org-wide settings for issue templates? Jason says that the presence of a .github directory completely overrides the org-wide values
  • Roadmap discussion continued

@jtpio
Copy link
Member

jtpio commented Mar 25, 2021

24 Mar 2021 Weekly Meeting

Additional Discussion

@jtpio
Copy link
Member

jtpio commented Apr 8, 2021

31 Mar 2021 Weekly Meeting

  • Luciano

    • Do we have any updates or news around other kernels supporting Lab Debugger/DAP?
    • Any progress on NBDime proper release? I believe this is blocking JupyterLab-git extension go out of beta and other dependent extensions. It also sort of blocks conda based releases
      • Vidar mentioned he is planning to get things moving starting next week

  • Max

  • Steve

    • Enabled the welcome and request-info bots across the org, if you're wondering why they show up

  • Tony

    • CZI Accessibility proposal submitted
    • Accessibility working meeting after this.

  • Gonzalo

    • Jlab perf tests in PRs in main repo:
      • Create an NPM package with the needed assets for this and a python package with the scripts?
      • Move the needed scripts and assets to JupyterLab main repo?
      • Leave them on jupyterlab/benchmarks and do some git cloning work?

  • Kevin

    • Update on Jupyter RTC

Additional Discussion

@jtpio
Copy link
Member

jtpio commented Apr 8, 2021

07 April 2021 Weekly Meeting

Additional Discussion

@jtpio
Copy link
Member

jtpio commented Apr 19, 2021

14 April 2021 Weekly Meeting

  • Steve
  • Eric
    • Looking for community feedback on React.js options to solve performance issues.
  • Isabela
    • Jupyter community call is in two weeks! Visit Discourse for more information. The unofficial prompt is tutorials, how-to's, and things you wish you knew when starting in the community.
  • Tony

Additional Discussion

@jtpio
Copy link
Member

jtpio commented Apr 22, 2021

21 April 2021 Weekly Meeting

  • Steve
  • Darian
  • Martha
  • Vidar
    • Q: Is it possible to have CDN based federated module loading?
      A: Yes, but requires disting of build outputs to the CDN + ensuring that the URL matches up with the request URL. There shouldn't be any processing of these files on the server.
    • Q: How comfortable are we with storing deploy-level secrets for automated deploy ? What are actions we can take to ensure there is a manual gating for releases to help harden things ?
      A: We can have a manual GHA job that deploys versions, where the deploy step that has access to the secret does not use any external actions.
  • Luciano
    • nbdime and git extensions now have GA releases supporting Lab 3.0. Thank you all for helping with that. That unblocked Elyra to push its packages to conda-forge.
  • Ross
    • Language Packs - Chinese + Japanese

Additional Discussion

@jtpio
Copy link
Member

jtpio commented Apr 29, 2021

28 April 2021 Weekly Meeting

Additional Discussion

@jtpio
Copy link
Member

jtpio commented May 6, 2021

5 May 2021 Weekly Meeting

  • Isabela

    • What are the plans to convert all the roadmapping work and documents used in these meetings to the 4.0 roadmap issue?
      • Next steps are to get names on the empty parts of spreadsheet via the meeting Darien is coordinating with people looking for projects to contribute to (jupyterlab/team-compass #124).
      • Should be linked on main JupyterLab 4.0 issue.
      • Once all areas are filled out, this needs to be made markdown and tied to the main issue for reference.
    • Thanks to Jeremy for running this meeting!

  • Frederic

    • Hello
    • Discussion on cell toolbar #9733 - does it make sense to bring the cell toolbar extension in core?
    • Menu items filtering #10091 - first trial by explicitly listing command ids to hide thanks to the isVisible property PR. The trouble comes from the need to modify the commands where they are defined. So an approach inside the lumino Menu sounds more generic. If some have suggestions or comments that would be nice.

  • Maggie and MJ

    • Questions about jupyterlab build process https://jupyterlab.readthedocs.io/en/stable/user/directories.html?highlight=dependency#jupyterlab-build-process
      • How does it resolve sub-dependencies versions of installed extensions? It seems it always installs the newest dependencies available that meets the semver range in the extension's package.json, instead of by package-lock or yarn.lock. Is it expected or is there specific reason?
        • 2 layers: application level (lumino) get resolved at the top level. other dependencies, use webpack to find the compatible version. The package-lock in extension itself is ignored.
        • JL v1 uses webpack module resolution by default. JL v3 has custom settings under builder subfolder.
      • Any recommendation how extension can specify specific sub-dependency versions to be installed? We tried to pin the version in "dependencies" and "resolutions" in extension's package.json, but didn't help.
        • Since JL v1 doesn't have custom way to resolve dependencies, we should look more into general webpack documentations and solutions.

  • Max

  • Kevin

    • Let's merge the RTC PR
      • We need more feedback / people trying out he PR in practice.
      • There is only one smaller issue that we need to fix before the PR (fixed it)

Additional Discussions:

@jtpio jtpio mentioned this issue May 6, 2021
Closed
@jtpio
Copy link
Member

jtpio commented May 20, 2021

12 May 2021 Weekly Meeting

@jtpio
Copy link
Member

jtpio commented May 20, 2021

19 May 2021 Weekly Meeting

Additional Discussion

@jtpio
Copy link
Member

jtpio commented May 28, 2021

26 May 2021 Weekly Meeting

  • Darian

    • Next week's call: let's try an RTC binder for weekly meeting minutes

  • Steve

    • Cutting an alpha release during this meeting - v3.1.0a10
    • Update list of maintainers?
      • I propose the following folks to add:
        • Michał Krassowski, University of Oxford (general development, extensions).
        • Gonzalo Peña-Castellanos, QuanSight (general development, i18n, extensions).
        • Frédéric Collonval, QuantStack (general development, extensions).
        • Isabela Presedo-Floyd, QuanSight Labs (design/UX).
        • Jeremy Tuloup, QuantStack (general development, extensions).
      • We could also consider moving some folks to emeritus status (but they can update themselves whenever they'd like to return to a maintenance role)
      • Update Maintainer List jupyterlab#10300
    • Lumino is now compatible with jupyter_releaser! JupyterLab is the final "hard" target

  • Frederic

    • Build menu from settings -> translation issue

  • Mike

    • Completer refactor: on LSP jupyterlab-lsp#600
      • create a new ICompletionProvider interface
      • should it go to @jupyterlab/completer-extension or to a new package? 3.1 or 4.0?

  • Max

    • New v0.0.6 release of jupyter-fs and the new filebrowser UI
      • first release that includes new tree-finder-based browser UI
      • first jlab 3.x compatible release
      • supports inter-browser copy/paste
        • can copy from an S3 bucket and paste into local filesystem

  • Martha

    • #10260 Collapsable headings in notebooks PR ready for more review - particularly code review

  • Layne (if time allows)

    • Jupyter = NumFOCUS UI.

    • Dask = NumFOCUS at scale (pd, np, sklearn, generic Python objects).

    • Integration of Dask UI/admin/config in Jupyter core. Ever been discussed?

    • Dask platform validated in success of commercial platforms Saturn Cloud & Coiled.

    • High Jupyter usage for pipelines, but prefer alternative tools for pipelines.

      • "I want to scale but don't know how" theme of survey.
      • Dask already as popular as Spark.

    • Extension: https://github.com/dask/dask-labextension (Steven, Brian contributors)

Additional Discussion

@jtpio
Copy link
Member

jtpio commented Jun 10, 2021

2 June 2021 Weekly Meeting

@jtpio
Copy link
Member

jtpio commented Jun 10, 2021

9 June 2021 Weekly Meeting

Additional Discussion

  • ZenHub demo (Gonzalo)
  • 3.1 triage, continued

@jtpio jtpio mentioned this issue Jun 10, 2021
Open
@isabela-pf isabela-pf mentioned this issue Jun 11, 2021
Closed
@isabela-pf isabela-pf mentioned this issue Jun 18, 2021
Open
@afshin
Copy link
Member

afshin commented Jun 23, 2021 •
edited by fcollonval
Loading

16 June 2021 Weekly Meeting

@afshin
Copy link
Member

afshin commented Jun 23, 2021 •
edited by fcollonval
Loading

23 June 2021 Weekly Meeting

Discussion

  • 3.1 timeline: 21 open PRs, 44 open issues, scipy starting in 2.5 weeks

Introductions

  • Andrii Ieroshenko / Cal Poly Jupyter Notifications/To-Do Extensions

    • Github username: @andrii-i
    • Call for volunteers to participate in interviews for Jupyter Notifications system user research (please contact if interested!)

  • Harshit Mittal / Cal Poly Jupyter Notifications/To-Do Extensions

@jtpio jtpio mentioned this issue Jun 24, 2021
Closed
@afshin
Copy link
Member

afshin commented Jun 30, 2021

30 June 2021 Weekly Meeting

  • Isabela

    • Can I get review on a Jupyter community call notes PR? And is there a better group or meeting to reach out to in the future?
    • Is the Jupyter blog still accepting guest blog posts? If so, do I still point people to the mailing list for that? https://blog.jupyter.org/
      • There's no one actively handling the blog right now, so it's been defaulting to the Steering Council temporarily.
    • Accessibility meeting is today fifteen minutes after this call!
    • Mentioning the interest in CodeMirror 6 in JupyterLab one more time.

  • Mike

    • JEP on Language Server Protocol enhancement-proposals#72
    • Version detection in extensions for language packs jupyterlab-translate#4?
      • Perhaps allow a field in package.json or pyproject.toml for this configuration and we can use that if it is available, else fall back on auto-detect methods

  • Frédéric (or Steve)

  • Steve

    Additional Discussion

    • Any more 3.1 triage - make sure all issues have an assignee or get bumped

@jasongrout
Copy link
Contributor Author

7 July 2021 Weekly Meeting

Updates

  • Luciano

    • Sort of Summer of Code experience for JupyterLab? Possible available funds for 2 students for 3 months. How to proceed?
    • Jupyterlab-lsp moving to JupyterLab github org?

  • Frederic

    • Turn on Discussions on GitHub repo to reduce the issue stack?

      • Is there some tags to automatically convert issue to discussion (like Reference milestone, Question label)

      • For now, does not seems enough useful. But we should add direct links to gitter and discourse when opening a new issue (look at JHub and ipywidgets for example).

      • It would probably be helpful to have an actual survey of issues, say in the last 6-12 months, that are support issues. How many did we have? What broad categories were they? How were they handled (or ignored?)? Did they end up getting turned into PRs that changed things? That would help us make decisions backed by evidence.

  • Isabela

    • Final feedback on updated skiplink so it gets into 3.1?
      • Missing a space after private keyword here and the calling of the method here should use this._createSkipLink
    • If you have things you'd like to propose are included at the SciPy Tools plenary, please add info to discourse

  • Steve

  • Nick

  • Mike

    • Improve the user experience and awareness about prebuilt extensions #10554
      • prebuilt preferred, "federated" is outdated
      • can distrbute prebuilt using npm in princpiple
      • can extract the package from NPM/PyPI/Conda package and put in the the right path
        • but pip gives us a solver which helps with solving dependencies

  • Jason:

    • Activity Bar as a new UI term in JupyterLab. If you have comments about this, please post on the issue.

Additional Discussion

@jtpio
Copy link
Member

jtpio commented Jul 14, 2021

14 July 2021 Weekly Meeting

This was referenced Jul 20, 2021
Merged
Closed
@isabela-pf isabela-pf mentioned this issue Jul 21, 2021
Merged
@jtpio
Copy link
Member

jtpio commented Jul 21, 2021 •
edited
Loading

21 July 2021 Weekly Meeting

Individual updates

  • Frederic
    • Remove JupyterLab issue templates to use the one of the organization: #10649
    • Draft JupyterLab issues analysis: notebook #127

Additional discussion

  • 3.2 Release
    • Gonzalo wants to be the release manager and get a couple features in. Are there any suggestions for additional features?
      • Frederic: Toolbar customization #10469, rich variable rendering #10299 and restart and debug #10462 PRs would be nice to get in 3.2
      • Mike: set numberCellsToRenderDirectly to Inf for 3.1 and enable with lower number in 3.2?
    • Path forward: make an issue tracking 3.2 with suggested features and timeline

@adpatter adpatter mentioned this issue Jul 28, 2021
Closed
@afshin
Copy link
Member

afshin commented Jul 28, 2021

28 July 2021

Attendees

Name Organization GitHub Favorite Animal
A. T. Darian Two Sigma @afshin 🐻
Ryan Cooper UConn @cooperrc turtle
Layne Sadler AIQC @aiqc beaver
Tony Fast Quansight @tonyfast sad faced puppy dogs
Steve Silvester Apple @blink1073 sloth
Martha Cryan IBM @marthacryan giraffe
Vidar T Fauske JPMorgan Chase @vidartf Cassowary
Karla Spuldaro IBM @karlaspuldaro cat
Piyush Jain AWS @3coins
Loic Huder ESRF @loichuder 🐢
Frederic Collonval QuantStack @fcollonval
Isabela Presedo-Floyd Quansight Labs @isabela-pf fox
Jessica Xu Quansight @jess-x

Agenda

Additional discussion

  • 3.2 release of JupyterLab
    • Let's create a 3.2 milestone and migrate 4.0 issues that are relevant over to it
    • Let's create a 3.2 project

@afshin
Copy link
Member

afshin commented Aug 4, 2021 •
edited by fcollonval
Loading

JupyterLab Weekly Call - August 4, 2021

Attendees

Name Organization GitHub Favorite Color
A. T. Darian Two Sigma @afshin pink
William Stein SageMath/CoCalc @williamstein White
Vidar T Fauske JP Morgan Chase @vidar Ultramarine
Steve Silvester Apple @blink1073 fuchsia
Loïc Huder ESRF @loichuder midnightblue
Martha Cryan IBM @marthacryan yellow
Isabela Presedo-Floyd Quansight Labs @isabela-pf orange!
Frederic Collonval QuantStack @fcollonval
Jessica Xu Quansight @jess-x
Nick Bollweg Georgia Tech @bollwyvl @nrbgt #000, also #chucknorris
Alex Bozarth IBM @ajbozarth Black
Piyush Jain AWS @3coins blue
Karla Spuldaro IBM @karlaspuldaro scarlet
Mike UOXF/own behalf @krassowski coffee
Gonzalo Quansight, inc @goanpeca blue
Kevin Bates IBM @kevin-bates Dodger Blue

Agenda

Additional Discussion

Links

  • settings UI

  • conda-forge multiple outputs

@isabela-pf isabela-pf mentioned this issue Aug 4, 2021
Closed
@jupyterlab jupyterlab deleted a comment from afshin Aug 12, 2021
@fcollonval
Copy link
Member

ℹ️ Meetings notes for August to December 2021 are in #128

@meeseeksmachine
Copy link

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

https://discourse.jupyter.org/t/dag-based-notebooks/11173/2

@jtpio jtpio unpinned this issue Dec 8, 2021
@fcollonval fcollonval mentioned this issue Sep 7, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@afshin @jasongrout @jtpio @fcollonval @meeseeksmachine @layne-sadler