|
| 1 | +--- |
| 2 | +layout: single |
| 3 | +title: "pyOpenSci: Improving research software and code through open and accessible peer review" |
| 4 | +excerpt: "Discover how peer review improves research software quality and reproducibility. Hosted for the community within Stanford’s Open Source Program Office, this deep dive introduces pyOpenSci’s review process and ways for researchers to get involved and grow their open source and leadership skills through participating in software peer review." |
| 5 | +author: "pyopensci" |
| 6 | +event: |
| 7 | + start_date: "2025-08-07" |
| 8 | + location: Online |
| 9 | +permalink: /events/pyopensci-stanford-ospo-peer-review.html |
| 10 | +header: |
| 11 | + overlay_image: images/headers/pyopensci-sustainability.png |
| 12 | +categories: |
| 13 | + - events |
| 14 | +classes: wide |
| 15 | +type: "event" |
| 16 | +last_modified: 2025-07-03 |
| 17 | +comments: true |
| 18 | +--- |
| 19 | + |
| 20 | +## pyOpenSci: Improving research software and code through open and accessible peer review |
| 21 | + |
| 22 | +* **When:** Thursday, 7 August @ 11:00 AM Mountain Time |
| 23 | +* **Where:** Zoom: this event is for the Stanford Open Source Community |
| 24 | + |
| 25 | +This event, hosted in partnership with [Stanford’s Open Source Program |
| 26 | +Office](https://opensource.stanford.edu/), explores how [software peer review](https://www.pyopensci.org/about-peer-review/index.html) can help you build more reliable research tools, improve your coding and software development skills, and gain academic recognition while also connecting with a global community of practice that is dedicated to supporting the broader research and scientific Python community build better research software. |
| 27 | + |
| 28 | +You’ll learn how pyOpenSci’s community-driven review |
| 29 | +process supports open, sustainable Python software—and how to get |
| 30 | +involved as a contributor or reviewer. |
| 31 | + |
| 32 | +Peer review improves software quality, documentation, and long-term |
| 33 | +sustainability—and gives contributors academic recognition through our |
| 34 | +partnership with the [Journal of Open Source Software (JOSS)]( |
| 35 | +https://www.pyopensci.org/software-peer-review/partners/joss.html). |
| 36 | + |
| 37 | +The process is grounded in our [community-developed packaging |
| 38 | +guidelines](https://www.pyopensci.org/python-package-guide/index.html) |
| 39 | +tailored to scientific software. |
| 40 | + |
| 41 | +Whether you're building tools or reviewing them, you're helping shape a |
| 42 | +more open, collaborative, and reproducible future for science. Join us |
| 43 | +to improve research software—and get recognized for doing it. |
| 44 | + |
| 45 | +### Why attend |
| 46 | + |
| 47 | +- <i class="fa-solid fa-magnifying-glass-chart"></i> Learn what peer review |
| 48 | + looks like for research software |
| 49 | +- <i class="fa-solid fa-code"></i> Improve your own coding practices by reviewing |
| 50 | + real-world tools |
| 51 | +- <i class="fa-solid fa-diagram-project"></i> See how others structure code, write |
| 52 | + tests, and document their work |
| 53 | +- <i class="fa-solid fa-award"></i> Gain visibility and academic credit for |
| 54 | + contributions |
| 55 | +- <i class="fa-solid fa-right-to-bracket"></i> Take a low-barrier first step into the |
| 56 | + open-source research ecosystem |
| 57 | + |
| 58 | + |
| 59 | +### Building bridges: The power of our Stanford partnership |
| 60 | + |
| 61 | +Through our partnership with Stanford, we're building a bridge between |
| 62 | +the University Open Source Program Offices and the global open-source community that powers scientific |
| 63 | +Python. Researchers and students gain access to high-quality, community-based |
| 64 | +training in research software practices—without Stanford needing to create |
| 65 | +that infrastructure from scratch. |
| 66 | + |
| 67 | +This collaboration supports Stanford’s leadership in open, reproducible |
| 68 | +science while giving its researchers meaningful opportunities to engage with |
| 69 | +the pyOpenSci community and contribute to a broader, inclusive ecosystem of |
| 70 | +scientific software development. |
| 71 | + |
| 72 | +<div class="notice" markdown="1"> |
| 73 | + |
| 74 | +<i class="fa-solid fa-users-line"></i> Connect with us! |
| 75 | +{: .header } |
| 76 | + |
| 77 | +There are many ways to get involved if you're interested! |
| 78 | + |
| 79 | +* If you read through our lessons and want to suggest changes, open an issue in our [lessons repository here](https://github.com/pyOpenSci/lessons) |
| 80 | +* [Volunteer to be a reviewer for pyOpenSci's software review process](https://forms.gle/GHfxvmS47nQFDcBM6) |
| 81 | +* [Submit a Python package to pyOpenSci for peer review](https://www.pyopensci.org/software-peer-review/how-to/author-guide.html#submit-your-package-for-peer-review) |
| 82 | +* [Donate to pyOpenSci](https://give.communityin.org/pyopensci_2024) to support scholarships for future training events and the development of new learning content. |
| 83 | +* Check out our [volunteer page](/volunteer.html) for other ways to get involved. |
| 84 | + |
| 85 | +You can also: |
| 86 | + |
| 87 | +* Keep an eye on our [events page](/events.html) for upcoming training events. |
| 88 | + |
| 89 | +Follow us on social platforms: |
| 90 | + |
| 91 | +* [<i class="fa-brands fa-discourse" style="color:#81c0aa;"></i> Discourse](https://pyopensci.discourse.group/) |
| 92 | +* [<i class="fa-brands fa-mastodon" style="color:#81c0aa;"></i> Mastodon](https://fosstodon.org/@pyopensci) |
| 93 | +* [<i class="fa-solid fa-cloud" style="color:#81c0aa;"></i> Bluesky](https://bsky.app/profile/pyopensci.bsky.social) |
| 94 | +* [<i class="fa-brands fa-linkedin" style="color:#81c0aa;"></i> LinkedIn](https://www.linkedin.com/company/pyopensci) |
| 95 | +* [<i class="fa-brands fa-github" style="color:#81c0aa;"></i> GitHub](https://github.com/pyOpenSci) |
| 96 | + |
| 97 | +If you are on LinkedIn, check out and [subscribe to our newsletter, too](https://www.linkedin.com/newsletters/7179551305344933888/?displayConfirmation=true). |
| 98 | + |
| 99 | +</div> |
0 commit comments