<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>Jupyter Blog - Jason Grout</title><link href="https://jasongrout.github.io/medium-archive/pelican/" rel="alternate"/><link href="https://jasongrout.github.io/medium-archive/pelican/feeds/author-jason-grout.atom.xml" rel="self"/><id>https://jasongrout.github.io/medium-archive/pelican/</id><updated>2026-08-22T20:41:00+00:00</updated><subtitle>The Project Jupyter blog: news, releases, and community stories, archived from blog.jupyter.org.</subtitle><entry><title>Jupyter User Survey</title><link href="https://jasongrout.github.io/medium-archive/pelican/posts/2026/jupyter-user-survey/" rel="alternate"/><published>2026-06-18T15:04:00+00:00</published><updated>2026-06-18T15:04:00+00:00</updated><author><name>Jason Grout</name></author><id>tag:jasongrout.github.io,2026-06-18:/medium-archive/pelican/posts/2026/jupyter-user-survey/</id><summary type="html">&lt;p&gt;The Jupyter Foundation is excited to gather your feedback on the Jupyter user experience through a brief survey. If you had a magic wand…&lt;/p&gt;
</summary><content type="html">&lt;p&gt;The &lt;a href="https://jupyterfoundation.org/"&gt;Jupyter Foundation&lt;/a&gt; is excited to gather your feedback on the Jupyter user experience through a brief &lt;a href="https://linuxfoundation.surveymonkey.com/r/jupyter-user-survey"&gt;survey&lt;/a&gt;. If you had a magic wand, what would you change or add to Jupyter? Your insights are incredibly important as we continue to invest in making Jupyter better for everyone.&lt;/p&gt;
&lt;p&gt;The survey takes only about &lt;strong&gt;3 minutes&lt;/strong&gt; to complete, and we highly encourage you to participate. The survey will &lt;strong&gt;close on Sunday, June 28th&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://linuxfoundation.surveymonkey.com/r/jupyter-user-survey"&gt;&lt;strong&gt;TAKE THE SURVEY&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Thank you for your time, your input, and your continued support of the Jupyter ecosystem!&lt;/p&gt;
</content><category term="community"/><category term="Jupyter Foundation"/></entry><entry><title>Jupyter Community Workshops: Early 2026</title><link href="https://jasongrout.github.io/medium-archive/pelican/posts/2025/jupyter-community-workshops-early-2026/" rel="alternate"/><published>2025-11-20T13:48:00+00:00</published><updated>2025-11-20T13:48:00+00:00</updated><author><name>Jason Grout</name></author><id>tag:jasongrout.github.io,2025-11-20:/medium-archive/pelican/posts/2025/jupyter-community-workshops-early-2026/</id><summary type="html">&lt;p&gt;The Jupyter Community Building Working Group is happy to announce the Jupyter Community Workshops selected for funding in early 2026. The…&lt;/p&gt;
</summary><content type="html">&lt;p&gt;The &lt;a href="https://jupyter.org/governance/communitybuildingworkinggroup/"&gt;Jupyter Community Building Working Group&lt;/a&gt; is happy to announce the &lt;a href="https://jupyter.org/community#jupyter-community-workshops"&gt;Jupyter Community Workshops&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt;We applaud all who &lt;a href="/posts/2025/jupyter-community-workshops-are-back/"&gt;submitted proposals&lt;/a&gt; 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 &lt;a href="https://jupyterfoundation.org/"&gt;Jupyter Foundation&lt;/a&gt; that makes these workshops possible.&lt;/p&gt;
&lt;h3 id="ai-in-jupyter-building-extensible-ai-capabilities-for-interactive-computing"&gt;AI in Jupyter: Building Extensible AI Capabilities for Interactive Computing&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Zach Sailer (Apple), Jeremy Tuloup (Quantstack), David Qiu (AWS)&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3 id="roadmap-workshop-for-jupyterhub-and-binder"&gt;Roadmap Workshop for JupyterHub and Binder&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Arielle Bennett (The Alan Turing Institute), Min Ragan-Kelley (Berkeley Institute for Data Science, UC Berkeley), Raniere Silva (GESIS)&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;This workshop will be developing and documenting a roadmap for &lt;a href="https://jupyter.org/hub"&gt;JupyterHub&lt;/a&gt; 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, &lt;a href="https://z2jh.jupyter.org"&gt;Zero to JupyterHub&lt;/a&gt;, &lt;a href="https://tljh.jupyter.org"&gt;The Littlest JupyterHub&lt;/a&gt;, &lt;a href="https://repo2docker.readthedocs.io"&gt;repo2docker&lt;/a&gt;, &lt;a href="https://binderhub.readthedocs.io"&gt;binderhub&lt;/a&gt;, possibly &lt;a href="https://jupyterhealth.org/"&gt;JupyterHealth&lt;/a&gt;), depending on which participants we get.&lt;/p&gt;
&lt;h3 id="security-tooling-sprint"&gt;Security Tooling Sprint&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Joe Lucas (NVIDIA)&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3 id="demistify-myst-markdown-in-education"&gt;Demistify MyST Markdown in Education&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Chiara Marmo (Université Paris Saclay — LISN), Nicolas Grenier (Université Paris Saclay — LISN), Kirstie Whitaker (Berkeley Institute for Data Science, UC Berkeley)&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The goal of this workshop is to remove barriers for science educators in their adoption of &lt;a href="https://jupyterbook.org"&gt;Jupyter Book&lt;/a&gt; and the &lt;a href="https://mystmd.org/"&gt;MyST&lt;/a&gt; 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.&lt;/p&gt;
</content><category term="events"/><category term="workshops"/></entry><entry><title>Jupyter Community Workshops Are Back!</title><link href="https://jasongrout.github.io/medium-archive/pelican/posts/2025/jupyter-community-workshops-are-back/" rel="alternate"/><published>2025-08-07T20:03:00+00:00</published><updated>2025-09-04T21:44:00+00:00</updated><author><name>Jason Grout</name></author><id>tag:jasongrout.github.io,2025-08-07:/medium-archive/pelican/posts/2025/jupyter-community-workshops-are-back/</id><summary type="html">&lt;p&gt;The Jupyter Community Building Working Group is pleased to announce that the next call for proposals for Jupyter Community Workshops is now…&lt;/p&gt;
</summary><content type="html">&lt;p&gt;The Jupyter Community Building Working Group is pleased to announce that the next &lt;a href="https://events.linuxfoundation.org/jupyter-workshops/"&gt;call for proposals for Jupyter Community Workshops&lt;/a&gt; is now open through Sunday, September 14 (deadline extension!) for events from October 2025 through February 2026!&lt;/p&gt;
&lt;h3 id="weve-extended-the-call-for-proposals-to-be-open-through-sunday-september-14"&gt;We’ve extended the call for proposals to be open through Sunday, September 14.&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;In contrast with the broad reach of &lt;a href="https://jupyter.org/community#jupyter-community-workshops"&gt;prior Jupyter Community Workshops&lt;/a&gt;, &lt;strong&gt;this round of workshops focuses on the Jupyter contributor community&lt;/strong&gt;. Workshops should include participants who are current or aspiring Jupyter contributors.&lt;/p&gt;
&lt;h3 id="the-call-for-proposals-for-jupyter-community-workshops-is-open-through-sunday-september-14th-2025-deadline-extension"&gt;The &lt;a href="https://events.linuxfoundation.org/jupyter-workshops/"&gt;call for proposals&lt;/a&gt; for Jupyter Community Workshops is open through Sunday, September 14th, 2025 (deadline extension!)&lt;/h3&gt;
&lt;p&gt;&lt;a href="https://events.linuxfoundation.org/jupyter-workshops/what-does-hosting-a-jupyter-workshop-entail/"&gt;Learn more about what hosting a Jupyter Workshop entails&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;We are grateful for the support of the &lt;a href="https://jupyterfoundation.org"&gt;Jupyter Foundation&lt;/a&gt; and its &lt;a href="https://jupyterfoundation.org/members"&gt;members&lt;/a&gt; that makes our workshops possible. If your organization would like to support this program, please &lt;a href="https://jupyterfoundation.org/contact/"&gt;contact the Jupyter Foundation&lt;/a&gt;.&lt;/p&gt;
</content><category term="events"/><category term="workshops"/></entry><entry><title>Jupyter recognized as “Champion of Open Science” by U.S. White House</title><link href="https://jasongrout.github.io/medium-archive/pelican/posts/2024/jupyter-recognized-as-champion-of-open-science-by-u-s/" rel="alternate"/><published>2024-05-07T20:51:00+00:00</published><updated>2024-07-09T16:36:00+00:00</updated><author><name>Jason Grout</name></author><id>tag:jasongrout.github.io,2024-05-07:/medium-archive/pelican/posts/2024/jupyter-recognized-as-champion-of-open-science-by-u-s/</id><summary type="html">&lt;p&gt;Jupyter is recognized as a “Champion of Open Science” by the United States White House Office of Science and Technology Policy, in…&lt;/p&gt;
</summary><content type="html">&lt;p&gt;Jupyter is &lt;a href="https://www.whitehouse.gov/ostp/news-updates/2024/03/21/white-house-office-of-science-technology-policy-announces-year-of-open-science-recognition-challenge-winners/"&gt;recognized&lt;/a&gt; as a “Champion of Open Science” by the United States White House Office of Science and Technology Policy, in celebration of 2023 being the &lt;a href="https://open.science.gov/"&gt;Year of Open Science&lt;/a&gt;. For more information, see the &lt;a href="https://www.whitehouse.gov/ostp/news-updates/2024/03/21/white-house-office-of-science-technology-policy-announces-year-of-open-science-recognition-challenge-winners/"&gt;White House press release&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This recognition honors the large group of contributors, users, and organizations that have made Jupyter what it is today. More specifically, we, the Project Jupyter Executive Council, lists and thanks here the current (as of December 2023) and previous members of the following Jupyter leadership groups: Executive Council, Software Steering Council, Software Subproject Councils, Working Groups, Standing Committees, Distinguished Contributors, and the former Jupyter Steering Council. (If there is someone in these groups that we accidentally missed in the list below, please let us know.)&lt;/p&gt;
&lt;h3 id="project-leaders-and-distinguished-contributors-alphabetical-by-last-name"&gt;Project leaders and distinguished contributors (alphabetical by last name)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Safia Abdalla&lt;/li&gt;
&lt;li&gt;Damián Avila&lt;/li&gt;
&lt;li&gt;Lorena A. Barba&lt;/li&gt;
&lt;li&gt;Kevin Bates&lt;/li&gt;
&lt;li&gt;Mehmet Bektas&lt;/li&gt;
&lt;li&gt;Douglas Blank&lt;/li&gt;
&lt;li&gt;Nicholas Bollweg&lt;/li&gt;
&lt;li&gt;Alex Bozarth&lt;/li&gt;
&lt;li&gt;Maarten Breddels&lt;/li&gt;
&lt;li&gt;Nicolas Brichet&lt;/li&gt;
&lt;li&gt;David Brochart&lt;/li&gt;
&lt;li&gt;Matthias Bussonnier&lt;/li&gt;
&lt;li&gt;Eric Charles&lt;/li&gt;
&lt;li&gt;S. Chris Colbert&lt;/li&gt;
&lt;li&gt;Frédéric Collonval&lt;/li&gt;
&lt;li&gt;Sylvain Corlay&lt;/li&gt;
&lt;li&gt;Martha Cryan&lt;/li&gt;
&lt;li&gt;Carlos Córdoba&lt;/li&gt;
&lt;li&gt;Itay Dafna&lt;/li&gt;
&lt;li&gt;Afshin Darian&lt;/li&gt;
&lt;li&gt;Jacob Diamond-Reivich&lt;/li&gt;
&lt;li&gt;Georgiana Dolocan&lt;/li&gt;
&lt;li&gt;R Ely&lt;/li&gt;
&lt;li&gt;Tony Fast&lt;/li&gt;
&lt;li&gt;Vidar T. Fauske&lt;/li&gt;
&lt;li&gt;Sharan Foga&lt;/li&gt;
&lt;li&gt;Jessica Zosa Forde&lt;/li&gt;
&lt;li&gt;Gabriel Fouasnon&lt;/li&gt;
&lt;li&gt;Jonathan Frederic&lt;/li&gt;
&lt;li&gt;Eric Gentry&lt;/li&gt;
&lt;li&gt;Tim George&lt;/li&gt;
&lt;li&gt;Sarah Gibson&lt;/li&gt;
&lt;li&gt;Kevin Goldsmith&lt;/li&gt;
&lt;li&gt;Rahul Goyal&lt;/li&gt;
&lt;li&gt;Brian Granger&lt;/li&gt;
&lt;li&gt;Jason Grout&lt;/li&gt;
&lt;li&gt;Jessica Hamrick&lt;/li&gt;
&lt;li&gt;Tim Head&lt;/li&gt;
&lt;li&gt;Lindsey Heagy&lt;/li&gt;
&lt;li&gt;Carlos Herrero&lt;/li&gt;
&lt;li&gt;Chris Holdgraf&lt;/li&gt;
&lt;li&gt;Andrii Ieroshenko&lt;/li&gt;
&lt;li&gt;Paul Ivanov&lt;/li&gt;
&lt;li&gt;Piyush Jain&lt;/li&gt;
&lt;li&gt;Lucy Jimenez&lt;/li&gt;
&lt;li&gt;Kyle Kelley&lt;/li&gt;
&lt;li&gt;Max C Klein&lt;/li&gt;
&lt;li&gt;Thomas Kluyver&lt;/li&gt;
&lt;li&gt;Michał Krassowski&lt;/li&gt;
&lt;li&gt;Simon Li&lt;/li&gt;
&lt;li&gt;Ryan Lovett&lt;/li&gt;
&lt;li&gt;Joe Lucas&lt;/li&gt;
&lt;li&gt;Johan Mabille&lt;/li&gt;
&lt;li&gt;Grant Nestor&lt;/li&gt;
&lt;li&gt;Cameron Oelsen&lt;/li&gt;
&lt;li&gt;M Pacer&lt;/li&gt;
&lt;li&gt;Yuvi Panda&lt;/li&gt;
&lt;li&gt;Peter Parente&lt;/li&gt;
&lt;li&gt;Fernando Pérez&lt;/li&gt;
&lt;li&gt;Isabela Presedo-Floyd&lt;/li&gt;
&lt;li&gt;David Qiu&lt;/li&gt;
&lt;li&gt;Min Ragan-Kelley&lt;/li&gt;
&lt;li&gt;Martin Renou&lt;/li&gt;
&lt;li&gt;Luciano Resende&lt;/li&gt;
&lt;li&gt;Rosio Reyes&lt;/li&gt;
&lt;li&gt;Ian Rose&lt;/li&gt;
&lt;li&gt;Ana Ruvalcaba&lt;/li&gt;
&lt;li&gt;Zach Sailer&lt;/li&gt;
&lt;li&gt;Ayaz Salikhov&lt;/li&gt;
&lt;li&gt;Matthew Seal&lt;/li&gt;
&lt;li&gt;Saul Shanabrook&lt;/li&gt;
&lt;li&gt;Steve Silvester&lt;/li&gt;
&lt;li&gt;William Stein&lt;/li&gt;
&lt;li&gt;Erik Sundell&lt;/li&gt;
&lt;li&gt;Nicolas Thiéry&lt;/li&gt;
&lt;li&gt;Rollin Thomas&lt;/li&gt;
&lt;li&gt;Jeremy Tuloup&lt;/li&gt;
&lt;li&gt;Rick Wagner&lt;/li&gt;
&lt;li&gt;Mariko Wakabayashi&lt;/li&gt;
&lt;li&gt;Jason Weill&lt;/li&gt;
&lt;li&gt;Carol Willing&lt;/li&gt;
&lt;li&gt;Jessica Xu&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Additionally, we’d like to thank the following organizations that were directly involved in the work (other than funding agencies) in terms of staff or other significant resources to directly support the development of Project Jupyter.&lt;/p&gt;
&lt;h3 id="organizations-alphabetical"&gt;Organizations (alphabetical)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Amazon Web Services&lt;/li&gt;
&lt;li&gt;Anaconda&lt;/li&gt;
&lt;li&gt;Bloomberg&lt;/li&gt;
&lt;li&gt;California Polytechnic State University, San Luis Obispo&lt;/li&gt;
&lt;li&gt;Databricks&lt;/li&gt;
&lt;li&gt;Lawrence Berkeley National Laboratory&lt;/li&gt;
&lt;li&gt;MongoDB&lt;/li&gt;
&lt;li&gt;QuanSight&lt;/li&gt;
&lt;li&gt;QuantStack&lt;/li&gt;
&lt;li&gt;Simula Research Lab&lt;/li&gt;
&lt;li&gt;Two Sigma&lt;/li&gt;
&lt;li&gt;University of California, Berkeley&lt;/li&gt;
&lt;/ul&gt;
</content><category term="open science"/></entry><entry><title>Jupyter Community Workshops: Call for Proposals for Jan-Aug 2020</title><link href="https://jasongrout.github.io/medium-archive/pelican/posts/2019/jupyter-community-workshops-call-for-proposals-for-jan/" rel="alternate"/><published>2019-11-12T23:32:00+00:00</published><updated>2019-11-21T05:13:00+00:00</updated><author><name>Jason Grout</name></author><id>tag:jasongrout.github.io,2019-11-12:/medium-archive/pelican/posts/2019/jupyter-community-workshops-call-for-proposals-for-jan/</id><summary type="html">&lt;p&gt;We are pleased to announce the third call for proposals for Jupyter Community Workshops is now open!&lt;/p&gt;
</summary><content type="html">&lt;figure&gt;
&lt;img alt="Teaching and Learning with Jupyter community workshop. Credit: Richard West." src="https://jasongrout.github.io/medium-archive/pelican/posts/2019/jupyter-community-workshops-call-for-proposals-for-jan/images/001-1_wrX3-f3MQ8LbVQRYqJGB3A.jpeg" loading="lazy" data-body-image=""&gt;
&lt;figcaption&gt;&lt;a href="/posts/2019/teaching-and-learning-with-jupyter/"&gt;Teaching and Learning with Jupyter&lt;/a&gt; community workshop. Credit: Richard West.&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;We are pleased to announce the third call for proposals for Jupyter Community Workshops is now open!&lt;/p&gt;
&lt;p&gt;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 &lt;a href="/posts/2019/jupyter-community-workshops/"&gt;proposals funded in the last round&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;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 &lt;a href="https://numfocus.org/"&gt;NumFOCUS&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="the-third-call-for-proposals-for-jupyter-community-workshops-is-open-through-sunday-december-15-2019"&gt;The third call for proposals for Jupyter Community Workshops is open through Sunday, December 15, 2019.&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;For examples of recent workshops, see the &lt;a href="/posts/2019/jupyter-community-workshops/"&gt;proposals funded in the last round&lt;/a&gt;).&lt;/p&gt;
&lt;h2 id="proposal-process-highlights"&gt;Proposal Process Highlights:&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Submit initial proposal &lt;a href="https://docs.google.com/forms/d/e/1FAIpQLScPT-qLXttF6lgdJx-4kDXruVMIqt2LZbjzAqo3aI1v_IbbIQ/viewform?usp=sf_link"&gt;using this form&lt;/a&gt; by &lt;strong&gt;Sunday, December 15 (&lt;/strong&gt;&lt;a href="https://en.wikipedia.org/wiki/Anywhere_on_Earth"&gt;&lt;strong&gt;Anywhere on Earth&lt;/strong&gt;&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;Initial Steering Council review (up to a week). Proposal goes to Steering Council for initial review and feedback. Proposal is either approved or declined.&lt;/li&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The proposal process for these workshops is managed by the Director of Jupyter Cal Poly, Ana Ruvalcaba (&lt;a href="mailto:jupyterops@gmail.com"&gt;jupyterops@gmail.com&lt;/a&gt;), NumFOCUS and the Jupyter Steering Council. Applications can be completed using the &lt;a href="https://docs.google.com/forms/d/e/1FAIpQLScRw97uRtsWC3IzWKPED7XyJg86L2eDmJo0QctzdbF02288Qw/viewform"&gt;online form&lt;/a&gt; and are due by Sunday, December 15 (&lt;a href="https://en.wikipedia.org/wiki/Anywhere_on_Earth"&gt;Anywhere on Earth&lt;/a&gt;). Events should be hosted no later than August of 2020.&lt;/p&gt;
&lt;p&gt;— -&lt;/p&gt;
&lt;p&gt;This initiative is organized by Jason Grout, Paul Ivanov, Brian Granger, and Ana Ruvalcaba.&lt;/p&gt;
</content><category term="events"/><category term="workshops"/></entry><entry><title>Jupyter Conference Advisory Committee</title><link href="https://jasongrout.github.io/medium-archive/pelican/posts/2019/jupyter-conference-advisory-committee/" rel="alternate"/><published>2019-02-11T16:07:00+00:00</published><updated>2019-02-11T16:07:00+00:00</updated><author><name>Jason Grout</name></author><id>tag:jasongrout.github.io,2019-02-11:/medium-archive/pelican/posts/2019/jupyter-conference-advisory-committee/</id><summary type="html">&lt;p&gt;Safia Abdalla, Paige Bailey, Doug Blank lead community Jupyter Conference Advisory Committee to explore future Jupyter conference…&lt;/p&gt;
</summary><content type="html">&lt;p&gt;In December, we announced the &lt;a href="/posts/2018/the-future-of-jupytercon-2019-and-beyond/"&gt;formation of a Jupyter Conference Advisory Committee&lt;/a&gt; to explore the future of the annual Jupyter conference. We are very grateful for the outpouring of support from the community in this endeavor.&lt;/p&gt;
&lt;p&gt;We are pleased to announce that Safia Abdalla, Paige Bailey, and Doug Blank will co-lead this committee. They will reach out to those who volunteered to help with this committee about next steps. If anyone else from the community would like to participate, please reach out to the leaders at &lt;a href="mailto:safia@safia.rocks"&gt;safia@safia.rocks&lt;/a&gt;, &lt;a href="mailto:webpaige@google.com"&gt;webpaige@google.com&lt;/a&gt;, and &lt;a href="mailto:doug@comet.ml"&gt;doug@comet.ml&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This advisory committee is organized to advise the Jupyter Steering Council in a report in March on answers to the following key questions:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Conference format and name&lt;/strong&gt;: What conference format should Jupyter adopt for its annual conference? What alternatives were considered, and what principles led to this recommendation? What should the name of the conference be?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;2019 conference&lt;/strong&gt;: Should we have a conference in 2019? If so, what are feasible venues and dates?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Organizing and planning&lt;/strong&gt;: How should the next conference be organized? What committees should be formed and what are their responsibilities? What organizational milestones and timelines should there be?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Financial&lt;/strong&gt;: What is the business model for sustaining the conference? What are the sources of risk in the business model and what can be done to mitigate those risks?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Partners&lt;/strong&gt;: With what organizations (if any) will Jupyter partner in the organization of the conference? On the operations/logistics side? On the program side? Financially? How should sponsorships work?&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Again, we are very grateful for the community response, and for Safia, Paige, and Doug serving as leaders of this committee.&lt;/p&gt;
</content><category term="events"/></entry><entry><title>Jupyter Community Workshops</title><link href="https://jasongrout.github.io/medium-archive/pelican/posts/2019/jupyter-community-workshops/" rel="alternate"/><published>2019-01-15T20:06:00+00:00</published><updated>2019-01-16T07:48:00+00:00</updated><author><name>Jason Grout</name></author><id>tag:jasongrout.github.io,2019-01-15:/medium-archive/pelican/posts/2019/jupyter-community-workshops/</id><summary type="html">&lt;p&gt;We are thrilled to announce the Jupyter Community workshops for the first half of 2019. We had 16 proposals submitted, each of which…&lt;/p&gt;
</summary><content type="html">&lt;p&gt;We are thrilled to announce the Jupyter Community workshops for the first half of 2019. We had 16 proposals submitted, each of which represents a tremendous amount of effort and opportunity for community growth. Thank you for your proposals!&lt;/p&gt;
&lt;p&gt;We were able to fund the following seven proposals. The dates, venues, participants, and specific agenda for each workshop are being finalized in the near future. If you are interested in participating in one of the workshops, please contact the organizers (tentative locations and contact emails are in the descriptions below).&lt;/p&gt;
&lt;h3 id="introduction-to-python-coding-for-kids-parents-and-teachers"&gt;Introduction to Python Coding for Kids, Parents and Teachers&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;England; Tariq Rashid (CoderDojo Cornwall, Data Science Cornwall and Algorithmic Art (London));&lt;/em&gt; &lt;a href="mailto:coderdojocornwall@gmail.com"&gt;coderdojocornwall@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Cornwall, in the southwest of England is primarily a rural and coastal region, where traditional industries are not as prevalent as they were in the past. The technology sector is small but hugely enthusiastic and growing. A key challenge for the region is to develop a sustainable technology ecosystem. That means providing young people with pathways into hugely rewarding fields like data science. There is growing effort, mostly voluntary, to inspire children to learn to code, and provide teachers and parents with support to do this. Although a very wide range of technologies and ideas are covered — from creative coding on the web to programming hardware microcontrollers — a critical gap in many resources for young learners are the tools and techniques used by modern developers and data scientists. Our project will start to address this gap by providing free workshops across Cornwall introducing children to working with the Jupyter notebook, a simple but powerful tool, suitable for learning Python as well as gaining experience with data science concepts and techniques. These young people will not just gain skills and experience attractive to employers, but perhaps also discover a talent or a passion they didn’t know they had. And of course, all the learning resources, example projects and code, and supporting videos we develop and test will be made available on the web for everyone to use.&lt;/p&gt;
&lt;h3 id="dashboarding-in-the-jupyter-ecosystem"&gt;Dashboarding in the Jupyter ecosystem&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Europe; Maarten Breddels (independent/freelance), Sylvain Corlay (QuantStack), Pascal Bugnion (ASI Data Science), Vidar Tonaas Fauske (Simula Research Laboratory), Alexandre Gramfort (INRIA);&lt;/em&gt; &lt;a href="mailto:pascal@bugnion.org"&gt;pascal@bugnion.org,&lt;/a&gt; &lt;a href="mailto:sylvain.corlay@quantstack.net"&gt;sylvain.corlay@quantstack.net&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The Jupyter ecosystem has great tools for teaching, exploration and development. Dashboards allow a user to interact with a kernel with interactive controls, plots, maps, etc., and allow researchers and data scientists to share their results with students, with their peers, and with the general public. Currently, users of Jupyter are (mostly) forced towards other Python or R libraries or they have to develop using frontend technologies like JavaScript directly.&lt;/p&gt;
&lt;p&gt;There are existing early technologies that allow serving dashboards based off notebooks, most notably &lt;a href="https://github.com/QuantStack/voila"&gt;voila&lt;/a&gt;. The goal of this workshop is to gather core Jupyter widgets developers, members of the community and users with experience in dashboarding to bring dashboarding to a level where it can be used by all members of the Jupyter ecosystem. Ultimately, we envisage users being able to develop and deploy dashboards entirely within the Jupyter ecosystem.&lt;/p&gt;
&lt;h3 id="jupyter-server-design-and-roadmap-workshop"&gt;Jupyter Server Design and Roadmap Workshop&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;California; Luciano Resende (IBM);&lt;/em&gt; &lt;a href="mailto:lresende@us.ibm.com"&gt;lresende@us.ibm.com&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The Jupyter Notebook backend capabilities are evolving quickly and a new project, Jupyter Server, aims to become the new backend for Jupyter web applications such as the Jupyter notebook and JupyterLab.&lt;/p&gt;
&lt;p&gt;The goal of this workshop is to foster collaboration between different projects and community contributors working on Jupyter server-side functionality and have a broader discussion about design and future roadmap for the project. We will take the opportunity to also ensure that Jupyter Community use cases for pluggability and extensibility are being properly considered (e.g. extension points to enable kernel as a service, remote kernels, etc).&lt;/p&gt;
&lt;h3 id="jupyter-for-scientific-user-facilities-and-high-performance-computing"&gt;Jupyter for Scientific User Facilities and High-Performance Computing&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Berkeley, California; Dan Allan (BNL), Debbie Bard (LBNL), Shane Canon (LBNL), Shreyas Cholia (LBNL), Chris Holdgraf (BIDS — UC Berkeley), Kelly Rowland (LBNL), Rollin Thomas (LBNL);&lt;/em&gt; &lt;a href="mailto:rcthomas@lbl.gov"&gt;rcthomas@lbl.gov&lt;/a&gt;&lt;a href="mailto:daniel.b.allan@gmail.com"&gt;, daniel.b.allan@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Scientists love Jupyter because it combines documentation, visualization, data analytics, and code into a document they can share, modify, and even publish. What about using Jupyter to control experiments in real-time, or steer complex simulations on a supercomputer, or even connect experiments to high-performance computing for real-time feedback? How does one reach outside the notebook to corral external data and computational resources in a seamless manner? Our workshop will bring together Jupyter developers, scientists from experimental and observational science facilities, and supercomputing center staff to elevate Jupyter as the preeminent interface for distributed data-intensive workflows. We will identify best practices, share lessons learned, clarify gaps and challenges in supporting deployments, and work on new tools to make Jupyter easier to use for big science.&lt;/p&gt;
&lt;h3 id="building-upon-the-jupyter-kernel-protocol"&gt;Building upon the Jupyter Kernel Protocol&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Europe; Sylvain Corlay (QuantStack);&lt;/em&gt; &lt;a href="mailto:sylvain.corlay@quantstack.net"&gt;sylvain.corlay@quantstack.net&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The Jupyter kernel protocol is one of the main extension points of the Jupyter ecosystem. Dozens of language kernels have been developed by the community, and these languages can now leverage other components of the stack, such as the notebook, the console, and interactive widgets.&lt;/p&gt;
&lt;p&gt;The goal of this workshop is to foster collaboration between kernel developers, including the development of common tools for testing and supporting all aspect of the protocol. Beyond the currently supported messages, we will discuss potential improvements and additions, such as the support of debugging messages, the ability to parameterize kernelspecs, and common testing infrastructures.&lt;/p&gt;
&lt;h3 id="nbgrader-hackathoncode-sprint"&gt;Nbgrader Hackathon/Code Sprint&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Scotland; James Slack (University of Edinburgh);&lt;/em&gt; &lt;a href="mailto:james.slack@ed.ac.uk"&gt;james.slack@ed.ac.uk&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The University of Edinburgh will be hosting a three-day community event focused using Jupyter notebooks within teaching. The core aspect of this event will be a Hackathon focused on adding improvements, fixes and extra documentation for the nbgrader extension. Alongside this, there is a plan to run introductory open workshops for using Jupyter in teaching, targeting local communities with some exposure to Jupyter as well as those new to Jupyter. Our key aim will be to improve the existing features within nbgrader. This will allow the existing Jupyter user community and new users to adopt and use this as an assessment tool alongside Jupyter notebooks. By enthusing our existing local Jupyter users to be more involved with the wider community and inviting new users to join, we will be increasing the diversity of opinion and experience within the Jupyter user community.&lt;/p&gt;
&lt;h3 id="south-american-jupyter-developers"&gt;South American Jupyter Developers&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;Argentina; Damián Avila;&lt;/em&gt; &lt;a href="mailto:damianavila@gmail.com"&gt;damianavila@gmail.com&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The Jupyter community is the vital force that builds and sustains the Jupyter ecosystem. In our workshop, we will begin building an active South American Jupyter community. This will greatly increase the diversity of our current community, bringing not only new ideas but also new Jupyter developments and solutions to solve some of the problems we see in this part (and other parts) of the world.&lt;/p&gt;
&lt;p&gt;We will start this process with an event bringing people from some parts of South America to Córdoba, Argentina to work/sprint in some of the pieces of the Jupyter ecosystem. Our plan is to plant seeds to disseminate the Jupyter ecosystem in different regions of South America, accelerating the South American Jupyter community growth.&lt;/p&gt;
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt;
&lt;p&gt;We are very grateful to each of the organizers, and each person who submitted a proposal, which represent a significant commitment to building the Jupyter community. We are also grateful for the generous support &lt;a href="https://www.techatbloomberg.com/"&gt;Bloomberg&lt;/a&gt; provided that made these workshops possible.&lt;/p&gt;
</content><category term="events"/><category term="workshops"/></entry><entry><title>Deadline Extension: Jupyter Community Workshops</title><link href="https://jasongrout.github.io/medium-archive/pelican/posts/2018/deadline-extension-jupyter-community-workshops/" rel="alternate"/><published>2018-07-31T17:52:00+00:00</published><updated>2026-08-22T20:41:00+00:00</updated><author><name>Jason Grout</name></author><id>tag:jasongrout.github.io,2018-07-31:/medium-archive/pelican/posts/2018/deadline-extension-jupyter-community-workshops/</id><summary type="html">&lt;p&gt;We recently announced a call for proposals for Jupyter Community Workshops. These workshops are intended to bring together small groups of…&lt;/p&gt;
</summary><content type="html">&lt;p&gt;We recently announced a &lt;a href="/posts/2018/jupyter-community-workshops/"&gt;call for proposals&lt;/a&gt; for Jupyter Community Workshops. These workshops are intended to bring together small groups of Jupyter community members (1–2 dozen people) and core contributors for high-impact strategic work and community engagement on focused topics related to the Jupyter’s core mission.&lt;/p&gt;
&lt;p&gt;We are extending the deadline for the initial proposals to &lt;strong&gt;Monday, August 6&lt;/strong&gt;, &lt;strong&gt;8am Pacific time (3pm UTC)&lt;/strong&gt;. Please submit your proposals with &lt;a href="https://docs.google.com/forms/d/e/1FAIpQLScRw97uRtsWC3IzWKPED7XyJg86L2eDmJo0QctzdbF02288Qw/viewform"&gt;this form&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;For more information related to expectations of organizers and other logistics, please read our &lt;a href="https://docs.google.com/document/d/1dkGMOAzulLg_l3mQTYWhWotr3sYQ1FLa8rjoSrD_FVA/edit?usp=sharing"&gt;information document&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id="proposal-process-highlights"&gt;Proposal Process Highlights:&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Submit initial proposal using &lt;a href="https://docs.google.com/forms/d/e/1FAIpQLScRw97uRtsWC3IzWKPED7XyJg86L2eDmJo0QctzdbF02288Qw/viewform"&gt;this form&lt;/a&gt; by &lt;strong&gt;Monday, August 6, 8am Pacific time (3pm UTC)&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Initial steering council review (up to a week). Proposal goes to Steering Council for initial review and feedback. Proposal is either approved or declined.&lt;/li&gt;
&lt;li&gt;Budget development (up to two weeks). Operations Manager and workshop organizer will work together to develop a detailed budget, event plan, and proposed list of participants.&lt;/li&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Several possible workshop ideas are mentioned in the &lt;a href="/posts/2018/jupyter-community-workshops/"&gt;original announcement&lt;/a&gt; for proposals. Another idea that has come up in conversation is a workshop focused on using Jupyter in a broad discipline or setting which would have high-impact strategic importance for Jupyter.&lt;/p&gt;
&lt;p&gt;Feel free to email jupyterops@gmail.com with questions about the proposal process or feedback on potential proposals.&lt;/p&gt;
</content><category term="events"/><category term="workshops"/></entry></feed>