pyOpenSci announcement with a festive design. The text reads: ‘See You In 2026! Join us in some mission-critical downtime: 🌱 Peer Review is paused: Dec 22, 2025 – Jan 16, 2026 🌱 Mental health is as important as our work 🌱 Open source thrives when we care for ourselves and our community 💖.’ The graphic includes champagne glasses, balloons, and a person relaxing in a chair, symbolizing rest and celebration.

Hi friends! 👋
pyOpenSci is pausing Peer Review Dec 22, 2025 – Jan 16, 2026. 💖 Reviews will resume after Jan 16, reflecting our values of care and balance. Take time for yourselves this holiday season! See you in 2026—exciting things ahead! 🥂
#OpenScience #community #opensource #python

we love options, but python packaging has too many.

Packaging guru Jeremiah Paige wrote about our values-based rubric for selecting:
🌱 free & open
🤝 inclusive
📐 standards-compliant
💪 well-supported
🎯 opinionated (less paralysis!)

www.pyopensci.org/blog/how-we-...

#python #opensource #openscience

Community is so critical during times of political unrest. We value the members of the pyOpenSci community who work together to make scientific #opensource more accessible and inclusive and to help researchers and others navigating #python packaging and creating open reproducible workflows.

Infographic split into two sections. Left side in dark green with checkmark icon titled 'Do's' lists: Create a src/packagename directory, Add a pyproject.toml instead of setup.py, Create a unique package name, Consider submitting your package to pyOpenSci for peer review. Right side in purple with X icon titled 'Don'ts' lists: Don't try to solve everyone's problems, Worry about publishing to PyPI or conda-forge immediately. Bottom text reads 'Embrace the do's, steer clear of the don'ts, and JOIN a community like pyOpenSci for support along the way.' pyOpenSci logo at top. Link at bottom: bit.ly/pyos-packaging-2025

Your #Python package needs 3 things:
✅ src/packagename directory
✅ pyproject.toml file
✅ unique package name
It does NOT need to:
❌ Solve everyone's problems
❌ Be on PyPI immediately
If your code helps you, it might help others.
Join our workshop for more: Nov 6 💛
bit.ly/pyos-packagi...

A graphic from zero ro Python package. 2 hour packaging workshop. Build a pure Python package using Hatch and UV, publish securely to PyPI, Automate with GitHub actions, and write docs that help users and contributors. Thursday, 6 November 2025. Early bird special is extended. Link: bit.ly/pythonpackaging

🚨 Early bird extended! 🚨
Join our From Zero to Python Package workshop, Nov 6.
Decode the packaging ecosystem: Hatch, PyPI, Uvicorn — and more. Build your package step-by-step. Scholarships available 💛
🔗 bit.ly/pyos-packaging-2025
#OpenScience #Python

Get involved with pyOpenSci pyOpenSci’s Website

So much brilliant work never makes it into a paper.
The code, the data, the long nights helping others debug.
At pyOpenSci, we believe that code, data, and community are the pulse.
Research advances quickly when we build together & openly.
Join us. 💛 bit.ly/pyos-volunteer
#openscience #opensource

Dark purple graphic with the pyOpenSci logo at the top. Large white text reads: “From Zero to Python Package.” Subheading: “A 2-hour packaging workshop with pyOpenSci!” A checklist below includes: Build your first Python package; Publish securely to PyPI; Automate releases with GitHub Actions; Write docs that help users & contributors. Event details: Thursday, 6 November 2025, 10:00 AM MST – 12:15 PM MST. White text at the bottom shows the link: bit.ly/PythonPackaging. A teal button on the right says “REGISTER NOW.” On the right side, there’s a line-drawn robot illustration.

pyOpenSci has supported 50+ Python packages. Now you can learn the same packaging practices in our hands-on workshop with founder @leahawasser.bsky.social.

📅 Nov 6 | 10 AM MST
🎟️ Early bird rates + scholarships
🔗 bit.ly/PythonPackaging

🐍 Make your code easier to share, use & contribute to.

pyOpenSci Workshop: Create a Python package – Stanford Open Source Program Office Python packaging can be tricky to navigate. pyOpenSci will lead a pilot workshop on creating your first Python package. The goal of this workshop is to help scientists learn how to package and make co...

Want your #Python code to be easier to share + reuse? 📦

Join pyOpenSci + #StanfordOSPO for an online workshop:
Create a Python package: make your code easier to share and use

🗓 Thu, Oct 2 · 10 AM MT / 9 AM PT
🔗 pyopensci.org/events/pyopensci-stanford-create-python-package-workshop.html

Purple background with floral illustrations. Text reads: “Get involved with pyOpenSci! We’re growing our editorial team, and are seeking volunteers from a wide variety of scientific backgrounds. Editors: Lead the review process for 3–4 packages a year. Assist with editorial and peer review policies. People from diverse backgrounds are especially encouraged to apply! Questions? Email media@pyopensci.org. Apply: bit.ly/pyOSEditor.” At the bottom are social links: pyopensci.org, Fosstodon @pyOpenSci, LinkedIn pyOpenSci. Illustration shows a person at a desk on a video call with four people.

🚨 Call for editors! 🚨

We’ve got 3️⃣ new pyOpenSci packages ready for review:

✨ Phyleas (hardware security experiments)
✨ LSAPy (land suitability analysis w/ fuzzy logic)
✨ RSTT (sports simulation w/ probabilistic models)

Your expertise could help make scientific software stronger & more reusable.

Have you ever inherited an #opensource project with limited docs?
I am rebuilding the all-contributors bot and the accounts/workflows r undocumented. I'm becoming a PI in search of accounts 😅

Lesson learned: Create a DEVELOPMENT.md file from day one and add everything to it! #openscience

pyOpenSci’s vision? 👀

A research ecosystem where the code behind the science is valued as much as the paper.

Where collaboration is the norm, not the exception.

Where open is the default. 💛

Purple graphic with pyOpenSci logo at the top. Large white text reads: From Zero to Python Package. Subheading: A 2-hour packaging workshop with pyOpenSci! A checklist underneath says: Build your first Python package, Publish securely to PyPI, Automate releases with GitHub Actions, Write docs that help users & contributors. Below, text reads: Thursday, 6 November 2025, 10:00 AM MST – 12:15 PM MST. At the bottom: bit.ly/PythonPackaging with a button that says Register Now. A simple robot illustration is on the right side.

🐍 Want to publish your own Python package?

Join pyOpenSci’s 2-hour online workshop Nov 6:

✔️ Build your first package fast
✔️ Learn the core files (pyproject.toml, docs, metadata)
✔️ Publish to PyPI with confidence

📅 Nov 6, 2025 | Online
🎟️ bit.ly/PythonPackaging

Did you know? 👀

Every pyOpenSci peer review is collaborative, not combative.

Maintainers say that our process leaves their packages stronger, better documented, and more usable...not torn apart.

Your code matters. And we’re here to help it shine! ✨

👉 Learn more: www.pyopensci.org/software-pee...

Purple graphic with pyOpenSci logo at the top. Large white text reads: From Zero to Python Package. Subheading: A 2-hour packaging workshop with pyOpenSci! Bulleted list: “Build your first Python package; Publish securely to PyPI; Automate releases with GitHub Actions; Write docs that help users & contributors.” Below, event details: Thursday, 6 November 2025, 10:00 AM MST – 12:15 PM MST. Link shown: bit.ly/PythonPackaging. On the right is a simple robot illustration. A teal button at the bottom right says REGISTER NOW.

Turn your scripts into a real Python package! 🐍✨

📅 pyOpenSci 2-hour workshop: Nov 6, online.

✅ Build a package in minutes
✅ Learn to publish on PyPI
✅ Practice with GitHub Actions

🎟️ Early bird pricing is live now — scholarships are available!

🔗 www.pyopensci.org/events/pytho...

Logos of the five participating organizations (top to bottom: The Carpentries, PREreview, rOpenSci, OLS, pyOpenSci) enclosed in grey ovals along the border of a larger grey circle. Inside the circle at the top is text in all caps spelling “STRONGER TOGETHER.” Below that is an image of several arms and hands closed in a fist. At the bottom of the image in is text spelling “Building resilience in open science starts with collaboration” with the words “resilience” and “collaboration bolded.

Open science orgs are stronger together 💪

@carpentries.carpentries.org, OLS, @ropensci.org, @pyopensci.org & @prereview.bsky.social are convening to move from surviving → thriving.

Read how we’re charting a sustainable, collective path forward: www.pyopensci.org/blog/pyopens... #OpenScience #FOSS

Purple background with floral illustrations. Text reads: “Get involved with pyOpenSci! We’re growing our editorial team, and are seeking volunteers from a wide variety of scientific backgrounds. Editors: Lead the review process for 3–4 packages a year. Assist with editorial and peer review policies. People from diverse backgrounds are especially encouraged to apply! Questions? Email media@pyopensci.org. Apply: bit.ly/pyOSEditor.” At the bottom are social links: pyopensci.org, Fosstodon @pyOpenSci, LinkedIn pyOpenSci. Illustration shows a person at a desk on a video call with four people.

🚨 Call for editors! 🚨

We’ve got 3️⃣ new pyOpenSci packages ready for review:

✨ Phyleas (hardware security experiments)
✨ LSAPy (land suitability analysis w/ fuzzy logic)
✨ RSTT (sports simulation w/ probabilistic models)

Your expertise could help make scientific software stronger & more reusable.

Purple graphic with pyOpenSci logo and text: “From Zero to Python Package — A 2-hour packaging workshop with pyOpenSci.” Bullet points: Build your first Python package; Publish securely to PyPI; Automate releases with GitHub Actions; Write docs that help users & contributors. Event details: Thursday, 6 November 2025, 10:00 AM–12:15 PM MST. URL: bit.ly/PythonPackaging. A “Register Now” button appears at the bottom right. Decorative line-art robot stands on the right side.

Want your Python code to be installable + reusable? 🐍📦

Join pyOpenSci’s 2-hour workshop From Zero to Python Package (Nov 6). Build your first package, learn PyPI publishing, and automate with GitHub Actions.

👀 See the graphic for registration!

Python packaging 101 A start to finish beginner-friendly tutorial Welcome to the pyOpenSci Python packaging tutorial series. The lessons on the upcoming pages walk you through the core steps needed to create a Python p...

Want to share your Python code with the world? 🌍

Start small: build a package.

Our beginner-friendly guide shows you how →
www.pyopensci.org/python-packa...

Your science. Your code. Your impact. ✨

Hot take 🔥

Reproducibility isn’t just about data and methods. It’s about scientific software.

If your code can’t be run, your science can’t be trusted.

Let’s fix that together. 💜

#OpenScience

pyOpenSci’s vision?

A research ecosystem where the code behind the science is valued as much as the paper.

Where collaboration is the norm, not the exception.

Where open is the default.

GitHub - pyOpenSci/software-submission: Interested in having your Python package reviewed according to pyOpenSci's standards? Please submit your software here under our "Issues" page. Interested in having your Python package reviewed according to pyOpenSci's standards? Please submit your software here under our "Issues" page. - pyOpenSci/software-submission

Writing, sharing, documenting, maintaining your code…it’s a lot.

pyOpenSci is here to help. 💛

📦 Submit your package: github.com/pyopensci/so...

Get involved with pyOpenSci pyOpenSci’s Website

We don’t believe in gatekeeping.

pyOpenSci is built on mentorship, support, and shared learning.

If you’re a #Python user, a data scientist, or a curious researcher, we want your voice in the room.

✨ Get involved: www.pyopensci.org/volunteer.html

pyOpenSci Python Package Guide We support the Python tools that scientists need to create open science workflows. GitHub release (latest by date) DOI new Tutorial Series: Create a Python Package: The first round of our community...

Finish this sentence:
💭 I wish I’d known ___ before publishing my first Python package.

Your experience could help someone new to packaging—what would you add?

👉 www.pyopensci.org/python-packa...

OpenSource@Stanford & pyOpenSci: Improving Research Software through Open and Accessible Peer Review YouTube video by Stanford Data Science

New collab! OpenSource@Stanford + pyOpenSci hosted their first event on software peer review.

Zach Chandler, @mafrancesca.bsky.social & @leahawasser.bsky.social shared how review helps researchers grow skills, gain recognition & build sustainable Python software.

🎥 www.youtube.com/watch?v=LIE5...

pyOpenSci Python Package Guide We support the Python tools that scientists need to create open science workflows. GitHub release (latest by date) DOI new Tutorial Series: Create a Python Package: The first round of our community...

Thinking about packaging your Python code, but not sure where to start? 👩‍💻🐍

Our beginner-friendly guide walks you through it step by step:
📂 Organize your code
📝 Write docs
⚙️ Set up pyproject.toml
🤝 Submit for peer review

👉 www.pyopensci.org/python-packa...

Graphic featuring a thank-you message for Isabel Zimmerman from pyOpenSci. The left side includes text acknowledging her contributions as Editor in Chief, editor, and triage team member, noting her leadership, kindness, and clarity. It states she is stepping into an Emeritus role while remaining a valued community member. The right side shows a smiling woman with shoulder-length brown hair in a sleeveless black top, framed in a purple circular border. The pyOpenSci logo appears at the bottom left.

This week, we’re honoring Isabel Zimmerman as she steps down from her editor role at pyOpenSci.

From EiC to triage, her clarity and care shaped dozens of reviews. She now moves into an Emeritus role, still a vital part of our community 💜

#OpenScience #pyOpenSci #PeerReview #Python

Traditional academic peer review can feel harsh.

At pyOpenSci, our reviews are:
🤝 Collaborative
🛠️ Practical
💛 Centered on helping maintainers succeed

Because your code matters and so does the experience of sharing it.

👉 Learn how to submit: www.pyopensci.org/software-pee...

Graphic thanking Tracy Teal for completing a 3-year term as Executive Council Chair of pyOpenSci. Text expresses gratitude for her expertise, time, and effort, welcomes Karen Cranston as the new Chair, and April Johnson as the newest Council member. Includes pyOpenSci logo and headshots of Tracy Teal (top right), Karen Cranston (middle right), and April Johnson (bottom right).

After 3 years as our founding Executive Council Chair, Tracy Teal is passing the torch to Karen Cranston. We’re also welcoming April Johnson to the Council!

Here’s why this leadership transition is a milestone for our growth: www.pyopensci.org/blog/pyopens...

#OpenScience #Python

Portrait of Mandy Moore wearing a wide-brimmed black hat and sleeveless top, seated indoors with colorful lights in the background. To the right, the pyOpenSci logo appears on a purple patterned background.

📢 Please welcome Mandy Moore (@therubyrep.bsky.social) as pyOpenSci’s new Communications & Community Lead!

Read her intro post: www.pyopensci.org/blog/mandy-m...

#OpenScience #Python #CommunityDriven

Graphic announcing Eliot Robson as pyOpenSci’s new rotating Editor in Chief for the peer review program. Text reads: ‘THANK YOU Eliot Robson. Eliot Robson is our new rotating Editor in Chief for pyOpenSci’s peer review program. A past package submitter and reviewer, he brings experience and a collaborative spirit to leading our editorial team.’ On the right is a circular photo of Eliot wearing a pastel purple and blue hoodie. The pyOpenSci logo appears at the bottom left.

📢 Eliot Robson is our new rotating Editor in Chief! 🎉

A past package submitter & reviewer, Eliot brings experience and a collaborative spirit to guiding pyOpenSci’s peer review process. 💛

👏 Join us in congratulating him!
#OpenScience #Python #PeerReview #pyOpenSci