<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>pyOpenSci Blog on pyOpenSci</title><link>https://www.pyopensci.org/blog/</link><description>Recent content in pyOpenSci Blog on pyOpenSci</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 05 Jun 2026 00:00:00 -0600</lastBuildDate><atom:link href="https://www.pyopensci.org/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Generative AI and open source: what PyCon US 2026 taught us about the path forward</title><link>https://www.pyopensci.org/blog/pycon-us-2026-generative-ai-open-source.html</link><pubDate>Mon, 08 Jun 2026 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pycon-us-2026-generative-ai-open-source.html</guid><description>&lt;p>&lt;em>This post is Part 4 of a 4-part series on pyOpenSci at &lt;a href="https://us.pycon.org/2026/">PyCon US 2026&lt;/a>. &lt;a href="https://www.pyopensci.org/blog/pycon-us-2026-community-connection.html">Part 1&lt;/a> covers community and connection. &lt;a href="https://www.pyopensci.org/blog/pycon-us-2026-maintainers-summit.html">Part 2&lt;/a> covers the Maintainer Summit. &lt;a href="https://www.pyopensci.org/blog/pycon-us-2026-sprints.html">Part 3&lt;/a> covers the sprints.&lt;/em>&lt;/p>
&lt;h2 id="generative-ai-and-open-source-what-the-community-is-wrestling-with">Generative AI and open source: what the community is wrestling with&lt;/h2>
&lt;p>Generative AI was a dominant theme at PyCon US 2026 — prominent enough
to have its own dedicated conference track for the first time. But for
pyOpenSci, the conversation wasn&amp;rsquo;t about machine learning applications
or what AI can build. It was about something more immediate: &lt;strong>what
generative AI tools are doing to open source communities themselves.&lt;/strong>&lt;/p></description></item><item><title>It started with one contributor and now we fill the room: pyOpenSci sprints at PyCon US 2026</title><link>https://www.pyopensci.org/blog/pycon-us-2026-sprints.html</link><pubDate>Mon, 01 Jun 2026 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pycon-us-2026-sprints.html</guid><description>&lt;p>&lt;em>This post is Part 3 of a 4-part series on pyOpenSci at PyCon US 2026. &lt;a href="https://www.pyopensci.org/blog/pycon-us-2026-community-connection.html">Part 1&lt;/a> covers community and connection. &lt;a href="https://www.pyopensci.org/blog/pycon-us-2026-maintainers-summit.html">Part 2&lt;/a> covers the Maintainer Summit.&lt;/em>&lt;/p>
&lt;p>This year marked our fourth sprint at &lt;a href="https://us.pycon.org/2026/">PyCon US&lt;/a>. If you want to really understand what pyOpenSci is about, our sprints are the place to look.&lt;/p>
&lt;figure class="figure">
 &lt;a href="https://www.pyopensci.org/images/blog/2026/pycon-us-2026-sprints-keynote-slide.png" class="figure__link">
 &lt;picture class="figure__picture">&lt;source srcset="https://www.pyopensci.org/images/blog/2026/pycon-us-2026-sprints-keynote-slide.webp" type="image/webp">&lt;img src="https://www.pyopensci.org/images/blog/2026/pycon-us-2026-sprints-keynote-slide.png" alt="The PyCon US 2026 sprints slide projected on the main keynote screen, listing Monday and Tuesday sprint projects including Django, Mailman, ScanAPI, Memray, PyStack, Djangonaut Space, BeeWare, and more." class="figure__image">
 &lt;/picture>
 &lt;/a>&lt;figcaption class="figure__caption">Sprints at PyCon US 2026 — dozens of open source projects welcoming contributors on Monday and Tuesday.&lt;/figcaption>&lt;/figure>

&lt;p>When we held our very first sprint at PyCon US 2023 in Salt Lake City, it was my first time running a formal sprint. I missed the introductions to the sprints and pyOpenSci was not well known in the broader Python community&amp;ndash;yet. One person showed up. &lt;a href="https://www.pyopensci.org/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html">Read more about that first PyCon experience&lt;/a>. This year, ~20 people showed up throughout the day. That arc — from a single contributor to a buzzing room of people at round tables — tells you everything about our community.&lt;/p></description></item><item><title>Tools Track, GenAI Bof and Roundtables: This year's PyCon US Maintainer Summit was something special</title><link>https://www.pyopensci.org/blog/pycon-us-2026-maintainers-summit.html</link><pubDate>Fri, 29 May 2026 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pycon-us-2026-maintainers-summit.html</guid><description>&lt;p>&lt;em>This post is Part 2 of a 4-part series on pyOpenSci at PyCon US 2026. &lt;a href="https://www.pyopensci.org/blog/pycon-us-2026-community-connection.html">Part 1&lt;/a> covers community, connection, and what comes next.&lt;/em>&lt;/p>
&lt;p>I first attended the &lt;a href="https://us.pycon.org/2026/events/maintainers-summit/">PyCon US Maintainer Summit&lt;/a> five years ago as a speaker. I&amp;rsquo;m still here — now as a co-organizer. This year felt like a milestone for many different reasons.&lt;/p>
&lt;figure class="figure">
 &lt;a href="https://www.pyopensci.org/images/blog/2026/pycon-us-2026-maintainers-summit-organizers-slide.png" class="figure__link">
 &lt;picture class="figure__picture">&lt;source srcset="https://www.pyopensci.org/images/blog/2026/pycon-us-2026-maintainers-summit-organizers-slide.webp" type="image/webp">&lt;img src="https://www.pyopensci.org/images/blog/2026/pycon-us-2026-maintainers-summit-organizers-slide.png" alt="Maintainer Summit organizers slide with headshots of Inessa Pawson, Leah Wasser, and Mariatta Wijaya beneath the Maintainers Summit title and PyCon US Long Beach branding." class="figure__image">
 &lt;/picture>
 &lt;/a>&lt;figcaption class="figure__caption">Maintainer Summit co-organizers &lt;a href='https://github.com/InessaPawson'>Inessa Pawson&lt;/a>, Leah Wasser, and &lt;a href='https://github.com/mariatta'>Mariatta Wijaya&lt;/a>.&lt;/figcaption>&lt;/figure>

&lt;h2 id="building-the-summit-a-year-round-labor-of-love">Building the summit: a year-round labor of love&lt;/h2>
&lt;p>What most people don&amp;rsquo;t realize is that organizing the PyCon US Maintainer Summit is a year-round effort. We start thinking about the next one almost as soon as the last one wraps — collecting participant feedback, reflecting on what worked, and thinking about what to change.&lt;/p></description></item><item><title>PyCon US 2026: Community, connection, and what comes next</title><link>https://www.pyopensci.org/blog/pycon-us-2026-community-connection.html</link><pubDate>Thu, 21 May 2026 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pycon-us-2026-community-connection.html</guid><description>&lt;p>Times are hard right now. Communities like pyOpenSci matter more than ever. We saw it at &lt;a href="https://us.pycon.org/2026/">PyCon US&lt;/a> this year — the political strain, the GenAI hype cycle and anxiety, the rapid changes reshaping open source. People are tired. People are frustrated. But here&amp;rsquo;s what else we saw: people still showing up. Still connecting. Still supporting each other.&lt;/p>
&lt;p>When things get hard, when the ground shifts beneath us, we need each other more than ever. We need spaces to connect, to learn together, to solve challenging problems as a community. PyCon reminded me why I love this work so much.&lt;/p></description></item><item><title>Ship It Cohort One: What We Built, What We Learned, and What's Next</title><link>https://www.pyopensci.org/blog/ship-it-cohort-one.html</link><pubDate>Mon, 04 May 2026 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/ship-it-cohort-one.html</guid><description>&lt;p>Python packaging can be overwhelming — standards and tools evolve quickly, and the terminology is technical. To address these challenges, pyOpenSci recently launched &lt;strong>Ship It: Python Packaging in the Generative AI Era&lt;/strong>. This 10-day asynchronous course connects university researchers and learners with open source experts, guiding them through the process of transforming code into a published, tested, and documented package — while weaving in a framework for using generative AI thoughtfully. The curriculum is informed by our community-driven resources, including the &lt;a href="https://www.pyopensci.org/python-package-guide/">pyOpenSci Python packaging guide&lt;/a> and our beginner-friendly &lt;a href="https://www.pyopensci.org/python-package-guide/tutorials/create-python-package.html">packaging tutorials&lt;/a>.&lt;/p></description></item><item><title>Building Resilience: pyOpenSci in 2026</title><link>https://www.pyopensci.org/blog/2026-building-resilience-together.html</link><pubDate>Thu, 22 Jan 2026 00:00:00 -0700</pubDate><guid>https://www.pyopensci.org/blog/2026-building-resilience-together.html</guid><description>&lt;h2 id="the-world-has-changed">The world has changed&lt;/h2>
&lt;p>I&amp;rsquo;m not going to sugarcoat it—2025 was hard.&lt;/p>
&lt;p>Watching organizations like the &lt;a href="https://pyfound.blogspot.com/2025/10/NSF-funding-statement.html">Python Software Foundation turn down million-dollar National Science Foundation (NSF) grants&lt;/a>
because DEIA work was no longer supported made something painfully clear: the funding landscape that has grounded so many of us is no longer reliable.&lt;/p>
&lt;p>At the same time, Generative AI fundamentally changed how open source work happens. Maintainers found themselves reviewing more code than ever—much of it machine-generated—while navigating ethical questions about authorship and responsibility they didn&amp;rsquo;t sign up to solve on their own.&lt;/p></description></item><item><title>CyNetDiff: A Python Library for Accelerated Implementation of Network Diffusion Models</title><link>https://www.pyopensci.org/blog/cynetdiff.html</link><pubDate>Mon, 12 Jan 2026 00:00:00 -0700</pubDate><guid>https://www.pyopensci.org/blog/cynetdiff.html</guid><description>&lt;p>Network diffusion models study how information and epidemics spread over social networks, and have garnered increasing interest in recent years. Two of the most widely used models are the &lt;strong>independent cascade (IC)&lt;/strong> and &lt;strong>linear threshold (LT) models&lt;/strong>. These models simulate spread through a network by starting with a set of seed nodes that are designated as &amp;ldquo;active&amp;rdquo;, and all other nodes are &amp;ldquo;inactive&amp;rdquo;. Then, in each iteration, some inactive nodes become active, and the iterations continue until no other nodes can be activated.&lt;/p></description></item><item><title>Navigating LLMs in Open Source: pyOpenSci's New Peer Review Policy</title><link>https://www.pyopensci.org/blog/generative-ai-peer-review-policy.html</link><pubDate>Tue, 18 Nov 2025 00:00:00 -0700</pubDate><guid>https://www.pyopensci.org/blog/generative-ai-peer-review-policy.html</guid><description>&lt;p>authors: Leah Wasser, Jed Brown, Carter Rhea, Ellie Abrahams, Carol Willing, Stefan van der Walt, Eliot Robson&lt;/p>
&lt;h2 id="generative-ai-meets-scientific-open-source">Generative AI meets scientific open source&lt;/h2>
&lt;p>Some developers believe that using Generative AI products increases
efficiency. However, in scientific open source, speed isn&amp;rsquo;t
everything—transparency, quality, and community trust are just as
important as understanding the environmental impacts of using large
language models in our everyday work. Similarly, ethical questions
arise when tools may benefit some communities while harming others.&lt;/p></description></item><item><title>Why We Choose What We Choose</title><link>https://www.pyopensci.org/blog/how-we-choose-python-tools.html</link><pubDate>Thu, 02 Oct 2025 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/how-we-choose-python-tools.html</guid><description>&lt;p>A primary focus at pyOpenSci, one of our petals of support, is selecting packaging tools that work well for our users and work well together. We use our curated selection of tooling in our packaging guide, in our online tutorials, and in our trainings. We don’t require the use of any of our selected tools to submit a package to our peer review program but we will suggest them if the package authors ask for help trying to clean up or adopt new workflows.&lt;/p></description></item><item><title>From Surviving to Thriving: A Convening to Reclaim and Sustain Open Science Communities</title><link>https://www.pyopensci.org/blog/pyopensci-surviving-to-thriving.html</link><pubDate>Sun, 14 Sep 2025 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyopensci-surviving-to-thriving.html</guid><description>&lt;p>&lt;em>Authors: Kari L. Jordan, Erin Becker, Daniela Saderi, Vanessa Fairhurst, Patricia Herterich, Noam Ross, Yanina Bellini Saibene, Leah Wasser, Yo Yehudi&lt;/em>&lt;/p>
&lt;figure class="figure">
 &lt;a href="https://www.pyopensci.org/images/blog/2025/waterfall-flikr.jpg" class="figure__link">
 &lt;picture class="figure__picture">&lt;source srcset="https://www.pyopensci.org/images/blog/2025/waterfall-flikr.webp" type="image/webp">&lt;img src="https://www.pyopensci.org/images/blog/2025/waterfall-flikr.jpg" alt="A photograph of a waterfall cascading down rocks in a rich green forest setting&amp;#39; style=&amp;#39;width: 80%;" class="figure__image">
 &lt;/picture>
 &lt;/a>&lt;figcaption class="figure__caption">&amp;lsquo;Black Forest: waterfall&amp;rsquo; by &lt;em>rboed&lt;/em> is licensed under CC BY 2.0. To view a copy of this license, visit &lt;a href="https://creativecommons.org/licenses/by/2.0/?ref=openverse">https://creativecommons.org/licenses/by/2.0/?ref=openverse&lt;/a>.&lt;/figcaption>&lt;/figure>

&lt;p>Open science has transformed how research is conducted, shared, and reused. Yet the organisations at the heart of this transformation are often left vulnerable, underfunded, and disconnected from one another. To move from simply surviving to truly thriving, five leading open science organisations -- &lt;a href="https://carpentries.org/">The Carpentries&lt;/a>, &lt;a href="https://we-are-ols.org/">OLS&lt;/a>, &lt;a href="https://ropensci.org/">rOpenSci&lt;/a>, &lt;a href="https://www.pyopensci.org/">pyOpenSci&lt;/a>, and &lt;a href="https://prereview.org/">PREreview&lt;/a>) -- are convening to chart a collective path forward. We are so grateful to The Navigation Fund for supporting this work, and invite our communities to review the &lt;a href="https://commons.datacite.org/doi.org/10.71707/qttn-3j47">full proposal&lt;/a> online.&lt;/p></description></item><item><title>What’s New in pyOpenSci: September Updates + Community Shoutouts</title><link>https://www.pyopensci.org/blog/pyopensci-september-2025-updates.html</link><pubDate>Thu, 11 Sep 2025 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyopensci-september-2025-updates.html</guid><description>&lt;p>The summer was full of connection, collaboration, and momentum in the pyOpenSci community. Whether you joined us at SciPy, submitted a package for review, or just lurked, we’re so grateful you’re here!&lt;/p>
&lt;p>Here’s what’s been happening 👇&lt;/p></description></item><item><title>Succession is Success: pyOpenSci's Executive Council Transition Marks Organizational Maturity</title><link>https://www.pyopensci.org/blog/pyopensci-executive-council-transition.html</link><pubDate>Thu, 14 Aug 2025 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyopensci-executive-council-transition.html</guid><description>&lt;p>When an organization successfully navigates its first leadership transition, it&amp;rsquo;s a milestone worth celebrating. It demonstrates that the structures, processes, and culture you&amp;rsquo;ve built are strong enough to endure beyond any single individual. We&amp;rsquo;ve seen these transitions happening in our &lt;a href="https://www.pyopensci.org/handbook/governance/structure.html#peer-review-editorial-board">Editorial Board&lt;/a> over the past 3 years. Today, we&amp;rsquo;re proud to announce pyOpenSci&amp;rsquo;s first &lt;a href="https://www.pyopensci.org/handbook/governance/executive-council.html#pyopensci-executive-council">Executive Council&lt;/a> transition—a sign of our organization&amp;rsquo;s growth and maturity.&lt;/p>
&lt;figure class="figure">
 &lt;a href="https://www.pyopensci.org/images/blog/2025/executive-council-rotation-tracy.png" class="figure__link">
 &lt;picture class="figure__picture">&lt;source srcset="https://www.pyopensci.org/images/blog/2025/executive-council-rotation-tracy.webp" type="image/webp">&lt;img src="https://www.pyopensci.org/images/blog/2025/executive-council-rotation-tracy.png" alt="A graphic that says --Tracy Teal has completed a 3 year term as Executive Council Chair. We are grateful for the expertise, time and effort Tracy has put into the strategic vision for pyOpenSci.We also are grateful to Karen Cranston for stepping into the Executive Council chair position. And we welcome April Johnson as our newest Executive Council member!A timeline showing the growth of pyOpenSci from 2019 to 2024. It also has images of 3 women, Tracy, Karen and April on it on the right.&amp;#39; style=&amp;#39;width: 80%;" class="figure__image">
 &lt;/picture>
 &lt;/a>&lt;/figure>

&lt;p>As founding Executive Council Chair &lt;strong>Tracy Teal&lt;/strong> transitions from her leadership role after three transformative years, we&amp;rsquo;re excited to welcome &lt;strong>Karen Cranston&lt;/strong> as our new Executive Council Chair and &lt;strong>April Johnson&lt;/strong> as a new Executive Council member. This transition represents not just changing leadership, but the successful maturation of pyOpenSci as an organization.&lt;/p></description></item><item><title>Meet Mandy Moore, pyOpenSci’s new Communications and Community Lead!</title><link>https://www.pyopensci.org/blog/mandy-moore-communications-lead.html</link><pubDate>Wed, 13 Aug 2025 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/mandy-moore-communications-lead.html</guid><description>&lt;figure class="figure">
 &lt;a href="https://www.pyopensci.org/images/blog/2025/meet-mandy-moore-comms.png" class="figure__link">
 &lt;picture class="figure__picture">&lt;source srcset="https://www.pyopensci.org/images/blog/2025/meet-mandy-moore-comms.webp" type="image/webp">&lt;img src="https://www.pyopensci.org/images/blog/2025/meet-mandy-moore-comms.png" alt="Photo of Mandy Moore wearing a wide-brimmed black hat, sitting indoors with colorful lights in the background. Beside her is the pyOpenSci logo, featuring a stylized flower with circuit-like petals and a snake in the center, on a purple patterned background." class="figure__image">
 &lt;/picture>
 &lt;/a>&lt;/figure>

&lt;h2 id="meet-mandy-moore-pyopenscis-new-communications-and-community-lead">Meet Mandy Moore, pyOpenSci’s new Communications and Community Lead!&lt;/h2>
&lt;p>We’re thrilled to introduce &lt;strong>Mandy Moore&lt;/strong> as our new &lt;strong>Communications and Community Lead&lt;/strong> at &lt;a href="https://www.pyopensci.org/">pyOpenSci&lt;/a>!&lt;/p>
&lt;p>Mandy joins us in a part-time role focused on growing and supporting our community through clear, engaging, and inclusive communication. She’s already helping us shape how we show up across platforms, whether that’s through newsletters, social posts, blogs, or behind-the-scenes strategy. Her work is helping us highlight not just what we do at pyOpenSci, but who we’re doing it for.&lt;/p></description></item><item><title>Listening, learning, and building together: what we heard at our SciPy 2025 BoF</title><link>https://www.pyopensci.org/blog/pyopensci-bof-community-scipy-2025.html</link><pubDate>Tue, 05 Aug 2025 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyopensci-bof-community-scipy-2025.html</guid><description>&lt;figure class="figure">
 &lt;a href="https://www.pyopensci.org/images/blog/2025/scipy-bof/community-discussion-2.png" class="figure__link">
 &lt;picture class="figure__picture">&lt;source srcset="https://www.pyopensci.org/images/blog/2025/scipy-bof/community-discussion-2.webp" type="image/webp">&lt;img src="https://www.pyopensci.org/images/blog/2025/scipy-bof/community-discussion-2.png" alt="Attendees from different scientific backgrounds actively participate in a BoF discussion, sharing experiences from across the research software ecosystem." class="figure__image">
 &lt;/picture>
 &lt;/a>&lt;/figure>

&lt;p>At &lt;a href="https://www.scipy2025.scipy.org/">SciPy 2025&lt;/a> in July, &lt;a href="https://www.pyopensci.org/events/pyopensci-scipy25-bof-packaging-challenges.html">pyOpenSci hosted a Birds of a Feather session&lt;/a> focused on packaging challenges in research software.&lt;/p>
&lt;p>Rather than giving another talk or demo, we created a space to listen. Building on themes from &lt;a href="https://www.pyopensci.org/blog/python-packaging-friends-dont-let-friends-package-alone.html">our earlier blog about the social side of packaging&lt;/a>, we invited folks into a Birds of a Feather (BoF) session centered on one big question:&lt;/p></description></item><item><title>Highlights from SciPy 2025: Building Community, Code, and Culture</title><link>https://www.pyopensci.org/blog/scipy-2025-recap.html</link><pubDate>Thu, 24 Jul 2025 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/scipy-2025-recap.html</guid><description>&lt;figure class="figure">
 &lt;a href="https://www.pyopensci.org/images/events/scipy-2025/pixi-workshop.png" class="figure__link">
 &lt;picture class="figure__picture">&lt;source srcset="https://www.pyopensci.org/images/events/scipy-2025/pixi-workshop.webp" type="image/webp">&lt;img src="https://www.pyopensci.org/images/events/scipy-2025/pixi-workshop.png" alt="A room full of attendees at the pyOpenSci packaging workshop during SciPy 2025, all seated and coding on laptops." class="figure__image">
 &lt;/picture>
 &lt;/a>&lt;/figure>

&lt;p>&lt;a href="https://www.scipy2025.scipy.org/">SciPy 2025&lt;/a> was one for the books, and for &lt;a href="https://www.pyopensci.org/">pyOpenSci&lt;/a>, it was a powerful reminder of how far our community has come and how much energy we bring when we show up together.&lt;/p>
&lt;p>This year, more than 15 members of the pyOpenSci community participated in the conference. We hosted a workshop, facilitated a BoF session with over 60 participants, gave talks, and filled the hallway track with laughter, advice, and real conversations about scientific Python pain points and the future of research software. We also led a community sprint where contributors opened over 30 issues and pull requests—an incredible showing of collaboration across experience levels.&lt;/p></description></item><item><title>pyOpenSci at SciPy 2025 - science, Python and Community</title><link>https://www.pyopensci.org/blog/pyopensci-at-scipy-2025.html</link><pubDate>Mon, 30 Jun 2025 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyopensci-at-scipy-2025.html</guid><description>&lt;h2 id="pyopensci-at-scipy-2025-community-contribution-and-packaging-know-how">pyOpenSci at SciPy 2025: Community, Contribution, and Packaging Know-How&lt;/h2>
&lt;p>We&amp;rsquo;re heading to SciPy 2025 in Tacoma, Washington, and we couldn’t be more excited to connect with the incredible scientific Python community in person! This year, we’re showing up with tutorials, conversations, and community-driven events designed to support open science and lower the barrier to contributing to open source.&lt;/p>
&lt;p>Here&amp;rsquo;s how you can connect with us throughout the conference:&lt;/p>
&lt;h3 id="learn-packaging-with-pyopensci-tutorial">Learn Packaging with pyOpenSci (Tutorial)&lt;/h3>
&lt;p>pyOpenSc is back this year, teaching a hands-on tutorial on &lt;strong>Python packaging for scientific software&lt;/strong>. Whether you’re just getting started or looking to strengthen your skills, this session is for you. You&amp;rsquo;ll leave with a better understanding of how to create Python packages that are shareable, reusable, and aligned with scientific best practices.&lt;/p></description></item><item><title>pyOpenSci at PyCon US 2025 - Python, Packaging and Community</title><link>https://www.pyopensci.org/blog/pyopensci-at-pyconus-2025.html</link><pubDate>Tue, 06 May 2025 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyopensci-at-pyconus-2025.html</guid><description>&lt;div class="admonition admonition--info">
 &lt;div class="admonition__icon">
 &lt;svg fill="none" stroke="currentColor" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg">&lt;path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M13 16h-1v-4h-1m1-4h.01M21 12a9 9 0 11-18 0 9 9 0 0118 0z">&lt;/path>&lt;/svg>
 &lt;/div>
 &lt;div class="admonition__content">&lt;div class="admonition__title">
 TL;DR
 &lt;/div>&lt;div class="admonition__body">&lt;ul>
&lt;li>We’re excited to get back to PyCon US this year!&lt;/li>
&lt;li>Join us for the Maintainers Summit, community events, and the Packaging Summit. At the end of each meeting, we will hold beginner-friendly sprints.&lt;/li>
&lt;li>Join us in our beginner-friendly sprints on Monday / Tuesday following the conference.&lt;/li>
&lt;li>Last year’s recap: &lt;a href="https://www.pyopensci.org/blog/recap-pyos-pyconus-2024.html">Read about pyOpenSci at PyCon US 2024&lt;/a>&lt;/li>
&lt;/ul>
&lt;/div>
 &lt;/div>
&lt;/div>

&lt;h2 id="pycon-us-maintainers-summit-co-hosted-by-pyopensci">PyCon US Maintainers Summit: Co-hosted by pyOpenSci&lt;/h2>
&lt;p>I&amp;rsquo;m thrilled to be a second-time organizer of the PyCon US &lt;a href="https://us.pycon.org/2025/events/maintainers-summit/">Maintainers Summit&lt;/a> alongside long-time organizer &lt;a href="https://github.com/InessaPawson">Inessa Pawson&lt;/a> and Python Steering Council alum and past PyCon chair &lt;a href="https://github.com/mariatta">Mariatta Wijaya&lt;/a>. This annual event brings maintainers, contributors, and community leaders together to share challenges and strategies in maintaining and sustaining open source software.&lt;/p></description></item><item><title>Reaffirming pyOpenSci's Commitment to Inclusion</title><link>https://www.pyopensci.org/blog/pyopensci-commitment-inclusion.html</link><pubDate>Fri, 21 Mar 2025 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyopensci-commitment-inclusion.html</guid><description>&lt;p>During challenging times, it’s critical to pause and reflect on who we are, what we care about, and why our work matters. Since its inception, pyOpenSci, a global community fiscally sponsored in the U.S., has been committed to actively building an inclusive, welcoming, open source community of practice that supports better, more open science. Our Code of Conduct reinforces our &lt;a href="https://www.pyopensci.org/handbook/CODE_OF_CONDUCT.html">values,&lt;/a> as does the thought that we put into the events that we run, the accessible resources that we develop, and the work that we do to make our &lt;a href="https://www.pyopensci.org/#broadening-participation-in-scientific-open-source">peer review program inclusive&lt;/a> and &lt;a href="https://www.pyopensci.org/python-package-guide/tutorials/intro.html">creating Python software easier&lt;/a>.&lt;/p></description></item><item><title>Contribute to Open Source Software: It's More Than just Code</title><link>https://www.pyopensci.org/blog/contribute-to-open-source-lessons.html</link><pubDate>Tue, 18 Mar 2025 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/contribute-to-open-source-lessons.html</guid><description>&lt;h2 id="beyond-code-the-social-side-of-open-source">Beyond code: the social side of open source&lt;/h2>
&lt;p>When you think about contributing to open source, you might assume the biggest hurdle for newcomers is technical&amp;ndash;learning Git, using GitHub, and/or writing code. Most contribute to open source guides focus on technical skills. But for many new contributors, the challenge isn’t only technical—it’s social too.&lt;/p>
&lt;p>Receiving open feedback on your contributions in the form of code review, whether code or documentation, &lt;a href="https://osf.io/preprints/psyarxiv/8k5a4_v1">creates anxiety for many&lt;/a>.&lt;/p></description></item><item><title>How to Secure Your Python Packages When Publishing to PyPI</title><link>https://www.pyopensci.org/blog/python-packaging-security-publish-pypi.html</link><pubDate>Thu, 13 Mar 2025 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/python-packaging-security-publish-pypi.html</guid><description>&lt;h2 id="is-your-pypi-publication-workflow-secure">Is your PyPI publication workflow secure?&lt;/h2>
&lt;p>We can learn a lot from the Python package breach &lt;a href="https://blog.pypi.org/posts/2024-12-11-ultralytics-attack-analysis/">involving Ultralytics&lt;/a>. This breach highlighted the importance of making our PyPI publishing workflows for Python packages more secure.&lt;/p>
&lt;p>In this breach, hackers exploited a GitHub Actions workflow to inject malicious code into a Python package. This package was then published to PyPI. The outcome: users who downloaded the package unknowingly allowed their machines to be hijacked for Bitcoin mining.&lt;/p></description></item><item><title>Building Momentum for the Future: Reflections on Our First Open Science Festival Week</title><link>https://www.pyopensci.org/blog/pyopensci-reflections-fall-festival-2024.html</link><pubDate>Wed, 05 Mar 2025 00:00:00 -0700</pubDate><guid>https://www.pyopensci.org/blog/pyopensci-reflections-fall-festival-2024.html</guid><description>&lt;h2 id="our-inaugural-fall-festival-was-a-great-success">Our inaugural fall festival was a great success!&lt;/h2>
&lt;p>Three years ago, I envisioned an online event where our community could come together to celebrate open source and open science, share knowledge, and learn new skills. Last month, that vision became reality with pyOpenSci’s first-ever &lt;a href="https://www.pyopensci.org/events/pyopensci-2024-fall-festival.html">Fall Festival, held from October 28 to November 1&lt;/a>. The event brought together &lt;strong>64 participants&lt;/strong> from over &lt;strong>15 countries&lt;/strong>—a global mix of researchers, developers, educators, and Python enthusiasts.&lt;/p></description></item><item><title>2024: A Transformative Year for pyOpenSci</title><link>https://www.pyopensci.org/blog/2024-pyopensci-retrospective.html</link><pubDate>Fri, 07 Feb 2025 00:00:00 -0700</pubDate><guid>https://www.pyopensci.org/blog/2024-pyopensci-retrospective.html</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>In 2024, pyOpenSci’s vibrant community led efforts to make open source science more accessible, inclusive, and equitable for all. We empowered the broader community to create, contribute to, and discover better software through beginner-friendly &lt;a href="https://www.pyopensci.org/events/">training events&lt;/a>, &lt;a href="https://www.pyopensci.org/learn.html#start-learning-beginner-friendly-python-packaging-tutorials">collaborative tutorials&lt;/a>, and &lt;a href="https://www.pyopensci.org/about-peer-review/index.html">software peer review&lt;/a>.&lt;/p>
&lt;figure class="figure">
 &lt;a href="https://www.pyopensci.org/images/pyopensci-general/pyopensci-by-the-numbers-2024.png" class="figure__link">
 &lt;picture class="figure__picture">&lt;source srcset="https://www.pyopensci.org/images/pyopensci-general/pyopensci-by-the-numbers-2024.webp" type="image/webp">&lt;img src="https://www.pyopensci.org/images/pyopensci-general/pyopensci-by-the-numbers-2024.png" alt="Infographic summarizing pyOpenSci&amp;#39;s achievements in 2024 with the title &amp;#39;pyOpenSci 2024: A year of community &amp;amp; growth.&amp;#39; The &amp;#39;Training &amp;amp; Sprints&amp;#39; section shows 7 events and 180 attendees. The &amp;#39;Peer Review&amp;#39; section highlights 39 accepted packages and approximately 100 editors and reviewers. The &amp;#39;Community&amp;#39; section emphasizes 1,436 issues and pull requests submitted, 278 contributors, and 23 new co-developed lessons." class="figure__image">
 &lt;/picture>
 &lt;/a>&lt;/figure>

&lt;p>Looking back, I’m inspired and humbled by what we’ve achieved together:&lt;/p></description></item><item><title>QuadratiK: Collection of Methods Constructed using Kernel-Based Quadratic Distances</title><link>https://www.pyopensci.org/blog/quadratik.html</link><pubDate>Fri, 17 Jan 2025 00:00:00 -0700</pubDate><guid>https://www.pyopensci.org/blog/quadratik.html</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>&lt;code>QuadratiK&lt;/code> provides a suite of methods based on kernel-based quadratic distances, and hence the name!&lt;/p>
&lt;p>&lt;code>QuadratiK&lt;/code> contains several goodness of Fit (GoF) tests such as normality tests and two and k-sample tests. It also includes tests for uniformity on the d-dimensional sphere, a clustering algorithm using Poisson kernel densities, and algorithms for generating random samples from PKBD. &lt;code>QuadratiK&lt;/code> offers graphical functions that enhance user experience by facilitating the validation, visualization, and interpretation of clustering results. Furthermore, it provides methods for meaningful analyses and reproducible inference across diverse fields. A dashboard application with a user-friendly interface is also a part of &lt;code>QuadratiK&lt;/code> to enhance accessibility for practitioners beyond the domain of statistical sciences.&lt;/p></description></item><item><title>CLOSED pyOpenSci is hiring a Communications Lead</title><link>https://www.pyopensci.org/blog/pyopensci-job-communications.html</link><pubDate>Fri, 13 Dec 2024 00:00:00 -0700</pubDate><guid>https://www.pyopensci.org/blog/pyopensci-job-communications.html</guid><description>&lt;p>&lt;strong>We are no longer accepting applications for this position. Thank you for your interest.&lt;/strong>&lt;/p>
&lt;h2 id="closed-job-writer--social-media-specialist">CLOSED Job: writer &amp;amp; social media specialist&lt;/h2>
&lt;p>&lt;em>Last Updated: {{ page.last_modified}}&lt;/em>&lt;/p>
&lt;h3 id="about-the-role">About the role&lt;/h3>
&lt;p>pyOpenSci seeks a talented Writer and Social Media Specialist to enhance our communications and engagement with the scientific Python community. This position involves crafting engaging content highlighting our &lt;a href="https://www.pyopensci.org/lessons/">online learning content&lt;/a>, &lt;a href="https://www.pyopensci.org/python-package-guide/tutorials/intro.html">tutorials&lt;/a>, &lt;a href="https://www.pyopensci.org/events/">events&lt;/a>, and &lt;a href="https://www.pyopensci.org/python-packages.html">package ecosystem&lt;/a> for our social media channels, newsletters, and blog to keep our community informed and inspired. It also involved reviewing and editing educational content. This is an excellent opportunity for someone passionate about open science and skilled in clear, impactful communication. The position requires 10-15 hours per week at a rate of 25-40$/hour based on experience, with the flexibility of remote, part-time work. There is some flexibility in this position week-to-week based on pyOpenSci&amp;rsquo;s deadlines. This is a non-regular, part-time, remote, non-exempt position. This position will report
to the pyOpenSci Executive Director. Applicants must be eligible for employment in the United States.&lt;/p></description></item><item><title>The Human Dimension to Clean, Distributable, and Documented Data Science Code</title><link>https://www.pyopensci.org/blog/human-dimension-clean-documented-data-science-code.html</link><pubDate>Mon, 28 Oct 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/human-dimension-clean-documented-data-science-code.html</guid><description>&lt;p>This post was originally posted on &lt;a href="https://ericmjl.github.io/blog/2024/10/25/the-human-dimension-to-clean-distributable-and-documented-data-science-code/">Eric&amp;rsquo;s blog&lt;/a> in support of the &lt;a href="https://www.pyopensci.org/events/pyopensci-2024-fall-festival.html">2024 pyOpenSci Open Science Fall Festival&lt;/a>.&lt;/p>
&lt;figure class="align-center">
&lt;picture>
 &lt;source srcset="https://www.pyopensci.org/images/blog/2024/eric-ma-blog-post-header.webp" type="image/webp">
 &lt;img src="https://www.pyopensci.org/images/blog/2024/eric-ma-blog-post-header.png" alt="An illustration of a diverse group of people collaboratively analyzing and discussing code displayed on a large transparent screen, surrounded by books, plants, and abstract symbols, set against a vibrant gradient background." />
&lt;/picture>
## Introduction
&lt;p>Since 2016 (8 years now!),
I&amp;rsquo;ve been advocating for data scientists
to apply basic software development practices in their work.
This means making sure that one&amp;rsquo;s work is well-documented &amp;ndash; and thus easily understandable,
working in a way that is portable across machines &amp;ndash; and thus easily accessible,
making sure that one&amp;rsquo;s code is modular &amp;ndash; and thus easy to reuse,
and ensuring that one&amp;rsquo;s code is well-tested &amp;ndash; and thus reliable. (Table 1)
In this post,
we&amp;rsquo;ll dive deeper into why it is crucial for making your work impactful
to consider the psychology of people
who read, install, and use your work.
We&amp;rsquo;ll explore the &amp;ldquo;why&amp;rdquo; behind the &amp;ldquo;what&amp;rdquo;
that will be covered in the upcoming pyOpenSci training course.
This training course will be teaching you a lot of valuable skills - the &amp;ldquo;what to do&amp;rdquo; -
and I&amp;rsquo;d like to help reinforce the &amp;ldquo;why&amp;rdquo; behind all of these.
By understanding the reasoning and motivation behind these practices,
you&amp;rsquo;ll be better equipped to apply them effectively
and adapt them to your specific needs in data science projects.&lt;/p></description></item><item><title>pyOpenSci celebrates Inessa Pawson</title><link>https://www.pyopensci.org/blog/pyopensci-celebrates-inessa-pawson.html</link><pubDate>Thu, 10 Oct 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyopensci-celebrates-inessa-pawson.html</guid><description>&lt;h1 id="pyopensci-celebrates-inessa">pyOpenSci Celebrates Inessa&lt;/h1>
&lt;p>Today, I want to take a moment to celebrate a devoted pyOpenSci community member, colleague, and friend, &lt;a href="https://github.com/InessaPawson/InessaPawson">Inessa&lt;/a>,
who was just awarded the NumFOCUS Community Leadership award. In my opinion, no one is more deserving of recognition for their contributions and dedication
to the open source community. Inessa&amp;rsquo;s day job at &lt;a href="https://otincubator.com/team.html">OpenTeams&lt;/a> is devoted to open source, where she serves as the Open Source Program
Manager. But her open source work extends far beyond her professional role!&lt;/p></description></item><item><title>A Blueprint for the Future: pyOpenSci's Sustainability Model</title><link>https://www.pyopensci.org/blog/pyopensci-funding-sustainability.html</link><pubDate>Tue, 17 Sep 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyopensci-funding-sustainability.html</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>Funding is critical to the success of any nonprofit organization. In this blog post, I&amp;rsquo;ll outline pyOpenSci&amp;rsquo;s sustainability plan. We define sustainability as building a diverse funding &amp;ldquo;portfolio&amp;rdquo; that includes grants and internally generated revenue sources to support our mission, growth, and core activities.&lt;/p>
&lt;h2 id="how-funding-has-propelled-pyopensci-forward">How funding has propelled pyOpenSci forward&lt;/h2>
&lt;p>Funding from &lt;a href="https://sloan.org/">Sloan Foundation&lt;/a> catalyzed pyOpenSci&amp;rsquo;s growth by enabling me to dedicate full-time effort to growing the organization&amp;rsquo;s impact in September 2022. This full-time commitment, paired with support from a fiscal sponsor, &lt;a href="https://www.pyopensci.org/blog/what-pyopensci-accomplished-with-two-years-of-funding.html">catalyzed pyOpenSci&amp;rsquo;s recent growth and success&lt;/a>.&lt;/p></description></item><item><title>It's Been a Long Short Road: The Monumental Past 2 Years of pyOpenSci</title><link>https://www.pyopensci.org/blog/what-pyopensci-accomplished-with-two-years-of-funding.html</link><pubDate>Fri, 30 Aug 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/what-pyopensci-accomplished-with-two-years-of-funding.html</guid><description>&lt;h2 id="its-been-two-years-since-i-started-working-full-time-on-pyopensci">It&amp;rsquo;s been two years since I started working full-time on pyOpenSci&lt;/h2>
&lt;p>I have been working full-time building pyOpenSci for two years now, thanks to funding from the &lt;a href="https://sloan.org/">Sloan Foundation&lt;/a> and &lt;a href="https://chanzuckerberg.com/">CZI (Chan Zuckerberg Initiative)&lt;/a>. pyOpenSci has come SO FAR in two years.&lt;/p>
&lt;p>It&amp;rsquo;s time to take a breath and celebrate everything the pyOpenSci community has accomplished. Before we move on to the next big thing—&lt;a href="https://www.pyopensci.org/events/pyopensci-2024-fall-festival.html">our pyOpenSci Fall Festival&lt;/a> (more on that below)—I want to take a moment to reflect on:&lt;/p></description></item><item><title>pyOpenSci @ SciPy 2024 - Python Packaging Tutorials, Talks and Community :heart:</title><link>https://www.pyopensci.org/blog/pyos-scipy-2024-recap.html</link><pubDate>Fri, 02 Aug 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyos-scipy-2024-recap.html</guid><description>&lt;div class="admonition admonition--info">
 &lt;div class="admonition__icon">
 &lt;svg fill="none" stroke="currentColor" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg">&lt;path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M13 16h-1v-4h-1m1-4h.01M21 12a9 9 0 11-18 0 9 9 0 0118 0z">&lt;/path>&lt;/svg>
 &lt;/div>
 &lt;div class="admonition__content">&lt;div class="admonition__title">
 TL;DR
 &lt;/div>&lt;div class="admonition__body">&lt;ul>
&lt;li>pyOpenSci lead 3 incredibly successful events at &lt;a href="https://www.scipy2024.scipy.org/">SciPy&lt;/a> this year: A tutorial,
a talk and a 1.5 day sprint.&lt;/li>
&lt;li>During our SciPy 2024 meeting sprint we had over 35 GitHub issues and pull requests submitted by XX new contributors.&lt;/li>
&lt;li>Our tutorial had over 30 attendees. Almost all of the learners had never created a Python package before, and most of them were successful creating their first Python package.&lt;/li>
&lt;li>I thoroughly enjoyed connecting with new and old colleagues and friends.&lt;/li>
&lt;/ul>
&lt;/div>
 &lt;/div>
&lt;/div>

&lt;h2 id="pyopenscis-fourth-year-attending-scipy---my-experience">pyOpenSci&amp;rsquo;s fourth year attending SciPy - my experience&lt;/h2>
&lt;p>This year was my fourth time attending the annual SciPy meeting—a meeting
organized by &lt;a href="https://www.numfocus.org">NumFocus&lt;/a> that celebrates the scientific
Python ecosystem. My first experience was in 2019, where we held the very first
pyOpenSci Birds of a Feather (BoF) session.&lt;/p></description></item><item><title>pyOpenSci Community News: August 2024</title><link>https://www.pyopensci.org/blog/pyos-community-news-aug-2024.html</link><pubDate>Fri, 02 Aug 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyos-community-news-aug-2024.html</guid><description>&lt;h2 id="i-classfa-regular-fa-hearti-pyopensci-community-news">&lt;i class="fa-regular fa-heart">&lt;/i> pyOpenSci community news&lt;/h2>
&lt;p>As the pyOpenSci community has continued to grow, we wanted to dedicate at least one newsletter issue a month to sharing conversations, contributions, and news related to our diverse and vibrant community! This month we’re celebrating everyone who’s participated in a pyOpenSci sprint, sharing the exciting news around the Spanish translation of our Python Packaging Guide, and elevating a discussion from GitHub around the use of Hatch for Python package creation.&lt;/p></description></item><item><title>pyOpenSci beginner-friendly sprints at PyCon US 2024</title><link>https://www.pyopensci.org/blog/pyopensci-pyconus-2024-sprints.html</link><pubDate>Wed, 31 Jul 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyopensci-pyconus-2024-sprints.html</guid><description>&lt;h2 id="pyopenscis-approach-to-beginner-friendly-sprints">pyOpenSci&amp;rsquo;s approach to beginner-friendly sprints&lt;/h2>
&lt;p>In previous posts, I talked about:&lt;/p>
&lt;ul>
&lt;li>Our &lt;a href="https://www.pyopensci.org/blog/recap-pyos-pyconus-2024.html">incredible experience at PyCon US 2024&lt;/a>.&lt;/li>
&lt;li>My &lt;a href="https://www.pyopensci.org/blog/python-packaging-friends-dont-let-friends-package-alone.html">personal experiences with the Python packaging ecosystem and building consensus
within the scientific Python community&lt;/a>.&lt;/li>
&lt;/ul>
&lt;p>Here, I will share with you what we have learned at pyOpenSci through holding
beginner-friendly sprints over the past two years.
Specifically, I want to
explore the varied motivations and barriers associated with contributions to
open source, and how pyOpenSci is addressing them.&lt;/p></description></item><item><title>automata: Simulation and manipulation</title><link>https://www.pyopensci.org/blog/automata.html</link><pubDate>Wed, 10 Jul 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/automata.html</guid><description>&lt;p>Automata are abstract machines used to represent models of computation, and are a central object of study in theoretical computer science. Given an input string of characters over a fixed alphabet, these machines either accept or reject the string. A language corresponding to an automaton is
the set of all strings it accepts. Three important families of automata in increasing order of generality are the following:&lt;/p>
&lt;ol>
&lt;li>Finite-state automata&lt;/li>
&lt;li>Pushdown automata&lt;/li>
&lt;li>Turing machines&lt;/li>
&lt;/ol>
&lt;p>The &lt;a href="https://caleb531.github.io/automata/">&lt;code>automata&lt;/code>&lt;/a> package facilitates working with these families by allowing simulation of reading input and higher-level manipulation
of the corresponding languages using specialized algorithms. For an overview on automata theory, see &lt;a href="https://en.wikipedia.org/wiki/Automata_theory">this Wikipedia article&lt;/a>, and
for a more comprehensive introduction to each of these topics, see &lt;a href="https://jeffe.cs.illinois.edu/teaching/algorithms/#models">these lecture notes&lt;/a>.&lt;/p></description></item><item><title>pyOpenSci's Guide to SciPy</title><link>https://www.pyopensci.org/blog/pyos-guide-to-scipy-2024.html</link><pubDate>Thu, 20 Jun 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyos-guide-to-scipy-2024.html</guid><description>&lt;h2 id="i-classfa-regular-fa-handshakei-see-you-at-scipy">&lt;i class="fa-regular fa-handshake">&lt;/i> See you at SciPy!&lt;/h2>
&lt;p>&lt;a href="https://www.scipy2024.scipy.org/">SciPy 2024&lt;/a> is just around the corner. We can’t wait to see you there! We’re pulling together our pyOpenSci Guide to SciPy, similar to the guide we did for &lt;a href="https://www.pyopensci.org/blog/pyos-guide-to-pyconus-2024.html">PyCon 2024&lt;/a>, and wanted to give you a preview of some of the tutorials and talks being given by pyOpenSci Community members!&lt;/p>
&lt;h2 id="i-classfa-solid-fa-chalkboard-useri-tutorials">&lt;i class="fa-solid fa-chalkboard-user">&lt;/i> Tutorials&lt;/h2>
&lt;h3 id="interactive-data-visualizations-with-bokeh-in-2024httpscfpscipyorg2024talkjrlmld">&lt;a href="https://cfp.scipy.org/2024/talk/JRLMLD/">Interactive data visualizations with Bokeh (in 2024)&lt;/a>&lt;/h3>
&lt;p>Along with Timo Metzger and Bryan Van de Ven, pyOpenSci community member &lt;a href="https://www.linkedin.com/in/pavithraes/">Pavithra Eswaramoorthy&lt;/a> will be covering everything you need to know to create beautiful and powerful interactive plots from scratch using Bokeh’s latest features. Starting with a quick introduction of Bokeh’s core concepts, the team will cover creating and customizing simple static plots like line and bar charts before introducing layers of interactivity, creating specialized plotting features like geographic maps, contour plots, Mathematical Text, and discussing new additions to Bokeh like ImageStacks. By the end, you will be able to create a complete interactive dashboard using Bokeh.&lt;/p></description></item><item><title>Get Involved with pyOpenSci</title><link>https://www.pyopensci.org/blog/get-involved-with-pyos.html</link><pubDate>Thu, 06 Jun 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/get-involved-with-pyos.html</guid><description>&lt;h2 id="i-classfa-regular-fa-hearti-the-pyopensci-mission">&lt;i class="fa-regular fa-heart">&lt;/i> The pyOpenSci mission&lt;/h2>
&lt;p>Founded in 2018 by our Executive Director, &lt;a href="https://github.com/lwasser">Leah Wasser&lt;/a>, pyOpenSci builds diverse community that supports free and open Python tools for processing scientific data. We also build technical skills needed to contribute to open source and that support open science. While a diverse, inclusive community is at our core, radiating out from it are the three petals–how we accomplish our community goals–of pyOpenSci. These are:&lt;/p>
&lt;ol>
&lt;li>&lt;a href="https://www.pyopensci.org/about-peer-review/index.html">Open peer review of scientific software&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.pyopensci.org/partners.html">Community partnerships&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.pyopensci.org/blog/pyos-education-announcement.html">Training and open educational resources&lt;/a>&lt;/li>
&lt;/ol>
&lt;h2 id="i-classfa-solid-fa-bullhorni-promote-pyopensci-online-and-in-person">&lt;i class="fa-solid fa-bullhorn">&lt;/i> Promote pyOpenSci online and in-person&lt;/h2>
&lt;p>pyOpenSci is active on both &lt;a href="https://www.linkedin.com/company/pyopensci">LinkedIn&lt;/a> and &lt;a href="https://fosstodon.org/@pyOpenSci">Fosstodon&lt;/a>, and you’re welcome to tag us on social media, as well as to &lt;a href="mailto:media@pyopensci.org">reach out with questions&lt;/a>! We also have &lt;a href="https://docs.google.com/presentation/d/1glwf3BEPxo5H6pOHp6d55r2sbw8x-8kQZ9GzoLXwEDc/edit?usp=drive_link">a series of brand assets and guidelines&lt;/a> if you need a copy of our logo, information on our fonts, and/or access to various illustrations we use.&lt;/p></description></item><item><title>Friends don't let friends package alone- my Python packaging talk at PyCon 2024</title><link>https://www.pyopensci.org/blog/python-packaging-friends-dont-let-friends-package-alone.html</link><pubDate>Wed, 05 Jun 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/python-packaging-friends-dont-let-friends-package-alone.html</guid><description>&lt;h2 id="i-classfa-solid-fa-hearti--python-packaging-and-community-my-first-talk-at-pycon-us-2024">&lt;i class="fa-solid fa-heart">&lt;/i> Python packaging and community: my first talk at PyCon US 2024&lt;/h2>
&lt;p>This year I gave my first talk in the &lt;a href="https://us.pycon.org/2024/">PyCon US&lt;/a> main track! For context, PyCon US is a big meeting—with over 2,700 registrations this year—a record for the event! My talk was about my experiences navigating the packaging ecosystem from a few perspectives:&lt;/p>
&lt;ul>
&lt;li>Teaching scientists how to share their code,&lt;/li>
&lt;li>As a maintainer of a smaller Python package—stravalib and&lt;/li>
&lt;li>Founder and Executive Director of a non profit organization - pyOpenSci - which strives to support scientists in tackling the world&amp;rsquo;s greatest challenges using open software and workflows.&lt;/li>
&lt;/ul>
&lt;p>The irony of these three different perspectives is that the challenges that users face in each category are similar! Below I explore my experiences pulling together the talk.&lt;/p></description></item><item><title>SLEPLET: Slepian Scale-Discretised Wavelets in Python</title><link>https://www.pyopensci.org/blog/sleplet-slepian-wavelets.html</link><pubDate>Mon, 03 Jun 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/sleplet-slepian-wavelets.html</guid><description>&lt;p>&lt;a href="https://github.com/astro-informatics/sleplet">SLEPLET&lt;/a> is a Python package for
the construction of Slepian wavelets in the spherical and manifold (via meshes)
settings. In contrast to other codes, &lt;code>SLEPLET&lt;/code> handles any spherical region as
well as the general manifold setting. The API is documented and easily
extendible, designed in an object-orientated manner. Upon installation,
&lt;code>SLEPLET&lt;/code> comes with two command line interfaces - &lt;code>sphere&lt;/code> and &lt;code>mesh&lt;/code> - that
allow one to easily generate plots on the sphere and a set of meshes using
&lt;a href="https://github.com/plotly/plotly.py">plotly&lt;/a>. Whilst these scripts are the
primary intended use, &lt;code>SLEPLET&lt;/code> may be used directly to generate the Slepian
coefficients in the spherical/manifold setting and use methods to convert these
into real space for visualisation or other intended purposes. The construction
of the sifting convolution was required to create Slepian wavelets. As a result,
there are also many examples of functions on the sphere in harmonic space
(rather than Slepian) that were used to demonstrate its effectiveness. &lt;code>SLEPLET&lt;/code>
has been used in the development of several papers.&lt;/p></description></item><item><title>pyOpenSci at PyCon US 2024 - Python packaging and community</title><link>https://www.pyopensci.org/blog/recap-pyos-pyconus-2024.html</link><pubDate>Thu, 30 May 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/recap-pyos-pyconus-2024.html</guid><description>&lt;div class="admonition admonition--info">
 &lt;div class="admonition__icon">
 &lt;svg fill="none" stroke="currentColor" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg">&lt;path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M13 16h-1v-4h-1m1-4h.01M21 12a9 9 0 11-18 0 9 9 0 0118 0z">&lt;/path>&lt;/svg>
 &lt;/div>
 &lt;div class="admonition__content">&lt;div class="admonition__title">
 TL;DR
 &lt;/div>&lt;div class="admonition__body">&lt;ul>
&lt;li>pyOpenSci had a strong presence at &lt;a href="https://us.pycon.org/2024/">PyCon US&lt;/a> this year. I hope this continues for years to come! We held an open space, helped run the &lt;a href="https://us.pycon.org/2024/events/maintainers-summit/">Maintainers Summit&lt;/a> (lead by &lt;a href="https://github.com/InessaPawson">Inessa Pawson&lt;/a> for 5 years and counting), gave &lt;a href="https://us.pycon.org/2024/schedule/presentation/34/">a talk on Python packaging&lt;/a> and ran a 1 day sprint where over 16 people contributed to our efforts.&lt;/li>
&lt;li>pyOpenSci’s theme this year for PyConUS was people first: people first when trying to make technical concepts easier to understand, people first when trying to write good tutorials or documentation and people first when you are trying to solve the world’s hardest problems.&lt;/li>
&lt;li>Giving a talk on packaging at pyConUS triggered every ounce of the imposter in me. But in the end it was a rewarding experience. Having friends in the audience made a world of difference. It was calming to focus on people who I know support both me and this vibrant organization. Friends really should never let friends…package…or use Python…or do anything technical…alone.&lt;/li>
&lt;/ul>
&lt;/div>
 &lt;/div>
&lt;/div>

&lt;h2 id="another-year-another-incredible-pycon">Another year, another incredible PyCon&lt;/h2>
&lt;p>Wow! I wasn’t sure it would be possible to top &lt;a href="https://www.pyopensci.org/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html">last year’s PyCon US 2023 experience&lt;/a>
in Salt Lake City, but this year&amp;rsquo;s &lt;a href="https://us.pycon.org/2024/">PyConUS 2024&lt;/a> &lt;em>was even better&lt;/em>. People are learning about &lt;a href="https://www.pyopensci.org/">pyOpenSci&lt;/a>. The community is excited to support our mission to &lt;strong>help
scientists create better software and make their science more open and
reproducible&lt;/strong> so they can tackle the world&amp;rsquo;s greatest challenges.&lt;/p></description></item><item><title>pyOpenSci Newsletter: June 2024</title><link>https://www.pyopensci.org/blog/pyos-newsletter-june-2024.html</link><pubDate>Tue, 28 May 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyos-newsletter-june-2024.html</guid><description>&lt;h2 id="i-classfa-regular-fa-commentsi-pycon-was-incredible">&lt;i class="fa-regular fa-comments">&lt;/i> PyCon was incredible!&lt;/h2>
&lt;p>We feel so incredibly fortunate to have connected with so many of you at PyCon US! While we&amp;rsquo;re still recovering from a week of summits, talks, and sprints, we wanted to share this sentiment from our Executive Director and Founder, &lt;a href="https://github.com/lwasser">Leah Wasser&lt;/a>, which she shared on &lt;a href="https://fosstodon.org/@leahawasser">her Fosstodon account&lt;/a>:
&lt;figure class="figure">
 &lt;a href="https://www.pyopensci.org/images/blog/2024/may/leah-pycon.png" class="figure__link">
 &lt;picture class="figure__picture">&lt;img src="https://www.pyopensci.org/images/blog/2024/may/leah-pycon.png" alt="Screenshot of a Fosstodon post from Leah Wasser, reading: In my first few moments at pycon I ran into some of my conda friends &amp;amp; was quickly reminded of why this conference is so powerful. Python is more than a programming language. It&amp;#39;s a community of people who I can geek out with about the most obscure topics. I belong. People care. They care a lot about their work. They care about helping each other learn. While this is a tech conference, it&amp;#39;s really people that make python the vibrant community that it is." class="figure__image">
 &lt;/picture>
 &lt;/a>&lt;/figure>
&lt;/p></description></item><item><title>Save the Date: pyOpenSci's 2024 Open Science Fall Festival</title><link>https://www.pyopensci.org/blog/save-the-date-oss-fall-festival-2024.html</link><pubDate>Fri, 24 May 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/save-the-date-oss-fall-festival-2024.html</guid><description>&lt;h2 id="youre-invited-pyopenscis-open-science-fall-festival-2024">You&amp;rsquo;re invited: pyOpenSci&amp;rsquo;s Open Science Fall Festival 2024&lt;/h2>
&lt;p>Happening &lt;del>September 28&amp;ndash;29th, 2024,&lt;/del> October 28th through November 1st, 2024, the pyOpenSci Open Science Fall Festival will be held entirely online, and be a fantastic opportunity to bring together members of the Python community that create open source, open science tools with the members of the Python community who use these tools. In building this festival, our focus is on a grassroots, community-led event with some big unconference vibes.&lt;/p></description></item><item><title>Volunteers needed: pyOpenSci Editorial Board</title><link>https://www.pyopensci.org/blog/pyos-call-for-editors-may-2024.html</link><pubDate>Thu, 23 May 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyos-call-for-editors-may-2024.html</guid><description>&lt;h2 id="join-the-pyopensci-editorial-board">Join the pyOpenSci Editorial Board&lt;/h2>
&lt;h3 id="were-currently-in-need-of-editors-with-domain-expertise-in-climatology-andor-energy-and-also-accepting-applications-from-all-scientific-domains">We&amp;rsquo;re currently in need of editors with domain expertise in climatology and/or energy, and also accepting applications from all scientific domains&lt;/h3>
&lt;p>Thanks to the efforts of our incredible team of volunteers, pyOpenSci is growing! As a result, we&amp;rsquo;re currently seeing a large number of package submissions to &lt;a href="https://www.pyopensci.org/about-peer-review/index.html">our open peer review process&lt;/a>. In order to continue supporting scientists in the development of open source scientific software, we&amp;rsquo;re looking to add volunteer editors to our Editorial Board.&lt;/p></description></item><item><title>The pyOpenSci Guide to PyCon 2024</title><link>https://www.pyopensci.org/blog/pyos-guide-to-pyconus-2024.html</link><pubDate>Tue, 14 May 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyos-guide-to-pyconus-2024.html</guid><description>&lt;h2 id="i-classfa-solid-fa-hearti-connect-with-the-pyopensci-community-at-pycon-us-2024">&lt;i class="fa-solid fa-heart">&lt;/i> Connect with the pyOpenSci community at PyCon US 2024!&lt;/h2>
&lt;p>We know there are a million things to do and see while at &lt;a href="https://us.pycon.org/2024/">PyCon US 2024&lt;/a> in beautiful Pittsburgh this weekend, so we wanted to compile a list of every talk, keynote, summit, and panel where you can expect to meet some of the fantastic pyOpenSci community members as well as hear from some friends of pyOpenSci!&lt;/p>
&lt;h2 id="i-classfa-regular-fa-calendari-friday-may-17th">&lt;i class="fa-regular fa-calendar">&lt;/i> Friday, May 17th&lt;/h2>
&lt;h3 id="i-classfa-solid-fa-users-between-linesi-1100--430-pm-maintainers-summit">&lt;i class="fa-solid fa-users-between-lines">&lt;/i> 11:00&amp;ndash;4:30 PM: Maintainers Summit&lt;/h3>
&lt;p>&lt;em>Room 402, David L. Lawrence Convention Center&lt;/em>&lt;br>
The &lt;a href="https://us.pycon.org/2024/events/maintainers-summit/">Maintainers Summit&lt;/a>, organized by &lt;a href="https://github.com/InessaPawson">Inessa Pawson&lt;/a>, &lt;a href="https://github.com/offbyone">Chris Rose&lt;/a>, &lt;a href="https://github.com/karasowles">Kara Sowles&lt;/a>, and &lt;a href="https://github.com/lwasser">Leah Wasser&lt;/a>, is where the Python community comes together to discuss and foster best practices on how to develop sustainable projects and nurture thriving communities. Check out the video below about what to expect at this year&amp;rsquo;s Maintainers Summit produced by PyCon US 2024 Conference Chair &lt;a href="https://github.com/readme/stories/mariatta-wijaya">Mariatta Wijaya&lt;/a>:&lt;/p></description></item><item><title>pyOpenSci Newsletter: May 2024</title><link>https://www.pyopensci.org/blog/pyos-newsletter-may-2024.html</link><pubDate>Mon, 29 Apr 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyos-newsletter-may-2024.html</guid><description>&lt;h2 id="i-classfa-solid-fa-seedlingi-spring-is-in-the-air">&lt;i class="fa-solid fa-seedling">&lt;/i> Spring is in the Air&lt;/h2>
&lt;p>For those of us in the Northern Hemisphere, spring seems to have finally sprung. It’s a lovely time of year, filled with growth, opportunity, and new beginnings. And for all of us here in the pyOpenSci it’s brought new packages, new opportunities, and new projects that we can’t wait to share with you!&lt;/p>
&lt;h2 id="i-classfa-solid-fa-chalkboard-useri-pyopenscis-first-workshop-was-a-success">&lt;i class="fa-solid fa-chalkboard-user">&lt;/i> pyOpenSci’s first workshop was a success!&lt;/h2>
&lt;p>&lt;figure class="figure">
 &lt;a href="https://www.pyopensci.org/images/blog/2024/may/april-workshop.png" class="figure__link">
 &lt;picture class="figure__picture">&lt;img src="https://www.pyopensci.org/images/blog/2024/may/april-workshop.png" alt="Purple line art of a robot standing in a field of solid purple flowers. The text reads &amp;#39;Build Your First Python Package! a live, online workshop with pyOpenSci. Thursday, April 25th, 2024." class="figure__image">
 &lt;/picture>
 &lt;/a>&lt;figcaption class="figure__caption">Thank you to everyone who made our first workshop such a fun experience!&lt;/figcaption>&lt;/figure>

On Thursday, April 25th, pyOpenSci held its first-ever workshop, titled: &lt;a href="https://www.eventbrite.com/e/build-your-first-python-package-tickets-879586546037">Build Your First Python Package!&lt;/a>. With eight countries represented, we had 28 learners create and install their first Python package using &lt;a href="https://hatch.pypa.io/latest/">Hatch&lt;/a>, all in the course of three hours.&lt;/p></description></item><item><title>rdata: Read R datasets from Python</title><link>https://www.pyopensci.org/blog/read-r-datasets-from-python.html</link><pubDate>Thu, 18 Apr 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/read-r-datasets-from-python.html</guid><description>&lt;p>In the last years Python has solidified itself as the main language for data science and machine learning.
However, the R programming language is also a widely used language in statistics, offering thousands of specialized software packages in this field.
As it is common in the R community, many of these packages include accompanying data, often stored as R objects in the .rds and .rda formats.&lt;/p>
&lt;p>This variety of datasets is normally inaccessible directly from Python programs.
Instead, programmers typically have to open the data in R and manually convert it to another format, such as CSV, which can be understood by Python libraries.
This process requires an R interpreter, it is not fast, nor easy, and may even be impossible to do without information loss.
In particular, for nested structures and complex or custom R types there is no common file exchange format for Python and R that can be used to this purpose.&lt;/p></description></item><item><title>pyOpenSci launches open, accessible, online educational trainings for scientists</title><link>https://www.pyopensci.org/blog/pyos-education-announcement.html</link><pubDate>Tue, 16 Apr 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyos-education-announcement.html</guid><description>&lt;h2 id="the-three-petals-of-pyopensci">The three petals of pyOpenSci&lt;/h2>
&lt;p>&lt;figure class="figure">
 &lt;a href="https://www.pyopensci.org/images/pyopensci-pillars-flower.png" class="figure__link">
 &lt;picture class="figure__picture">&lt;img src="https://www.pyopensci.org/images/pyopensci-pillars-flower.png" alt="The three petals of pyOpenSci, a purple flower with a center and three petals. The center reads &amp;#39;Diverse, Inclusive Community&amp;#39; while the petals, from left to right, read &amp;#39;Software Peer Review&amp;#39;, &amp;#39;Community Partnerships&amp;#39;, &amp;#39;Community Driven Training &amp;amp; Open Education&amp;#39;." class="figure__image">
 &lt;/picture>
 &lt;/a>&lt;figcaption class="figure__caption">The three petals of pyOpenSci&lt;/figcaption>&lt;/figure>

pyOpenSci was founded with the mission to build diverse community that supports free and open Python tools for processing scientific data. We also build the technical skills needed to contribute to open source and that support open science. While a diverse, inclusive community is at our core, radiating out from it are the three petals–how we accomplish our community goals–of pyOpenSci. Those are: open peer review, community partnerships, and training and open educational resources.&lt;/p></description></item><item><title>pyOpenSci Newsletter: April 2024</title><link>https://www.pyopensci.org/blog/pyos-newsletter-april-2024.html</link><pubDate>Mon, 01 Apr 2024 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyos-newsletter-april-2024.html</guid><description>&lt;h2 id="i-classfa-solid-fa-hearti-to-200-and-beyond">&lt;i class="fa-solid fa-heart">&lt;/i> To 200 and beyond!&lt;/h2>
&lt;p>This past month, pyOpenSci reached a major milestone: &lt;a href="https://www.pyopensci.org/our-community/index.html">200 contributors&lt;/a>! We have a diverse and vibrant community of Pythonistas, and are thrilled that 200 (and counting) wonderful people have contributed to pyOpenSci. Will you be next? &lt;a href="https://www.pyopensci.org/volunteer.html">Learn more about getting involved&lt;/a>.&lt;/p>
&lt;h2 id="i-classfa-solid-fa-camerai-launched-editor-spotlight">&lt;i class="fa-solid fa-camera">&lt;/i> Launched: editor spotlight&lt;/h2>
&lt;p>pyOpenSci editors are volunteers who fulfill a critical role within pyOpenSci. Editors lead the open peer review process for three to four Python packages a year, and also weigh in on group editorial decisions. With everything they do for pyOpenSci, we wanted to celebrate them! In March we kicked off our pyOpenSci editor spotlight, where every Wednesday we share a short interview with one of our editors. You can catch up with previous spotlights, and stay tuned for more, on both our &lt;a href="https://fosstodon.org/@pyOpenSci">Fosstodon&lt;/a> and &lt;a href="https://www.linkedin.com/company/pyopensci">LinkedIn&lt;/a> pages.&lt;/p></description></item><item><title>pyOpenSci Newsletter: March 2024</title><link>https://www.pyopensci.org/blog/pyos-newsletter-march-2024.html</link><pubDate>Fri, 01 Mar 2024 00:00:00 -0700</pubDate><guid>https://www.pyopensci.org/blog/pyos-newsletter-march-2024.html</guid><description>&lt;h2 id="i-classfa-solid-fa-rocketi-welcome-astropy">&lt;i class="fa-solid fa-rocket">&lt;/i> Welcome, AstroPy&lt;/h2>
&lt;p>pyOpenSci has officially partnered with the &lt;a href="https://www.astropy.org/">AstroPy Project&lt;/a> through our &lt;a href="https://www.pyopensci.org/partners.html">Community Partnership program&lt;/a>. AstroPy is a Community Python Library for Astronomy, and the AstroPy Project is a community effort to develop a single core package for Astronomy in Python, while also fostering interoperability between Python astronomy packages. We&amp;rsquo;re thrilled to be partnering with the AstroPy project, and can&amp;rsquo;t wait to share more!
&lt;figure class="figure">
 &lt;a href="https://www.pyopensci.org/images/newsletter/04-2024-newsletter/peer-review-partners-process.png" class="figure__link">
 &lt;picture class="figure__picture">&lt;img src="https://www.pyopensci.org/images/newsletter/04-2024-newsletter/peer-review-partners-process.png" alt="Three sequential arrows, with the first reading &amp;#39;submit your package&amp;#39;, the second reading &amp;#39;Review, pyOpenSci standards&amp;#39;, and the third reading &amp;#39;Accepted, pyOpenSci &amp;#43; Community Affiliated&amp;#39;. Below the arrows is a box beneath &amp;#39;Review&amp;#39; that says &amp;#39;Your Community Standards&amp;#39;, with an input arrow reading &amp;#39;Customized review&amp;#39;." class="figure__image">
 &lt;/picture>
 &lt;/a>&lt;figcaption class="figure__caption">pyOpenSci adds an extra layer of community-specific review to our established open peer review process. This allows domain-specific scientific Python communities to vet affiliated tools through our robust peer review process. Communities then don&amp;rsquo;t have to develop and maintain their own review processes and software guidelines.&lt;/figcaption>&lt;/figure>
&lt;/p></description></item><item><title>CZI Funds pyOpenSci</title><link>https://www.pyopensci.org/blog/czi-funds-pyOpenSci-2024.html</link><pubDate>Wed, 03 Jan 2024 00:00:00 -0700</pubDate><guid>https://www.pyopensci.org/blog/czi-funds-pyOpenSci-2024.html</guid><description>&lt;h2 id="a-bright-2024-is-ahead-for-pyopensci">A bright 2024 is ahead for pyOpenSci&lt;/h2>
&lt;p>We are thrilled to announce that pyOpenSci has received 2 years of funding to cover core operations from the &lt;a href="https://chanzuckerberg.com/">Chan Zuckerberg Initiative (CZI)&lt;/a>. These CZI funds will be used to continue critical pyOpenSci work that:&lt;/p>
&lt;ul>
&lt;li>supports Python open source maintainers in developing the usable and maintainable scientific software the enables open science;&lt;/li>
&lt;li>helps scientists navigate a complex Python packaging ecosystem;&lt;/li>
&lt;li>diversifies the scientific Python open source community.&lt;/li>
&lt;/ul>
&lt;h2 id="open-science-builds-trust-and-enables-more-people-to-participate">Open science builds trust and enables more people to participate&lt;/h2>
&lt;p>Open and reproducible science builds trust and accelerates research and
discovery. Open science supports scientific research that is both transparent and
reusable. Free and open source software is critical to open science as it ensures that
the analyses of research data are broadly accessible. To build truly open research workflows, scientists need to use free and open source software (FOSS). FOSS removes the barriers that licenses and other fees may create making diverse participation more accessible.&lt;/p></description></item><item><title>👋 Hello, world! Greetings from the new pyOS Community Manager</title><link>https://www.pyopensci.org/blog/pyOpenSci-new-community-manager.html</link><pubDate>Wed, 29 Nov 2023 00:00:00 -0700</pubDate><guid>https://www.pyopensci.org/blog/pyOpenSci-new-community-manager.html</guid><description>&lt;h2 id="chicago-cats-and-community">Chicago, cats, and community&lt;/h2>
&lt;p>I’m thrilled to be joining pyOpenSci (pyOS) as the Community Manager, and bringing my experiences as a researcher, educator, and developer advocate to support the creation and maintenance of free and open Python tools for processing scientific data. I’ve spent most of my adult life building online communities, from video games to programming to data science, and it’s exciting to see so many familiar faces in my first weeks at pyOS.&lt;/p></description></item><item><title>pyOpenSci Python packaging discussion at the Research Software Engineering meeting 2023</title><link>https://www.pyopensci.org/blog/pyOpenSci-research-software-2023.html</link><pubDate>Wed, 18 Oct 2023 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyOpenSci-research-software-2023.html</guid><description>&lt;h2 id="intro">Intro&lt;/h2>
&lt;p>In October 2023, the United States Research Software Engineering (US-RSE),
funded by the Sloan foundation, held its very first ever
&lt;a href="https://us-rse.org/usrse23/">meeting&lt;/a>.&lt;/p>
&lt;p>I attended this meeting and lead a community session around our peer review
process and Python packaging. Key TL&amp;amp;DR takeaways were:&lt;/p>
&lt;ol>
&lt;li>Many RSE&amp;rsquo;s use Python (the show of hands in the main conference room on day 2 suggested 60-70% of them use it in their daily work)&lt;/li>
&lt;li>Most feel like the packaging ecosystem can be confusing to navigate given there are numerous ways of creating a Python package&lt;/li>
&lt;li>RSE&amp;rsquo;s are using a suite of different packaging tools and approaches in their Python work.&lt;/li>
&lt;/ol>
&lt;p>The good news take away is that the exact pain points described to me at this
meeting are the ones that pyOpenSci is taking on. We are currently working on
an end-to-end packaging tutorial that hopefully will shed light on and demystify
a complex but vibrant ecosystem of Python packaging tools and options.&lt;/p></description></item><item><title>CLOSED: pyOpenSci is Hiring a Community Manager</title><link>https://www.pyopensci.org/blog/pyOpenSci-hiring-community-manager-fall-2023.html</link><pubDate>Mon, 11 Sep 2023 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pyOpenSci-hiring-community-manager-fall-2023.html</guid><description>&lt;div class="admonition admonition--info">
 &lt;div class="admonition__icon">
 &lt;svg fill="none" stroke="currentColor" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg">&lt;path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M13 16h-1v-4h-1m1-4h.01M21 12a9 9 0 11-18 0 9 9 0 0118 0z">&lt;/path>&lt;/svg>
 &lt;/div>
 &lt;div class="admonition__content">&lt;div class="admonition__body">&lt;strong>IMPORTANT:&lt;/strong> we are no longer accepting applications for this position.
Thank you for your interest.&lt;/div>
 &lt;/div>
&lt;/div>

&lt;h2 id="job-posting-pyopensci-community-manager">Job Posting: pyOpenSci Community Manager&lt;/h2>
&lt;p>pyOpenSci is accepting applications for a Community Manager. The Community
Manager supports growth and development of an inclusive pyOpenSci community. Our vibrant community is
dedicated to supporting high quality Python open source software that drives open science.&lt;/p></description></item><item><title>Shark Attacks and Open Science - pyOpenSci @ SciPy 2023 Meeting</title><link>https://www.pyopensci.org/blog/scipy-2023-community.html</link><pubDate>Tue, 18 Jul 2023 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/scipy-2023-community.html</guid><description>&lt;h2 id="i-classfa-solid-fa-fish-finsi-shark-attack---pyopensci-at-scipy">&lt;i class="fa-solid fa-fish-fins">&lt;/i> Shark attack - pyOpenSci at SciPy&lt;/h2>
&lt;p>I was so excited for SciPy this year.&lt;/p>
&lt;p>I wanted to spread the word about pyOpenSci&amp;rsquo;s core mission - supporting
the scientific open source Python community. I wanted to get more people
involved.&lt;/p>
&lt;p>pyOpenSci represents everything that matters most to me:&lt;/p>
&lt;ul>
&lt;li>🌱 Community &amp;amp; People&lt;/li>
&lt;li>🎓 Education&lt;/li>
&lt;li>🔓 Open Science and Open Source&lt;/li>
&lt;li>🌈 Diversity, Equity and Inclusion&lt;/li>
&lt;/ul>
&lt;h2 id="unplanned-is-often-best">Unplanned is often best&lt;/h2>
&lt;p>I am not used to going into a meeting with no specific plans and obligations.
While pyOpenSci didn&amp;rsquo;t get a talk or a community session / BoF this year, we
did get a lightning talk! It was a randomized selection, and I threw my name
into the bucket (literally) with fingers crossed that i&amp;rsquo;d get a lightning talk.&lt;/p></description></item><item><title>My First Time Attending PyCon - A Tale of Sprints and Python Packaging</title><link>https://www.pyopensci.org/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html</link><pubDate>Wed, 14 Jun 2023 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html</guid><description>&lt;h2 id="how-it-all-went-down---pycon-us-2023-salt-lake-city-utah">How it all went down - PyCON US 2023, Salt Lake City, Utah&lt;/h2>
&lt;p>This year was my first time attending pyCon US! I was intimidated to attend such
a big Python meeting. For years i&amp;rsquo;ve attended science meetings such as
AGU (American Geophysical Union), ESRI (GIS) users conferences and ESA (Ecological
Society of America). I&amp;rsquo;ve been to and lead data science hackathons and been to
the annual SciPy meeting. But i&amp;rsquo;ve never been to a pure tech conference.&lt;/p></description></item><item><title>Sorry This Talk Doesn't Have any ChatGPT in It: pyOpenSci peer review of Crowsetta</title><link>https://www.pyopensci.org/blog/pycon2023-crowsetta-peer-review.html</link><pubDate>Tue, 13 Jun 2023 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/pycon2023-crowsetta-peer-review.html</guid><description>&lt;h1 id="pycon-2023-us--david-nicholson-lightning-talk-on-pyopensci-peer-review">pyCon 2023 US -David Nicholson Lightning Talk on pyOpenSci Peer Review&lt;/h1>
&lt;p>David Nicholson, our pyOpenSci Editor in Chief, gave a fantastic lightning talk this year at &lt;a href="https://us.pycon.org/2023/">pyCon US 2023&lt;/a>. This year&amp;rsquo;s pyCon was held in Salt Lake City, Utah in April. David braved the expansive keynote room stage - talking to a gigantic room full of Pythonistas. He spoke about his experience going through our scientific Python software peer review process.&lt;/p></description></item><item><title>Demystifying the Python packaging ecosystem</title><link>https://www.pyopensci.org/blog/demystifying-python-packaging.html</link><pubDate>Wed, 22 Mar 2023 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/demystifying-python-packaging.html</guid><description>&lt;h2 id="a-guide-to-make-python-packaging-easier-for-scientists">A guide to make Python packaging easier for scientists&lt;/h2>
&lt;p>I&amp;rsquo;ve spent the last few months working on creating a Python packaging guide. This guide seeks to help those creating new scientific Python packages select a packaging tool and workflow. This guide also supports the &lt;a href="https://www.pyopensci.org/about-peer-review/">pyOpenSci peer review process&lt;/a>.&lt;/p>
&lt;p>Below, I provide a brief overview of our content development process given the &lt;a href="https://www.pyopensci.org/python-package-guide/package-structure-code/intro.html">packaging tool guide chapter has been published&lt;/a>! Yay!&lt;/p>
&lt;h1 id="tldr">TL;DR&lt;/h1>
&lt;p>There are a few key takeaways from this post:&lt;/p></description></item><item><title>What Makes a Python Open Source Package Healthy? A Conversation on Twitter.</title><link>https://www.pyopensci.org/blog/what-makes-open-source-python-package-healthy.html</link><pubDate>Mon, 21 Nov 2022 00:00:00 -0700</pubDate><guid>https://www.pyopensci.org/blog/what-makes-open-source-python-package-healthy.html</guid><description>&lt;div class="admonition admonition--info">
 &lt;div class="admonition__icon">
 &lt;svg fill="none" stroke="currentColor" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg">&lt;path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M13 16h-1v-4h-1m1-4h.01M21 12a9 9 0 11-18 0 9 9 0 0118 0z">&lt;/path>&lt;/svg>
 &lt;/div>
 &lt;div class="admonition__content">&lt;div class="admonition__title">
 Part 3/3: Blog series on package health
 &lt;/div>&lt;div class="admonition__body">This blog post is part 3 of a 3 part series on open source package health.
The series was inspired by a conversation
held on twitter. This blog post is not a comprehensive perspective on what pyOpenSci
plans to track as an organization. Rather it&amp;rsquo;s a summary of thoughts collect during
the conversation on twitter that we can use to inform our final metrics.&lt;ul>
&lt;li>&lt;a href="https://www.pyopensci.org/blog/why-python-open-source-software-matters-for-scientists.html">In blog 1/3 I discussed why Python open source software matters to scientists (and package maintainers too)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://www.pyopensci.org/blog/why-python-package-health-metrics-matter.html">In blog 2/3 I discussed
why free and open source package metrics matter and which categories of metrics we at pyOpenSci are thinking about tracking.&lt;/a>&lt;/li>
&lt;/ul>
In this post, I&amp;rsquo;ll summarize a conversation that was held on twitter that gaged
what the community thought about metrics to track the health of scientific
Python open source packages.&lt;/div>
 &lt;/div>
&lt;/div>

&lt;h2 id="packages-and-open-source-software-a-few-terms-to-clarify">Packages and open source software, a few terms to clarify&lt;/h2>
&lt;ul>
&lt;li>When I say Python package or Python open source software, I&amp;rsquo;m referring to a
tool that anyone can install to use in their Python environment.&lt;/li>
&lt;li>When I say open source or free and open source software I&amp;rsquo;m referring to Python tools that are free to download and and their code is openly available for anyone to see (open source).&lt;/li>
&lt;/ul>
&lt;h2 id="what-is-package-health-anyway">What is package health anyway?&lt;/h2>
&lt;p>There are many different ways to think about and evaluate open source
Python package health.&lt;/p></description></item><item><title>Why Python package health metrics are a priority for pyOpenSci and other open source communities</title><link>https://www.pyopensci.org/blog/why-python-package-health-metrics-matter.html</link><pubDate>Mon, 07 Nov 2022 00:00:00 -0700</pubDate><guid>https://www.pyopensci.org/blog/why-python-package-health-metrics-matter.html</guid><description>&lt;div class="admonition admonition--info">
 &lt;div class="admonition__icon">
 &lt;svg fill="none" stroke="currentColor" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg">&lt;path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M13 16h-1v-4h-1m1-4h.01M21 12a9 9 0 11-18 0 9 9 0 0118 0z">&lt;/path>&lt;/svg>
 &lt;/div>
 &lt;div class="admonition__content">&lt;div class="admonition__title">
 Part 2/3: Blog series on package health
 &lt;/div>&lt;div class="admonition__body">This blog is the second in a 3 part series. &lt;a href="https://www.pyopensci.org/blog/why-python-open-source-software-matters-for-scientists.html">In the previous blog post,&lt;/a>
I discussed why the health of (Python) open source
packages should matter to you as a scientist (and as a person who values and
uses free and open source tools in your workflow). In this post, I&amp;rsquo;ll talk
more about why collecting metrics are critical to both program development success
and to the success of open source tools. I&amp;rsquo;ll wrap up this series
&lt;a href="https://www.pyopensci.org/blog/what-makes-open-source-python-package-healthy.html">with a discussion on what types of package metrics pyOpenSci should be collecting
around the free and open source Python packages that you use.&lt;/a>.NOTE: all of this is in the context of a conversation on Twitter. It is not a
comprehensive perspective on the final metrics that pyOpenSci plans to collect.&lt;/div>
 &lt;/div>
&lt;/div>

&lt;h2 id="metrics-are-critical-to-the-development-of-any-program">Metrics are critical to the development of any program&lt;/h2>
&lt;p>I&amp;rsquo;ve created a few open science focused programs now from the ground up. One at
NEON and another at CU Boulder. When building a new program, one of the first
things that I do (after defining the mission and goals) is to define the metrics
that constitute success.&lt;/p></description></item><item><title>Why should Python open source package health matter to scientists? (and to you!)</title><link>https://www.pyopensci.org/blog/why-python-open-source-software-matters-for-scientists.html</link><pubDate>Mon, 24 Oct 2022 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/why-python-open-source-software-matters-for-scientists.html</guid><description>&lt;div class="admonition admonition--info">
 &lt;div class="admonition__icon">
 &lt;svg fill="none" stroke="currentColor" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg">&lt;path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M13 16h-1v-4h-1m1-4h.01M21 12a9 9 0 11-18 0 9 9 0 0118 0z">&lt;/path>&lt;/svg>
 &lt;/div>
 &lt;div class="admonition__content">&lt;div class="admonition__title">
 Part 1/3: Blog series on package health
 &lt;/div>&lt;div class="admonition__body">&lt;p>This blog post is part 1 of a 3 part series on open source package health.
The series was inspired by a conversation
held on twitter. This blog post is not a comprehensive perspective on what pyOpenSci
plans to track as an organization. Rather it&amp;rsquo;s a summary of thoughts collect during
the conversation on twitter that we can use to inform our final metrics.&lt;/p></description></item><item><title>pyOpenSci Editorial Process - New Editor in Chief and a Call For Editors</title><link>https://www.pyopensci.org/blog/python-software-review-process-editor-in-chief.html</link><pubDate>Tue, 27 Sep 2022 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/python-software-review-process-editor-in-chief.html</guid><description>&lt;h2 id="an-update-on-pyopenscis-review-process">An update on pyOpenSci&amp;rsquo;s review process&lt;/h2>
&lt;p>Hey there! I just wanted to update everyone about where pyOpenSci is with
its peer review process. We are currently hard at work updating &lt;a href="https://www.pyopensci.org/software-peer-review/">our peer review guides&lt;/a> to
streamline the peer review process. For the next 2 months (October &amp;amp; November 2022)
we will prioritize setting up an editorial board to support new reviews as they
come in.&lt;/p>
&lt;p>With that below you will find a few updates.&lt;/p></description></item><item><title>Big Changes for pyOpenSci: an update from the new Executive Director, Leah Wasser</title><link>https://www.pyopensci.org/blog/new-executive-director-leah-wasser.html</link><pubDate>Sat, 10 Sep 2022 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/new-executive-director-leah-wasser.html</guid><description>&lt;h2 id="pyopensci-is-now-an-independent-community-organization">pyOpenSci is now an independent community organization&lt;/h2>
&lt;p>I am thrilled to announce that pyOpenSci is now a fiscally sponsored project of
&lt;a href="https://communityin.org/our-projects/support-a-project/">Community Initiatives&lt;/a>! This means that pyOpenSci now serves the community of
scientific Python users and open source software maintainers. pyOpenSci is not
affiliated with any specific organization. I (Leah) will now be devoting ALL of my
(work :grin: ) time to the pyOpenSci project full time as the official Executive Director.&lt;/p></description></item><item><title>MovingPandas: Data Structures and Methods for Movement Data Analysis</title><link>https://www.pyopensci.org/blog/movingpandas-movement-data-analysis.html</link><pubDate>Wed, 29 Apr 2020 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/movingpandas-movement-data-analysis.html</guid><description>&lt;p>Movement data is everywhere: from tracking apps that record human or vehicle movement to ecologists monitoring wildlife behavior. Movement data analysis is challenging since movement data combines time series and spatial data analyses questions. Existing spatial analysis libraries, such as GeoPandas, are great at handling spatial data but they don&amp;rsquo;t support moving objects.&lt;/p>
&lt;p>MovingPandas aims to fill the gap of missing tools for exploring movement data. It provides data structures and methods for dealing with data of moving objects. MovingPandas has been accepted by pyOpenSci as part of its ecosystem in March 2020.&lt;/p></description></item><item><title>PyOpenSci at AGU 2019: Join Us</title><link>https://www.pyopensci.org/blog/pyopensci-at-agu-2019-python.html</link><pubDate>Tue, 03 Dec 2019 00:00:00 -0700</pubDate><guid>https://www.pyopensci.org/blog/pyopensci-at-agu-2019-python.html</guid><description>&lt;p>Hey all! I&amp;rsquo;m a part of the pyOpenSci Leadership team and Director of the Earth Analytics Education Initiative at Earth Lab, University of
Colorado, Boulder. There are several open source software events that you may
want to consider if you plan to be at AGU 2019 this year in San Francisco.
Please join us to learn more about pyOpenSci and to help shape what pyOpenSci
becomes.&lt;/p>
&lt;p>All are welcome!!&lt;/p>
&lt;h2 id="pyopensci-ignite-talk-tuesday-dec-10-2019-8am-in-moscone-west---2010-l2">pyOpenSci Ignite Talk: Tuesday Dec 10, 2019 8am in Moscone West - 2010, L2&lt;/h2>
&lt;p>I will giving an &lt;a href="https://agu.confex.com/agu/fm19/meetingapp.cgi/Paper/541546" target="_blank">invited ignite talk: pyOpenSci Promoting Open Source Python Software To Support Open Reproducible Science&lt;/a>. This talk is a part of a larger open source software initiative organized by pyOpenSci collaborators
Leonardo Uieda and Lindsey Heagy.&lt;/p></description></item><item><title>Pandera: A Statistical Data Validation Toolkit for Pandas</title><link>https://www.pyopensci.org/blog/pandera-python-pandas-dataframe-validation.html</link><pubDate>Mon, 18 Nov 2019 00:00:00 -0700</pubDate><guid>https://www.pyopensci.org/blog/pandera-python-pandas-dataframe-validation.html</guid><description>&lt;p>Modern data engineering and analysis workflows will often involve using data
manipulation libraries, which, in the Python universe, would be tools like
&lt;a href="https://pandas.pydata.org/">pandas&lt;/a>. One problem you may have encountered with
this powerful data manipulation tool is that the dataframe can be an opaque
object that&amp;rsquo;s hard to reason about in terms of its contents, data types, and
other properties.&lt;/p>
&lt;p>One tool that may help you with this problem is
&lt;a href="https://pandera.readthedocs.io/en/latest/index.html">pandera&lt;/a>, which was
accepted by pyOpenSci as part of its ecosystem of packages on September 2019.
Pandera provides a flexible and expressive data validation toolkit that helps
users make statistical assertions about pandas data structures.&lt;/p></description></item><item><title>Welcome to the pyOpenSci Blog!</title><link>https://www.pyopensci.org/blog/welcome-to-pyopensci/</link><pubDate>Fri, 25 Oct 2019 00:00:00 -0600</pubDate><guid>https://www.pyopensci.org/blog/welcome-to-pyopensci/</guid><description>&lt;h2 id="welcome-to-pyopensci">Welcome To PyOpenSci!&lt;/h2>
&lt;p>This is just a short post to let everyone know that we are starting a community blog post. Here we will write about many things including:&lt;/p>
&lt;ol>
&lt;li>Packages that have gone through the review process.&lt;/li>
&lt;li>Challenges that PyOpenSci is confronting in the open source Python community&lt;/li>
&lt;li>Activities and events going on&lt;/li>
&lt;/ol>
&lt;p>and more.&lt;/p>
&lt;p>Stay tuned for more in the upcoming months!&lt;/p></description></item><item><title>clean-hugo theme: blog formatting and shortcode reference</title><link>https://www.pyopensci.org/blog/clean-hugo-blog-theme-features.html</link><pubDate>Tue, 01 Jan 2019 00:00:00 -0700</pubDate><guid>https://www.pyopensci.org/blog/clean-hugo-blog-theme-features.html</guid><description>&lt;p>This post is a living reference for the clean-hugo theme. Every shortcode
and content-formatting option available in the theme is demonstrated here
with a working example and the code that produces it. Use this post to
test that a theme change has not broken existing content, and as a
copy-paste resource when writing new blog posts.&lt;/p>
&lt;h2 id="figures">Figures&lt;/h2>
&lt;p>The &lt;code>figure&lt;/code> shortcode renders images with optional captions and
automatic WebP support. It generates a &lt;code>&amp;lt;picture&amp;gt;&lt;/code> element with a WebP
&lt;code>&amp;lt;source&amp;gt;&lt;/code> and a fallback &lt;code>&amp;lt;img&amp;gt;&lt;/code>. If a &lt;code>.webp&lt;/code> file exists alongside the
source image, modern browsers use it automatically.&lt;/p></description></item></channel></rss>