Jupyter Blog - workshops

Navigating the Post-Workshop Fog: a Path to Myst

2026-07-09T15:15:00+00:00

From June 15th to 17th 2026 a Jupyter Workshop took place at Paris-Saclay University : “Demystifying MyST Markdown in education”. The workshop combined presentations in the mornings with collaborative sprints during the afternoons. It has been funded by the Jupyter Foundation and SaclAI-School.

Milestones

Improving documentation and tools for easier deployment even for non-specialists

Freek Pols from Delft University and Brigitta Sipočz form CalTech presented some examples and challenges in publishing courses and documentation at large scales. Angus Hollands, MyST maintainer, made an in depth presentation of Myst and JupyterBook2. Guided tutorials introduced participants to complete a Jupyter Book workflow. The participants learned how to create their first Jupyter Book, and how to publish it.

Text notebooks as first citizens

Marc Wouts and Yahya Heni discussed the path from jupytext to jupyter-plainb to open and execute plain markdown text notebooks directly in Jupyter Lab. Two Jupyter Enhancement Proposals (JEP) has been discussed together with Jupyter Lab and MyST maintainers:

One step at a time

Over 30 issues and pull requests have been opened in the whole Jupyter ecosystem:

documentation items: for example, about text notebooks in jupyterlite or publishing on different hosting solutions;
feature requests: for example, single document feature in JupyterBook2, non-default application to open files in Jupyter Lab;
adopt JupyterBook2 for software documentation: for instance itables and travo.

Sidewalks

The workshop provided the opportunity to continue previous discussions about AI in education: some participants attended the workshop “AI in Jupyter” and were able to pick up the conversation from there.

Relationships between Academia and Open Source Software communities were also topic of conversation: about Open Source Program Offices (OSPOs) and how their action can be connected to education strategies.

Wandering

Collaboration is a matter of trust. That’s why it is still important for people to meet in person and to know each other. It is about exchanging details, like keys to decrypt characters and aspirations. One might discover a shared passion for shoes. Another may finally enjoy long French-style lunch breaks.

When the time comes to resume the path, important steps have already been taken in the right direction.

A Jupyter Workshop: Demystifying MyST Markdown in Education

2026-04-30T15:05:00+00:00

A new Jupyter Workshop is happening June 15–17, 2026 in Orsay, France. Demystifying MyST Markdown in Education is a three-day workshop organized by the Jupyter community, focused on helping science educators adopt Jupyter Book and the MyST document engine for their teaching materials.

What’s it about?

The workshop aims to remove barriers for educators who want to use Jupyter Book and MyST to publish accessible, reproducible pedagogical content. Here are the broad topics of each day of the event:

Teaching use cases and needs : what educators actually need from tools like Jupyter Book.
Contributor tutorials and onboarding : how to get involved with the project.
MyST Markdown as a text representation for Jupyter notebooks : writing and sharing computational narratives.

Attendees will learn how to contribute to the Jupyter Book community, collaborate with maintainers, and advocate for the needs of their users.

Have a look to the workshop agenda and if you have ideas you would like to be discussed there, please share them in the related issue.

Where and how to join

The workshop is hosted by Laboratoire Interdisciplinaire des Sciences du Numérique (LISN) and supported by SaclAI-School at Université Paris-Saclay.
Travel funding is available, apply here for travel funding.

Registration and full details are on the event page.

Thanks

A huge thank you to the whole Jupyter community supporting the event and to the Jupyter Foundation for making it possible.

Jupyter Community Workshops: Early 2026

2025-11-20T13:48:00+00:00

The Jupyter Community Building Working Group is happy to announce the Jupyter Community Workshops selected for funding in early 2026. The dates, venues, participants, and specific agenda for each workshop are being finalized in the near future, so stay tuned for more details.

We applaud all who submitted proposals and each of these selected organizers, who are making a significant commitment to build the Jupyter community. We are very grateful for the generous support of the Jupyter Foundation that makes these workshops possible.

AI in Jupyter: Building Extensible AI Capabilities for Interactive Computing

Zach Sailer (Apple), Jeremy Tuloup (Quantstack), David Qiu (AWS)

This workshop aims to establish consensus around a unified, extensible framework for AI integration across the Jupyter ecosystem by designing shared building blocks, standardized APIs, and protocols that enable seamless integration of AI agents while maintaining the interactive, human-centered experience that defines Jupyter. We will bring together contributors working on AI in notebooks — whether through existing projects, independent extensions, or new ideas — to develop a collaborative roadmap for AI-enabled interactive computing through hands-on demos, collaborative discussions, and focused sprinting sessions.

Roadmap Workshop for JupyterHub and Binder

Arielle Bennett (The Alan Turing Institute), Min Ragan-Kelley (Berkeley Institute for Data Science, UC Berkeley), Raniere Silva (GESIS)

This workshop will be developing and documenting a roadmap for JupyterHub projects. We are inviting maintainers and users to discuss where JupyterHub, repo2docker, and BinderHub should be going and what resources we have to move it forward, and publicly documenting and communicating this plan for improved visibility. The scope will cover a subset of projects across JupyterHub (JupyterHub, Zero to JupyterHub, The Littlest JupyterHub, repo2docker, binderhub, possibly JupyterHealth), depending on which participants we get.

Security Tooling Sprint

Joe Lucas (NVIDIA)

This workshop will survey the open source security tooling ecosystem and find opportunities to integrate select tools to assess and improve the security of Jupyter development and resulting software. These tools may be integrated into existing automation like CI/CD, used for point in time assessments, or potentially during event-driven processes like reviewing vulnerability reports.

Demistify MyST Markdown in Education

Chiara Marmo (Université Paris Saclay — LISN), Nicolas Grenier (Université Paris Saclay — LISN), Kirstie Whitaker (Berkeley Institute for Data Science, UC Berkeley)

The goal of this workshop is to remove barriers for science educators in their adoption of Jupyter Book and the MyST document engine. MyST— part of Jupyter Book, an official sub-project of the Jupyter ecosystem — provides an opportunity to improve the accessibility and replicability of new and existing pedagogical contents. Attendees will leave knowing how they can contribute to the Jupyter Book community, collaborate effectively with maintainers, and advocate for their users’ needs: improving and strengthening the community for all.

Jupyter Community Workshops Are Back!

2025-08-07T20:03:00+00:00

The Jupyter Community Building Working Group is pleased to announce that the next call for proposals for Jupyter Community Workshops is now open through Sunday, September 14 (deadline extension!) for events from October 2025 through February 2026!

We’ve extended the call for proposals to be open through Sunday, September 14.

The majority of Jupyter’s work is accomplished through online collaboration; yet, over the years, we found value in focused in-person workshops. In-person events are particularly useful for high-impact strategic projects, growing the community of contributors, and strengthening collaborations. Jupyter Community Workshops is a series of community-organized events to enable such gatherings.

These workshops are expected to involve up to about two dozen participants over two to four days. Proposals may request a total Jupyter-funded budget of up to $20,000 for reimbursing direct expenses such as travel, lodging, meals, or event space.

In contrast with the broad reach of prior Jupyter Community Workshops, this round of workshops focuses on the Jupyter contributor community. Workshops should include participants who are current or aspiring Jupyter contributors.

The call for proposals for Jupyter Community Workshops is open through Sunday, September 14th, 2025 (deadline extension!)

Learn more about what hosting a Jupyter Workshop entails.

After the submission deadline, proposals will undergo initial review by the Jupyter Community Building Working Group. Accepted proposals will work with the Linux Foundation Events team to develop budget and logistics, followed by a final review.

We are grateful for the support of the Jupyter Foundation and its members that makes our workshops possible. If your organization would like to support this program, please contact the Jupyter Foundation.

Desktop GIS software in the cloud with JupyterHub

2023-08-02T16:23:00+00:00

👋 We are Trey Stafford and Matt Fisher, co-authors of the QGreenland data package’s source code. This year, we had the pleasure of running a hands-on geospatial data and open science QGreenland Researcher Workshop. It was important for attendees to participate in the workshop in a hands-on way while minimizing the negative impacts of installing software, requiring expensive personal computers, and troubleshooting unique computer configurations. We felt a JupyterHub was a good fit for our workshop for this reason, if it could accommodate our need for running QGIS — a desktop application.

In this blog post, we will introduce QGreenland, describe our experience using JupyterHub in the cloud for our workshop’s computing environment, and discuss challenges we overcame to enable our attendees to use QGIS in a cloud graphical desktop environment. Finally, we will highlight some workshop outcomes and discuss opportunities for enhancement based on new developments in the Jupyter ecosystem.

In our workshop, 25–30 international learners (including from Germany, India, France, Canada, Poland, and the United States) used QGIS in a JupyterHub’s browser-based Linux desktop environment to collaboratively test, explore, visualize, and process Earth science data simultaneously with the same user experience they expect from using QGIS on their personal computers! Better yet, getting started was as simple as logging in. Our workshop was a success story not just in education, but also in open source and collaborative development, and we want to share what we learned.

Note the browser tabs at the top of this screenshot; this is a full desktop-based GIS environment running QGreenland in the cloud!

The JupyterHub used by the QGreenland 2023 Researcher Workshop was generously provided by the NASA CryoCloud team, whose mission is to help researchers transition to cloud-based collaboration.

About QGreenland

QGreenland is an open-source Greenland-focused geospatial data package for QGIS, a community-owned graphical Geographic Information System (GIS) platform. Researchers and members of the public leverage QGreenland’s ready-to-use interdisciplinary datasets to do field planning, teach about glaciers, and much more.

QGreenland’s MIT-licensed source code uses community-maintained open software like GDAL and PyQGIS to automate data normalization and populate the QGIS project with important information like data provenance and the order of layers in the QGIS Layers Panel. Check out our documentation to learn more! QGreenland also has a YouTube channel with tutorials produced by CIRES Education and Outreach.

Once QGIS is installed, opening QGreenland is as easy as double-clicking the included “.qgs” file. Here, a representative view of QGreenland v3 alpha in QGIS is displayed with newly updated layers: Arctic sea routes (National Geospatial Intelligence Agency), bathymetric depth (General Bathymetric Chart of the Oceans (GEBCO)), and ice thickness (IceBridge BedMachine Greenland v5) layers.

Based on user research, QGreenland has enabled:

the public to more easily access data gathered by researchers visiting Greenland: “In Greenland, people are often asking, ‘how can we find the data the foreign scientists bring back from Greenland?’ Now we can directly utilize much of it.”
researchers to plan field work: “Being able to use QGreenland at our field station was critical to our research process!”
educators to develop interactive lessons about Greenland and climate change: “…using QGreenland for presentations because it is presentation quality already.”

QGreenland’s 2023 researcher workshop

One of the QGreenland team’s most important forms of direct user interaction and support is facilitating workshops. Most recently, we hosted a 3-day (total of 9 hours) virtual workshop for researchers focused on working with geospatial data in an open science framework. All of the materials covered in the workshop were built using open-source tools and are MIT-licensed and published on GitHub.

A “personal computer” in the cloud

We decided early on that we wanted to use JupyterHub to solve the diverse problems that come with “bring your own device” workshops. We experimented with administering our own JupyterHub on Kubernetes, but the setup overhead was too high for our short workshop. CryoCloud’s JupyterHub enabled us to avoid this overhead and focus on serving our participants. Because the software that comprises CryoCloud is open-source and developed in collaboration with the communities CryoCloud serves, we could directly contribute to curating a computing environment ideal for our participants.

JupyterHub is known for providing access to Jupyter Notebooks via JupyterLab, but it turns out it can also be used to host pretty much any interactive web based application! The jupyter-server-proxy project enables this, and there are additional packages that make running specific applications easier. jupyter-rsession-proxy makes it easy to run RStudio inside JupyterHub, jupyter-vscode-proxy allows running code-server (fully open source self-hosted version of Visual Studio Code) inside a JupyterHub, etc. Pertinent to our use case is jupyter-remote-desktop-proxy, which lets you run a complete Linux desktop environment inside your JupyterHub! This was critical for our workshop, as it allowed us to use QGIS — purely desktop software, not adapted for the web — from inside a web browser. Workshop participants did not need to install anything. This enabled participants to focus on the content of our workshop rather than the logistics of setting up and debugging tools on their varied machines.

The CryoCloud JupyterHub enabled each of our workshop participants to provision their own compute environment (JupyterLab + Linux Desktop) with all of our workshop’s dependencies pre-installed. It also set everyone on equitable footing — someone accessing the workshop on a 10 year old laptop would get the same computing resources as someone on a brand new MacBook Pro.

Challenges scaling QGreenland

The CryoCloud JupyterHub already had jupyter-remote-desktop-proxy and QGIS installed, so we could validate this approach to our workshop quickly. However, to use QGreenland at this scale, we needed to solve a couple of usability problems. The first issue was a user experience problem: the operating system did not have appropriate file type associations for QGIS, so files like the QGreenland project file would not open in QGIS when double-clicked in the desktop file browser. We quickly discovered a solution and integrated it with a simple pull request to the Docker image we were using.

The second problem was a performance problem: QGIS would take several minutes to open QGreenland from the hub’s shared storage drive. After some investigation, it turned out this was due to us loading multiple GB of data from an NFS share! While a long term solution might involve getting QGIS to load data directly from cloud object storage (like S3), we instead decided to go a different route — provision each user a small, fast and temporary Elastic Block Store disk. At the start of the workshop, we provided all users a small script that would copy the dataset from NFS to this faster disk once, and this drastically reduced load times from about 5 minutes to under 3 seconds! You can follow our debugging process on this issue, and find the JupyterHub config used to provision these disks here.

By overcoming these challenges, we created a smooth, intuitive, and performant computing experience for all of our participants, most of whom had never been exposed to this sort of collaborative computing environment.

Outcomes

The workshop participants engaged in small group work to complete various exercises, group discussions, and data scenarios. Each group produced Jupyter Notebooks and GitHub Discussions posts as deliverables. We created an outcomes webpage to summarize our participants’ accomplishments. One highlight was participants’ insightful commentary on FAIR & CARE principles.

Based on these outcomes, we consider our workshop a success. While we put in a significant amount of time creating our materials, CryoCloud’s cloud costs and our time investment in preparing computing resources were relatively small. For approximately 25 people, our cloud costs break down to roughly $1/person/day!

Conclusion

The CryoCloud JupyterHub met our workshop needs and provided a delightful experience for administrators and participants alike, and we are excited for what’s next. JupyterLab 4 and jupyter_collaboration v1.0.0, a real-time collaboration extension, were just announced, and the CryoCloud team is currently working to integrate these new releases into their hub. Real-time collaboration will enable exciting cloud use cases, like small groups working together on the same notebook without a screen share, or organizers providing technical support in a live notebook. We anticipate running this workshop again. We are excited to use JupyterHub again and look forward to experimenting with these new features!

Acknowledgements

Reviewers

In alphabetical order, thanks to Twila Moon, Yuvi Panda, Tasha Snow, and Alyse Thurber for their time contributing to this post!

CryoCloud

Snow, Tasha, Millstein, Joanna, Scheick, Jessica, Sauthoff, Wilson, Leong, Wei Ji, Colliander, James, Pérez, Fernando, James Munroe, Felikson, Denis, Sutterley, Tyler, & Siegfried, Matthew. (2023). CryoCloud JupyterBook (2023.01.26). Zenodo.https://doi.org/10.5281/zenodo.7576602

2i2c

2i2c is a non-profit organization that runs open-source infrastructure for collaborative computing, and maintains the CryoCloud JupyterHub used in this workshop. You can see the complete configuration of this JupyterHub in this public repository.

Jupyter Notebook format workshop outcomes

2023-04-12T17:40:00+00:00

Workshop Social Event challenging our senses

The Jupyter Community Workshop on the notebook file format took place at the Safran Campus near Paris from February 28th to March 2nd. It was a great opportunity to gather various Jupyter stakeholders from private and public affiliations to bootstrap new features for the Notebook file format.

Jupyter Community Workshops are a series of events designed to bring together small groups of Jupyter community members and core contributors for high-impact strategic work and community engagement on focused topics.

Community discussions

The community has lots of ideas to improve the Notebook format. So we split in three smaller groups with the aim of drafting Jupyter Enhancement Proposal (JEP): the markdown group, the text-format group and the cell types group.

The markdown group focused on backward compatible enhancement for the Markdown cells. The discussions focused on two subjects:

The specification of the Markdown flavor (pre-proposal): the goals are to specify which Markdown flavor (e.g. GitHub, CommonMark, MyST,…) is used for the cell source, how to store rendered output for easier cross-compatibility and what is the default Markdown flavor.
The persistence of user expression (pre-proposal): in order to display inline expressions within Markdown cells, the results obtained from the kernel should be stored in the notebook. This proposal aims to define the schema modification to store such information.

The text-format group lays out a specification for an official Jupyter notebook textual format. The discussion went on after the meeting to prepare that proposal.

Finally the cell-types group took the hypothesis of starting from the blank page to create the best Jupyter notebook format building on top of 10-years of experience. The discussion will take time to settle down on a new specification. So if you are interested, join the weekly discussion (see the meeting notes for all the details). In addition to the fully new specification, two backward compatible enhancements have been proposed:

Adding $schema to the notebook format and deprecate the nbformat version keys (see proposal).
Adding extraSchema to the notebook format to optionally extend the schema to specify in particular metadata (see pre-proposal).

Follow-up

Six JEP’s are foreseen from the workshop discussions. But as mentioned earlier, the community has lots of great other ideas (like SQL cells, low-/no-code cells for inputs or visualization). So we would like to encourage anyone interested by any Jupyter enhancement to open issue on the Jupyter Enhancement Proposals repository (see the guidelines for more information).

With the new Jupyter governance in place, the new Software Steering Council is responsible for ensuring those proposals get reviewed and go through the approval process.

Acknowledgements

I deeply want to thank all participants to the workshop that took the time (some of them despite time zone difference) to bring very constructive and thoughtful discussion.

We are really grateful to Bloomberg and Amazon Web Services for their donations to the Jupyter Community Workshops program. This event would not have been possible without their generous support.

We are also grateful to Safran Group for hosting this workshop and the NumFOCUS foundation for helping and mentoring this workshop organization.

Report on the JupyterLite Community Workshop 💡

2023-01-27T13:06:00+00:00

The JupyterLite Community Workshop, held at the OVHcloud headquarters in Paris, France from December 7th to December 9th, 2022, brought together a group of developers, educators, and data scientists to discuss the latest advancements in the Jupyter and Python in the browser ecosystems.

Jupyter Community Workshops are a series of community-organized events that aim to tackle challenging development and design projects, grow the community of contributors, and strengthen collaborations.

One of the main focuses of the workshop was the JupyterLite project, a Jupyter distribution built from the ground-up using JupyterLab components and extensions, allowing for very scalable deployments. It already powers inline consoles and notebooks on the websites of major projects of the PyData ecosystem, such as NumPy, SymPy, PyMC, and many more.

The workshop also gathered the main developers and contributors of the Pyodide, PyScript and Emscripten-Forge projects that enable using Python in the browser.

Highlights of the week

During the workshop, attendees had the opportunity to participate in group discussions, and split into smaller group to work on specific topics:

Pyodide, Emscripten Forge, PyScript, and more generally Python in the browser. This lead to discussions about making WebAssembly a first-class platform for the Python ecosystem, as per https://discuss.python.org/t/make-wasm-a-1st-class-platform-in-the-python-ecosystem/21798
A proof of concept for using the Language Server Protocol in JupyterLite was also presented, showcasing its potential for improving developer productivity: https://github.com/jupyterlite/jupyterlite-lsp
A presentation about Capytale and Basthon and the use of Python in the browser in the French high school system, deployed for 5000+ schools and with more than 200,000 active users per month.
Integrating JupyterLite and Pyodide in thebe, for producing interactive documents in arbitrary websites.
Another topic of work was about using the latest real-time collaboration (RTC) improvements developed upstream in JupyterLab. Enabling RTC on a static JupyterLite website will make it an even more powerful tool for remote teams and online education.

Resources

You can find the detailed notes and relevant links taken during the workshop:

JupyterLite GitHub discussion: https://github.com/jupyterlite/jupyterlite/discussions/920
Jupyter Discourse topic: https://discourse.jupyter.org/t/jupyterlite-community-workshop-2022-paris-report/17255

Acknowledgments

Overall, the JupyterLite Community Workshop provided a valuable opportunity for the community to come together and share their knowledge, ideas, and experiences.

We are really grateful to Bloomberg and Amazon Web Services for their donations to the Jupyter Community Workshops program. This event would not have been possible without their generous support.

We are also grateful to OVHcloud for hosting this workshop, and for their continued support to the Jupyter project and the NumFOCUS foundation.

Jupyter Community Workshop: The notebook file format

2022-12-08T16:09:00+00:00

We are excited to announce the next in-person Jupyter Community Workshop! It will focus on the Notebook file format.

Jupyter Community Workshops are a series of events designed to bring together small groups of Jupyter community members and core contributors for high-impact strategic work and community engagement on focused topics.

The Jupyter notebook file format has been around for 10 years. Its usage has grown in countless fields from teaching to data analysis in production pipelines. A great number of software applications and online services have added support for it.

We want this workshop to be an opportunity for various stakeholders to push forward the format while preserving its reusability in as many applications as possible. We could for example prototype a syntax for injecting variable values in Markdown cells, specify an alternative more textual format like RMarkdown, define the Markdown variant we support,… the boundary is our imagination. By the end of the workshop, we will submit those new specifications as Jupyter Enhancement Proposals to kick start the validation process for enhancing the official notebook format.

The workshop will last three days, with hands-on discussions, hacking sessions, and technical presentations. The goal of this event is to foster collaboration and the sharing of knowledge between maintainers of various platforms supporting the file format, downstream library authors and power users.

The workshop will be held at the Safran Campus in Paris suburb, France from February 28th to March 2nd, 2023. Travel funding assistance is available for attendees from academia and those from groups which are not well-represented within the Jupyter and wider tech community!

Application and all other details can be found in this form.

We are grateful to Safran Group for sponsoring this event. We are also grateful to the sponsors of the Jupyter Community Workshop series, Bloomberg and Amazon Web Services.

Jupyter Community Workshop: Jupyter for Education

2022-12-05T23:37:00+00:00

We are excited to announce the next in-person Jupyter Community Workshop! It will focus on the use of Jupyter for Education.

The event will be held at the Conservatoire National des Arts et Métiers (CNAM) headquarters in Paris, France, from January 24th to January 26th, 2023. Funding for travel expenses is available for attendees from academia and those from groups which are not well-represented in the Jupyter and wider tech community!

Jupyter Community Workshop are a series of community-organized events to tackle challenging development and design projects, growing the community of contributors, and strengthening collaborations.

This workshop will focus on the use of Jupyter for education. The goal is to bring together contributors, and community members to further the development of Jupyter-based tools and practices for education. Given the broad variety of topics relevant to this workshop (pedagogical practices, automatic grading, deployment challenges), we will compose the program based on the attendance. We are also planning an installment of the PyData Paris meetup at CNAM on the 26th of January, with a focus on open-source tools for education.

The workshop will last three days, with hands-on discussions, hacking sessions, and technical presentations. The goal of this event is to foster collaboration and the sharing of knowledge between Jupyter maintainers and downstream library authors and power users.

Should you be interested in joining us for this workshop, please fill this form. A limited number of spots are available for this event.

We are grateful to CNAM for hosting us and to INRIA for supporting this event. We are also grateful to the sponsors of the Jupyter Community Workshop series, Bloomberg and Amazon AWS.

Avion III de Clément Ader, at the CNAM — photo by Roi Boshi for Wikimedia Commons

Report on the Jupyter Community Workshop

2022-11-30T16:40:00+00:00

On behalf of all the participants to the workshop

On June 9–11, 2022, 25 researchers in Quantitative Musculoskeletal (MSK) Imaging met in Maastricht (The Netherlands) for a three-day Jupyter Community Workshop (JCW). Our aim was twofold: to learn tools for open and reproducible research in medical imaging — such as Python, Jupyter Notebook, and ITK—and to create open source software for MSK imaging research. During the three days, we had parallel sessions of tutorials and coding, we hosted speakers to give us inspiration and teach us how to do open and reproducible research, and we discussed the next steps for our community. You can find our workshop page here. In this blog post, we’ll give a detailed breakdown of what happened at the workshop.

Tutorials

As some of us did not have experience with the Jupyter/Python ecosystem, we organized tutorials at various levels of difficulty:

Introduction to the Jupyter ecosystem and Python, and to Pandas and Matplotlib (tutorial material here);
Introduction to the biomedical image analysis and visualization toolkit ITK (tutorial material here).

Computational projects

We split into three groups based on our research interest, and we worked on three computational projects, all of which are now close to publication:

Ciclope: a Python package that processes micro computed tomography images to generate micro finite element models. The software allows the user to create reproducible and fully open-source pipelines for simulating the mechanical behavior of trabecular bone using the finite element method. The Jupyter notebook examples created within the workshop illustrate a complete pipeline from 3D image preprocessing to finite element model generation, solution, and postprocessing.
ORMIR_XCT: a Python package for computing joint space parameters and trabecular bone microarchitecture in second generation high resolution peripheral quantitative computed tomography (HR-pQCT, XtremeCT2, Scanco Medical) images. This package contains all necessary scripts to convert Scanco image data (AIM/ISQ) and perform standard bone and joint analyses that are currently performed using the scanner manufacturer’s built-in software. A Jupyter notebook was developed during this workshop to demonstrate this package’s functionality by perform joint space analysis of a sample finger joint.
MuscleBIDS: a Python package for reading and writing a standardized data format for muscle MR imaging that is based on BIDS. Given the diversity of imaging data formats that exists internationally, such standardized formats are crucial for obtaining reproducible and comparable results. In addition to continuing the development of the tool to support more image contrasts and scanner vendors, a Jupyter notebook was produced, showcasing the current functionality of the package.

Invited speakers

We were excited to have two extraordinary speakers in person at our workshop:

Lorena Barba, who demonstrated the crucial role of open science in solving global problems (e.g. during the COVID pandemic) and showed current and future infrastructure for conducting open science (find her presentation here);
Chris Holdgraf, who talked about current efforts in developing and deploying Jupyter in research and education with different tools and adaptations depending on field requirements, e.g. JupyterLab, Jupyter Book (with MyST), and JupyterHub (find his presentation here).

Community discussion (i.e. what we learned and what’s next)

We dedicated the last session of the workshop to a free exchange of ideas, focusing on what we learned from this experience and defining our next steps:

Workshop organization. The choice of the venue was successful: staying in a modern, tech-style venue with space for work and play got us into the right mindset for coding and learning. On the other hand, we should have organized tutorials and coding sessions sequentially, as the parallel organization did not favor those who were eager to both learn and contribute to the computational projects. In addition, some new members of the community had difficulties finding a way to contribute to the computational projects, which had already been started by some labs;
Community organization. We understood that we needed to structure our community in a more formal way. Thus, we established a Technical Advisory Board, who are going to create guidelines for software homogenization and standardization, and a Community Advisory Board, whose task is to organize and share information about the community, and structure material for newcomers so that they can easily integrate into the community. Finally, we also decided to formally name our community the ‘Open and Reproducible Musculoskeletal Imaging Research’ (ORMIR) community;
Next steps. The Community and Technical Advisory Boards are already working to improve the community website, and create learning material and coding guidelines. We applied for a grant to continue developing our community, and we are looking for more funding opportunities to expand and maintain our projects.

In conclusion, the Jupyter Community Workshop was a powerful collective learning experience that inspired us to start, develop, and continue our journey towards open and reproducible research in quantitative musculoskeletal imaging.

This event would not have been possible without the generous support provided by Bloomberg and Amazon Web Services. If your organization would like to support programs like the Jupyter Community Workshops please contact NumFOCUS at info@numfocus.org

Jupyter Community Workshop: JupyterLite

2022-11-10T15:45:00+00:00

We are thrilled to announce the next in-person Jupyter Community Workshop, which will focus on the JupyterLite project!

The event will be held at the OVHCloud headquarters in Paris, France, from December 7th to December 9th, 2022. Funding for travel expenses is available for attendees from academia and those from groups which are not well-represented in the Jupyter and wider tech community!

Jupyter Community Workshop are a series of community-organized events to tackle challenging development and design projects, growing the community of contributors, and strengthening collaborations.

This specific workshop will focus on the JupyterLite project, a JupyterLab distribution that runs entirely in the browser built from the ground-up using JupyterLab components and extensions. JupyterLite allows for very scalable deployments, and already powers inline consoles and notebooks on the websites of major projects of our ecosystem, such as NumPy, SymPy, Pandas, and many more.

The workshop will last three days, with hands-on discussions, hacking sessions, and technical presentations. The goal of this event is to foster collaboration and the sharing of knowledge between Jupyter maintainers and downstream library authors and power users.

Should you be interested in joining us for this workshop, please fill this form. A limited number of spots are available for this event.

We are grateful to OVHCloud for hosting this event. We are also grateful to the sponsors of the Jupyter Community Workshop series, Bloomberg and Amazon AWS.

Jupyter Community Workshops Update — Current Round Review & Sneak Peek into Round 4

2022-10-12T21:45:00+00:00

We are excited to share an update on round three of the Jupyter Community Workshops!

This comes just as our round 4 workshops are beginning to be announced but this is the perfect time to highlight the successful workshops from our current round. Undeterred by global circumstances, these organizers produced successful workshops both online and in-person. Led by community members, this global event series brought together small groups of people to strengthen the Jupyter community and for high-impact strategic work on focused topics.

Thank you to all those in our community who made these workshops a success. It’s important to recognize the organizers who proposed, planned, and led the workshops, as well as those that supported their efforts and those that attended the gatherings. It is truly inspiring to see everyone come together to strengthen our community and to make the future of Jupyter brighter and more connected.

Many thanks to all those who led a workshop in the current round (listed in chronological order):

Africa Jupyter Community Workshop 2021: (Lead and Organized by Narcisse Mbunzama) The first Africa Jupyter Community Workshop was held in Kinshasa, the capital city of Democratic Republic of Congo on July 22–23, 2021. This event brought together Jupyter developers and contributors together and fostered collaboration, discussion, and contributed to Jupyter notebook for Open science in Africa.
An accessibility audit and roadmap for the Jupyter ecosystem (Lead and Organized by Tania Allard & Isabela Presedo-Floyd)
Building the Jupyter Community in Musculoskeletal Imaging Research: (Lead and Organized by Serena Bonaretti)

Jupyter Community Workshops Round Four

Eight proposals were submitted, each of which represents a tremendous amount of effort and opportunity for community growth. Thank you for your proposals!

Our fourth call for proposals: we are excited to announce the first workshop from this round is scheduled for Oct 18–21, 2023. The Future of Widgets is being organized by Itay Dafna and the in-person event will take place in London. For full details visit the workshop event post!

We’re also happy to share that planning efforts for the other three are already under way! Stay tuned to this blog for more round four announcements of the Jupyter Community Workshops coming in 2022–23.

A special thanks to the financial sponsors of this event series, Bloomberg and Amazon Web Services. If your organization would like to support this program in the future, please contactinfo@numfocus.org.

Jupyter Community Workshop: The Future of Jupyter Widgets

2022-09-20T17:02:00+00:00

After a long break from in-person events, we are excited to announce an in-person Jupyter Community Workshop!

Jupyter Community Workshops is a series of community-organized events to tackle challenging development and design projects, growing the community of contributors, and strengthening collaborations.

ipywidgets 8.0 was released earlier this year, and we are now looking at the future of Jupyter Widgets with versions 9 and beyond of ipywidgets. Some topics we are looking to discuss (non-exhaustive list) include the embedding of widgets in iframes, the next iteration of the Jupyter comm protocol, visual and styling improvements, and the embedding of Jupyter Widgets in contexts outside of Jupyter Notebook/Lab.

The workshop dates are 18th-21st of October. It will take place in the Bloomberg EMEA headquarters in London. Travel funding assistance is available for attendees from academia and those from groups which are not well-represented within the Jupyter and wider tech community!

Registration and all other details can be found in the link below: Jupyter Community Workshop: The Future of Jupyter Widgets (bloomberg.com)

We are really excited for this community workshop and hope you will join us!

We are grateful to Bloomberg for hosting this event. We are also grateful to the sponsors of the Jupyter Community Workshop series, Bloomberg and Amazon AWS.

Jupyter Community Workshops: Call for Proposals

2022-04-26T16:55:00+00:00

We are pleased to announce that the next call for proposals for Jupyter Community Workshops is now open!

The majority of Jupyter’s work is accomplished through online collaboration; yet, over the years, we found value in focused in-person workshops. In-person events are particularly useful for tackling challenging development and design projects, growing the community of contributors, and for strengthening collaborations.

Jupyter Community Workshops is a series of community-organized events to enable such gatherings. See examples of recent workshops here, and stay tuned for updates on the current round of workshops.

We are grateful for the initial and continuing financial support by Bloomberg and Amazon Web Services that makes our workshops possible. If your organization would like to support this program, please contact NumFOCUS.

The fourth call for proposals for Jupyter Community Workshops is open through ~~Sunday, May 22, 2022~~ Monday, June 6, 2022.

Jupyter Community Workshops bring together small groups of Jupyter community members and core contributors for high-impact strategic work and community engagement on focused topics. Events funded in this round would occur no later than April 30, 2023.

These workshops are expected to involve up to two dozen participants over the course of two to four days, in an in-person or virtual format. Depending on the format of the event, proposals may include a Jupyter-funded budget for direct expenses of up to $20,000 to reimburse in-person events or up to $5,000 for virtual events. Direct expenses include, for example, travel expenses, speaker promotional items, video conferencing platform, accommodation, meals and event space. (Please note this is not a grant with overhead or indirect costs.) It is our intent the workshops will include both participants who are core Jupyter contributors and stakeholders, contributors, and potential contributors within the larger Jupyter ecosystem. Participants should be at least 18 years old (i.e., not minors). While not the primary focus of the workshops, it would be highly beneficial to couple the workshop with broader community outreach events, such as sprints, talks, or tutorials at local meetings or conferences. For examples of recent workshops, see some proposals funded in a recent round.

Proposal Process Highlights

Submit initial proposal using this form by ~~Sunday, May 22, 2022~~ Monday, June 6, 2022 (Anywhere on Earth).
Initial Jupyter Community Building Committee (CBC) review (up to a week). Proposal goes to CBC for initial review and feedback. Proposal is either approved or declined.
Budget and Logistics Development (up to four weeks). Jupyter Community Events Manager will support workshop organizers, who will develop a venue/date proposal, detailed budget, event plan, and proposed list of participants.
Final CBC review (up to a week). Proposal presented for final approval to CBC, including final budget, event details, and an estimate of the potential impact of the event. Assuming the budget included in the initial proposal is fully developed and no major changes are proposed, this period may be waived.

The proposal process for these workshops is managed by the Jupyter Community Building Committee, NumFOCUS and the Jupyter Community Events Manager, Gayle Ollington (gayle@numfocus.org). Applications can be completed using the online form and are due by Sunday, May 22, 2022 (Anywhere on Earth). Events should be hosted no later than April 30, 2023.

This initiative is organized by Ana Ruvalcaba, Jason Grout, Sylvain Corlay, and Gayle Ollington.

Jupyter Accessibility Workshops Wrap Up

2022-04-09T04:48:00+00:00

All good things must come to an end, and Jupyter accessibility workshops are no exception. While I may be sad that this series is over, there are many, many things to celebrate and more to look forward to! Let’s break it up into what we did, what we’ve learned, and what we’re going to do in the future.

A quick recap: Jupyter accessibility workshops were a series of events where we connected Jovyans, accessibility experts, and the wider open-source ecosystem for learning and practice in improving accessibility across Jupyter projects. For more specifics on the events individually, visit the January and March event announcements.

What we did

We gathered, we learned, we contributed fixes, all with a dose of laughter. Across three events, our attendees were small in number but mighty, greeting our corner of the internet with

1 fantastic captioner
2 expert accessibility talks from Frank Elavsky and Eric Bailey
3 Saturdays
4 first-time contributors to Jupyter projects
5 Jupyter projects discussed to better understand how we can support the ecosystem’s accessibility needs as a whole
6 hours of events
25 participants, with several friendly faces appearing for more than one event
88 image descriptions written (contributed between Juptyer documentation and Jupyter.org)
~1000 smiles

What a busy season!

We kicked off the events with the knowledge of Frank Elavsky. This included an energetic discussion around the ways that data visualization is already an accessibility accommodation, how to prioritize user feedback and needs, and how to repurpose or reconfigure what we already have to something accessible.

For the second event, our community contributed accessibility fixes to Jupyter projects in the form of image descriptions. This event not only introduces these descriptions — usually alt text — but gives participants a chance to try it out for themselves. Practice always leads to more questions and great conversations, like how to handle long documentation diagrams or when the documentation might benefit from removing an image.

We regrouped in March to learn from Eric Bailey’s vast accessibility experience and to better understand the discussion from a wider perspective. He gave us wonderful examples of accessibility efforts from history, as well as inspiration for how to continue our community’s efforts.

You can find all event resources by date at the following links:

What we learned

With such a rich mix of people and the spotlight on some wonderful speakers, these workshops were privy to discussions at the intersection of digital accessibility and open source. Here are the biggest themes that emerged across all the events.

Guidelines are the floor. not the ceiling. Creating a pleasant accessible experience will require more than sticking to guidelines.
Do it, don’t just read about it. Once we started trying to describe Jupyter images, the best questions and discussions appeared.
It’s all about context. What an image is communicates is determined by what is around it; use this to write good descriptions.
Don’t be afraid mistakes. Because accessibility still isn’t the norm in many open source spaces, expect to be trying, failing, and iterating.
Listen to community members first! If they say communicate accessibility failures that are blocking them, prioritize those efforts when you can.

What’s next

Accessibility in Jupyter spaces is far from over, and we’d love to have you find your new favorite place on the internet here. Just as Jupyter is not a single project, accessibility goes beyond what we covered in the workshops.

We started somewhere designed to be approachable for people of all experience levels, but the next major steps include prioritizing the feedback of disabled people in Jupyter, solving existing issues across projects, and creating methods for sustainable accessibility within our community. These problems won’t be solved with Jupyter knowledge alone, accessibility experience alone, code sorcery alone, documentation brilliance alone, or any other single skill set alone. But they can be solved together. Bring your skills with you, and we can find a place for you here!

If you’d like to get more involved with accessibility efforts, feel free to join our community via

The jupyter/accessibility GitHub repository, a place for gathering cross-project on GitHub.
Jupyter’s Discourse section for accessibility, a place for gathering cross-project separate from Jupyter codebases.
Fortnightly JupyterLab accessibility meetings (found on the community calendar).
For JupyterLab efforts, visit the JupyterLab accessibility GitHub project, where issues and pull requests for are listed.
Open a GitHub issue to propose an accessibility change (please check if a similar issue already exists and add a comment to that one if possible).

Join us for the Jupyter Accessibility Workshops (Part 2)

2022-03-04T15:55:00+00:00

I’m happy to announce the next pair of Jupyter accessibility workshops happening this March! As a part of the third community workshop cycle, these workshops are designed to increase accessibility knowledge within the ecosystem and make Jupyter projects more usable for disabled people.

With community feedback as the inspiration, the following two events will open up discussions around general accessibility foundations and evaluating software with manual testing. If learning, contributing, and making connections in accessibility spaces sounds interesting to you, please join us. No previous experience needed.

What was part 1?

If you noticed the “Part 2” in the title, you might want to visit the blog post announcing the last two workshops for more context.

We also have resources from the last two events available!

What’s up next?

Part 2: March 12 and 19

On March 12, we’ll be joined by Eric Bailey as he introduces us to accessibility and inclusive design strategies. This event will provide some much-needed foundation and common language for our community as we continue to make accessibility a collective priority. People have often asked me how to get started in considering accessibility in their day-to-day work, so we are extremely fortunate to learn from one of the best!

On March 19, it’s sprint time. For this event, we’ll be focused on learning how to manually audit software for accessibility. This skill is great no matter what you spend your time on, whether testing your own work, reviewing someone else’s, or understanding expected accessibility experiences. We’ll practice testing methods as a group before contributing our review to projects across the Jupyter ecosystem. Don’t be intimidated, though, all are welcome at this event; no prior Git or GitHub knowledge is necessary!

To find these events in your timezone, please visit the Jupyter community calendar.

Who can attend these events?

As with the last two, Jupyter accessibility workshops are open to everyone! These events are also entirely remote, so all you need is to be online. Each event is stand-alone, so you can sign up to attend one or all depending on your availability and interest.

Ideally, these events will be attended by a mix of

Jupyter contributors to provide specific insight about the community and projects
People with accessibility skills to advise on the knowledge areas the Jupyter community currently lacks
Newcomers willing to learn and give us feedback on how to make these learning curves better for everyone

Please consider attending if any of these descriptions sound like you!

You can sign up for a Jupyter accessibility workshop individually. You are welcome to attend both events, though you will need to sign up on both forms. Please note that attendance is limited to about 40 attendees per event to make sure we can provide a quality experience with a small event team. (But don’t despair! Recordings of speaking events and notes for all events will be available to all afterwards.)

Where can I get more information?

These events are planned publicly on GitHub; you can explore the accessibility workshop planning repository for more information.

Thanks!

Once again, these events would not be possible without a number of people across the Jupyter community. My thanks wouldn’t be complete without acknowledgement for all Jovyans who have already joined in accessibility efforts, like our wonderful attendees from the last two events whose spirit keeps me inspired every day!

Of course, many thanks to the Jupyter Community Building Committee for supporting funded community events and being a constant presence throughout all our planning adventures. And thank you to the original team that proposed these workshops and made them possible.

Join us for the Jupyter Accessibility Workshops (Part 1)

2022-01-06T18:30:00+00:00

At long last, Jupyter accessibility workshops are here! This is a series of Jupyter community workshops aimed at increasing accessibility awareness within the ecosystem and making Jupyter projects more usable for disabled people.

The goal is to make existing accessibility efforts more prominent across the many Jupyter projects. Much of what we discuss will relate to the Web Content Accessibility Guidelines and how to apply them in open source, scientific spaces where this work has historically been neglected.

These workshops are a series of events proposed for and supported by the third community workshop cycle.

What are these events?

These workshops are a series of four virtual events alternating between learning from experts and contributing to projects.

They’ve been designed by listening to community requests and combining event types to include people of different skills and across communities. In total, they combine Jupyter experts and accessibility experts, learning and action, and working with old friends and making new connections.

Part 1: January 15 and 22

On January 15 we’ll be hearing from Frank Elavsky about how to build inclusive data representations. You can learn more about this work at Chartability, a framework for creating enjoyable and accessible data visualization experiences. I’ve heard so many questions from the community about how to author more accessible content in notebooks and otherwise, so I’m personally thrilled to announce this speaker. (Check the event time in your timezone.)

On January 22 we’ll host a sprint to learn how to write image descriptions and practice by contributing as a team to Jupyter documentation. Image descriptions, usually alt text, are a great place to make use of different skills and learn from one another. Whether you’re a Jupyter community member who wants to learn about accessibility, an accessibility expert who wants to learn about Jupyter, or someone new to both, all are welcome at this event. No prior git or GitHub knowledge necessary! (Check the event time in your timezone.)

Part 2: March

Two more events — a speaker and sprint event — are scheduled in March 2022. Mark your calendars and get excited for more details after the first two events.

Who can attend these events?

Jupyter accessibility workshops are open to everyone! These events are also entirely remote, so all you need is to be online. Each event is stand-alone, so you can sign up to attend one or all depending on your availability and interest.

Ideally, these events will be attended by a mix of

Jupyter contributors to provide specific insight about the community and projects
People with accessibility skills to advise on the knowledge areas the Jupyter community currently lacks
Newcomers willing to learn and give us feedback on how to make these learning curves better for everyone

Please consider attending if any of these descriptions sound like you!

Some events may be more useful to you if you already have certain skills, so be sure to review the sign up forms per-event for specific details.

You can sign up for a Jupyter accessibility workshop per-event. Please note that attendance is limited to about 40 attendees per event to make sure we can provide a quality experience with a small event team. (But don’t despair! Recordings of speaking events and notes for all events will be available to all post-event.)

Where can I get more information?

These events are planned in public on GitHub; you can explore the accessibility workshop planning repository for more information.

You can also read the agendas for the first two events:

Thanks

I want to take a moment to thank some of the many people that have helped make these events happen.

First off, thanks to the Jupyter Community Building Committee for encouraging and supporting the logistics of this and other community workshops. Thank you to the original team that proposed an accessibility workshop for their hard work and help in keeping the proposal going. And, of course, thanks to everyone in the Jupyter ecosystem who have already been committed to accessibility efforts. None of this would be possible alone.

Jupyter Community Workshops 2019 Year in Review

2020-02-24T20:03:00+00:00

Jupyter for Scientific User Facilities and High-Performance Computing (Photo Credit, Fernando Perez)

Intro to Python for Kids, Parents & Teachers Workshop Series

Dashboarding in the Jupyter Ecosystem Workshop (Photo Credit, Lindsey Heagy)

South America Jupyter Community Workshop

2019 was a busy, successful and exciting time for Jupyter Community Workshops! Led by community members, this global event series brought together small groups of people in order to strengthen the Jupyter community and for high-impact strategic work on focused topics.

Our third call for proposals was announced in November of 2019. We’re happy to share that planning efforts are already under way! Stay tuned to this blog for an announcement of the Jupyter Community Workshops to be hosted in the first round of 2020.

Jupyter Community Workshops 2019

Many thanks to all those who led a workshop in 2019 (listed here in chronological order):

Jupyter Server Design and Roadmap Workshop: (Luciano Resende)
Building upon the Jupyter Kernel Protocol (Sylvain Corlay)
Jupyter nbgrader Hackathon/Code Sprint: (James Slack)
Intro to Python for Kids, Parents & Teachers Series: (Tariq Rashad)
Dashboarding in the Jupyter Ecosystem: (Pascal Bugnion, Sylvain Corlay)
Jupyter for Scientific User Facilities and High-Performance Computing: (Rollin Thomas)
South America Jupyter Community Workshop: (Damian Avila)

A special thanks to the financial sponsors of this event series, Bloomberg and Amazon Web Services. If your organization would like to support this program in the future, please contact NumFOCUS.

Jupyter Community Workshops are managed by Jupyter and NumFOCUS contributors: Ana Ruvalcaba, Jason Grout and Walker Chabbott.

Building Upon the Jupyter Protocol Workshop

Report on the Jupyter Community Workshop on Dashboarding

2020-02-14T21:06:00+00:00

This report is long overdue! From June 3rd to June 6th 2019, thirty-five developers from the Jupyter community met in Paris for a four-day workshop on dashboarding with Project Jupyter.

Attendees to the Jupyter Community Workshop on Dashboarding (Photo credit to Lindsey Heagy)

For four days, attendees worked full time on the Jupyter project, including hacking sessions and discussions on improvements to Jupyter components and new development. We were lucky to count a large number of core developers to the project in the group.

Beyond the hacking sessions, each day was concluded with a series of presentations and demos of the progress made during the workshop. In partnership with the PyData Paris team, we had a special installment of the PyData Paris Meetup with

an invited presentation by Emmanuelle Gouillart on Plotly Dash,
a series of lightning talks by attendees of the workshop on their achievements, including a talk by Philip Rudiger on the first release of Panel, and an announcement of the first releases of Voilà and the Voilà Gallery.

We ended the week with a social evening at the QuantStack offices in Paris.

Why a workshop on Jupyter Dashboarding with Jupyter?

The Jupyter ecosystem is used extensively in scientific computing both in academia and industry, and a rich ecosystem of data visualization tools has been developed around the Jupyter widgets frameworks, from geographical data visualization to protein folding simulation.

However, the Jupyter ecosystem still did not provide a means for developers to transition from notebooks to stand-alone web applications that can be accessed by multiple users.

This has been a longstanding request from the community: provide better tools built upon the Jupyter stack to share results with students, peers, or the general public.

These are the challenges that we decided to tackle during that week. The workshop was attended by many Jupyter core developers.

Highlights of the week

Many of the developers spent the week working on the Voilà and Panel projects. Both projects had their first public releases during that week (see the first public announcement of Panel and Voilà).

During this week, a team of participants including Yuvi Panda, Pascal Bugnion, and Jeremy Tuloup iterated on the first version of the Voilà gallery. Several first-time contributors to the widget framework authored example dashboards for the gallery, showcasing their existing work. Yuvi also produced the first deployment scenarii for Voilà on Heruku.
Cheryl Quah, from Bloomberg MC-ed a panel on dashboarding in the Jupyter ecosystem, including lots of questions and comparisons with Dash.
Philip Rudigger started working on a Bokeh/ipywidgets integration for better interoperability between the two frameworks.
Other contributors iterated on creating new Voilà templates, such as voila-vuetify, adding the ability to position Jupyter widgets and outputs in arbitrary location in the dashboard template. Grant Nestor created visual mockups for a UI for creating dashboard layouts in JupyterLab. Grant also helped iterating on logos for the project, and gave a presentation on dynamically loading JavaScript modules in the browser.

Acknowledgments

This event would not have been possible without the generous support provided by Bloomberg, who made this workshop series possible

We are grateful to Société Générale for funding the catering for the workshop.

The hosting of the workshop at CRI was paid for by QuantStack.

The public meetup was organized in partnership with the PyData Paris team.

Finally, we especially thank Ana Ruvalcaba from Project Jupyter for her incredible work on the logistics and finances of the Jupyter Community Workshop series.

Jupyter Community Workshops: Call for Proposals for Jan-Aug 2020

2019-11-12T23:32:00+00:00

Teaching and Learning with Jupyter community workshop. Credit: Richard West.

We are pleased to announce the third call for proposals for Jupyter Community Workshops is now open!

The majority of Jupyter’s work is accomplished through remote, online collaboration; yet, over the years, we have found deep value in focused in-person workshops. In-person events are particularly useful for tackling challenging development and design projects, growing the community of contributors, and for strengthening collaborations. Jupyter Community Workshops is a series of community-organized events to enable such gatherings. For examples of recent workshops, see the proposals funded in the last round.

We are grateful for the initial and continuing financial support by Bloomberg that makes these workshops possible. We are also excited to announce that the program is expanding with additional financial support from Amazon Web Services. If your organization would like to support this program, please contact NumFOCUS.

The third call for proposals for Jupyter Community Workshops is open through Sunday, December 15, 2019.

Jupyter Community Workshops bring together small groups of Jupyter community members and core contributors for high-impact strategic work and community engagement on focused topics. Our vision is that the events funded in this round would occur no later than August of 2020.

We are particularly interested in workshops that explore and address topics of strategic importance for the future of Jupyter. We expect the workshops to involve up to about two dozen participants over a 2–4 day period, and have a total Jupyter-funded budget of up to $20,000 for reimbursing direct expenses such as travel, lodging, meals, or event space (note this is not a grant with overhead or indirect costs). It is our intent for the workshops to include both participants who are core Jupyter contributors, as well as stakeholders and contributors and potential contributors within the larger Jupyter ecosystem. While not the primary focus of the workshops, it would be highly beneficial to couple the workshop with broader community outreach events, such as sprints, talks, or tutorials at local meetings or conferences.

For examples of recent workshops, see the proposals funded in the last round.

Proposal Process Highlights:

Submit initial proposal using this form by Sunday, December 15 (Anywhere on Earth).
Initial Steering Council review (up to a week). Proposal goes to Steering Council for initial review and feedback. Proposal is either approved or declined.
Budget and Logistics Development (up to four weeks). Operations Manager will support workshop organizer who work will develop a venue/date proposal, detailed budget, event plan, and proposed list of participants.
Final steering council review (up to a week). Proposal presented for final approval to steering council, including final budget, event details, and an estimate of the potential impact of the event. Assuming the budget included in the initial proposal is fully developed and no major changes are proposed, this period may be waived.

The proposal process for these workshops is managed by the Director of Jupyter Cal Poly, Ana Ruvalcaba (jupyterops@gmail.com), NumFOCUS and the Jupyter Steering Council. Applications can be completed using the online form and are due by Sunday, December 15 (Anywhere on Earth). Events should be hosted no later than August of 2020.

This initiative is organized by Jason Grout, Paul Ivanov, Brian Granger, and Ana Ruvalcaba.

Jupyter Blog - workshops

Navigating the Post-Workshop Fog: a Path to Myst

Milestones

Improving documentation and tools for easier deployment even for non-specialists

Text notebooks as first citizens

One step at a time

Sidewalks

Wandering

A Jupyter Workshop: Demystifying MyST Markdown in Education

What’s it about?

Where and how to join

Thanks

Jupyter Community Workshops: Early 2026

AI in Jupyter: Building Extensible AI Capabilities for Interactive Computing

Roadmap Workshop for JupyterHub and Binder

Security Tooling Sprint

Demistify MyST Markdown in Education

Jupyter Community Workshops Are Back!

Desktop GIS software in the cloud with JupyterHub

About QGreenland

QGreenland’s 2023 researcher workshop

A “personal computer” in the cloud

Challenges scaling QGreenland

Outcomes

Conclusion

Acknowledgements

Reviewers

CryoCloud

2i2c

Jupyter Notebook format workshop outcomes

Community discussions

Follow-up

Acknowledgements

Report on the JupyterLite Community Workshop 💡

Highlights of the week

Resources

Acknowledgments

Jupyter Community Workshop: The notebook file format

Jupyter Community Workshop: Jupyter for Education

Report on the Jupyter Community Workshop

Tutorials

Computational projects

Invited speakers

Community discussion (i.e. what we learned and what’s next)

Jupyter Community Workshop: JupyterLite

Jupyter Community Workshops Update — Current Round Review & Sneak Peek into Round 4

Jupyter Community Workshops Round Four

Jupyter Community Workshop: The Future of Jupyter Widgets

Jupyter Community Workshops: Call for Proposals

Proposal Process Highlights

Jupyter Accessibility Workshops Wrap Up

What we did

What we learned

What’s next

Join us for the Jupyter Accessibility Workshops (Part 2)

What was part 1?

What’s up next?

Part 2: March 12 and 19

Who can attend these events?

How do I sign up?

Where can I get more information?

Thanks!

Join us for the Jupyter Accessibility Workshops (Part 1)

What are these events?

Part 1: January 15 and 22

Part 2: March

Who can attend these events?

How do I sign up?

Where can I get more information?

Thanks

Jupyter Community Workshops 2019 Year in Review

Jupyter Community Workshops 2019

Report on the Jupyter Community Workshop on Dashboarding

Why a workshop on Jupyter Dashboarding with Jupyter?

Highlights of the week

Acknowledgments

Jupyter Community Workshops: Call for Proposals for Jan-Aug 2020

Proposal Process Highlights: