Michał (Mike) Krassowski

@krassowski.bsky.social

Maintainer of JupyterLab. DPhil in omics/endometriosis - I miss research. Thinking how to leave the world a better place.

If you are using AI to open PRs without considering previous reviews and ignoring PR templates, you are not adding value. The point of good first issues was to let humans learn the contribution flow, not for AI to score virtual points.

#JupyterLab 4.6.0a3 enhances the file browser: - more breadcrumbs are shown to fill space - name sort order can be changed - you can 'Open in Terminal' from context menu Also: - you can paste code cells without outputs - before deleting a cell from cell toolbar, you will see a confirmation dialog

BildBildBildBild

JupyterLab 4.5 and Jupyter Notebook 7.5 are here! 🎉 Highlights 🎁 - Enhanced notebook scrolling behavior - Native audio and video support - New Terminal search - Debugger, Notebook and File Browser improvements Check out the blog post to learn more! blog.jupyter.org/jupyterlab-4...

JupyterLab 4.5 and Notebook 7.5 are available!

JupyterLab 4.5 has been released! This new minor release of JupyterLab includes 51 new features and enhancements, 81 bug fixes, 44…

blog.jupyter.org

I used to think the friction in community OSS/corporate dynamics comes from a difference in culture between organizations and teams. The more I see the same team flip between amazing and questionable contribution trajectory the more I think this comes down to changing internal direction/incentives.

There are two things you should not remove when transitioning to a metapackage: integration tests and documentation. In fact, the transition should double down on these two things as they are critical to ensure the packages integrate well, and that discoverability is preserved.

A mismatch of expectation on what irks #OSS maintainers: I saw folks really worry about removing a feature I contributed due to lack of bandwidth to port it to new version - but this was absolutely fine! I saw them remove tests and ignore my warning against it - and this is what in fact made me sad.

🚨 The deadline for Jupyter Community Funding Proposals (blog.jupyter.org/your-ideas-o...) has been extended to October 5th, 2025 ( by one week). We've got a few great-looking proposals in the works (github.com/orgs/jupyter...), so you've all got another 7 days to write!

Your Ideas, Our Support: Jupyter Community Call For Funding Proposals

The Jupyter Executive Council and Jupyter Foundation are pleased to announce a call for proposals for the Jupyter community. Visit the…

blog.jupyter.org

You’re invited to join the next Jupyter Community Call on September 4th, 2025. Get updates from across the Jupyter ecosystem, hear talks from community members, and get involved. It’s a great way to connect, contribute, and engage! The Zoom link in our blog post: blog.jupyter.org/jupyter-comm...

Jupyter Community Call: September 2025

Hey Jovyans, we want to learn about the great things you’re doing with Jupyter! The Community Building working group is holding an open…

blog.jupyter.org

Have a great idea for Project Jupyter? We want to help you build it! 🚀 The Jupyter Foundation is now accepting funding proposals from all community members. This is your chance to make a direct impact. Learn how to apply! 👇 blog.jupyter.org/your-ideas-o...

Your Ideas, Our Support: Jupyter Community Call For Funding Proposals

The Jupyter Executive Council and Jupyter Foundation are pleased to announce a call for proposals for the Jupyter community. Visit the…

blog.jupyter.org

👋 JupyterLab and Jupyter Notebook users: What's one thing you'd love to see improved in JupyterLab, Jupyter Notebook, or JupyterLite? The team is prepping the upcoming 4.5/7.5 releases and wants to tackle some usability issues. Drop your feedback below, this will help prioritize what gets fixed!👇