enh(events): add stanford ospo and scipy events to website

_data/navigation.yml

@@ -38,7 +38,7 @@ main:
       - title: Blog
         url: "/blog/index.html"
       - title: Events
-        url: "/events/index.html"
+        url: "/events.html"
       - title: Ask a question
         url: "https://pyopensci.discourse.group/"
         icon: "fa-brands fa-discourse"

_layouts/posts_events.html

@@ -11,6 +11,7 @@ <h2>Upcoming events</h2>
 {% assign all_events = site.posts
   | where_exp: "item", "item.hidden != true"
   | where_exp: "item", "item.categories contains 'events'"
+  | sort: "event.start_date"
 %}
 
 {% capture nowunix %}{{'now' | date: '%s'}}{% endcapture %}

_pages/events.md

@@ -1,6 +1,6 @@
 ---
 layout: posts_events
-permalink: /events/
+permalink: /events.html
 classes: wide
 title: "pyOpenSci Events"
 excerpt: "pyOpenSci holds events that support scientists developing open science skills."

_posts/2024-08-30-pyopensci-monumental-growth-2024.md

@@ -34,7 +34,7 @@ facing in creating open, reproducible workflows using Python. My experience
 inspired me to establish a vibrant, inclusive pyOpenSci community of practice
 fueled by making open science best practices more accessible to scientists.
 
-pyOpenSci makes open science more accessible by [developing educational resources](/learn.html), [running training events](/events/index.html), running an [open software peer review process](/about-peer-review/index.html) and [partnering with other communities](/partners.html). From humble beginnings characterized by small community meetings, pyOpenSci has blossomed into a thriving community marked by:
+pyOpenSci makes open science more accessible by [developing educational resources](/learn.html), [running training events](/events.html), running an [open software peer review process](/about-peer-review/index.html) and [partnering with other communities](/partners.html). From humble beginnings characterized by small community meetings, pyOpenSci has blossomed into a thriving community marked by:
 
 * a robust editorial team,
 * hundreds of contributors, and

_posts/2025-02-07-pyopensci-2024-a-year-in-review.md

@@ -17,7 +17,7 @@ last_modified: 2025-02-07
 
 ## Introduction
 
-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 [training events](https://www.pyopensci.org/events/index.html), [collaborative tutorials](https://www.pyopensci.org/learn.html#start-learning-beginner-friendly-python-packaging-tutorials), and [software peer review](https://www.pyopensci.org/about-peer-review/index.html).
+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 [training events](https://www.pyopensci.org/events.html), [collaborative tutorials](https://www.pyopensci.org/learn.html#start-learning-beginner-friendly-python-packaging-tutorials), and [software peer review](https://www.pyopensci.org/about-peer-review/index.html).
 
 <figure>
 <picture>

_posts/2025-03-18-contribute-to-open-source-github-lessons.md

@@ -112,7 +112,7 @@ There are lots of ways to get involved if you are interested!
 
 You can also:
 
-* Keep an eye on our [events page]({{ site.baseurl }}/events/index.html) for upcoming training events.
+* Keep an eye on our [events page]({{ site.baseurl }}/events.html) for upcoming training events.
 
 Follow us on social platforms:
 

_posts/2025-06-30-pyos-scipy-2025.md

@@ -172,7 +172,7 @@ There are lots of ways to get involved if you are interested!
 
 You can also:
 
-* Keep an eye on our [events page](https://www.pyopensci.org/events/index.html) for upcoming training events.
+* Keep an eye on our [events page](https://www.pyopensci.org/events.html) for upcoming training events.
 
 Follow us on socials:
 

_posts/events/2025-06-24-scipy25-bof.md

@@ -0,0 +1,71 @@
+---
+layout: single
+title: "SciPy 2025: Open Code, Open Science: What’s Getting in Your Way?"
+excerpt: "Join us for an interactive discussion on pain points that you are experiencing with developing and maintaining reusable software and code."
+author: "pyopensci"
+event:
+  start_date: "2025-07-10"
+  location: Online
+permalink: /events/pyopensci-scipy25-bof-packaging-challenges.html
+header:
+  overlay_image: images/headers/pyopensci-sustainability.png
+categories:
+  - events
+classes: wide
+type: "event"
+last_modified: 2025-07-03
+comments: true
+---
+
+## <i class="fa-solid fa-box-open"></i> Learn how to create your first Python package!
+
+* **When:** Thursday, 10 July 2025 @ 1:15–2:10 PM Pacific Time
+* **Where:** Room 315 @ SciPy Meeting 2025 in Tacoma, Washington
+* **Session leaders:**
+    * Leah Wasser
+    * Inessa Pawson
+    * Carol Willing
+    * Jeremiah Paige
+    * Tetsuo Koyama
+    * Avik Basu
+
+
+
+[<i class="fa-regular fa-circle-right"></i> View our session abstract](https://cfp.scipy.org/scipy2025/talk/3ZHYMH/){: .btn .btn--success .text-center }
+
+Collaborating on code and software is essential to open science—but it’s not always easy. Join this BoF for an interactive discussion on the real-world challenges of open source collaboration. We’ll explore common hurdles like Python packaging, contributing to existing codebases, and emerging issues around LLM-assisted development and AI-generated software contributions.
+
+We’ll kick off with a brief overview of pyOpenSci—an inclusive community of Pythonistas, from novices to experts—working to make it easier to create, find, share, and contribute to reusable code. We’ll then facilitate small-group discussions and use an interactive Mentimeter survey to help you share your experiences and ideas.
+
+Your feedback will directly shape pyOpenSci’s priorities for the coming year, as we build new programs and resources to support your work in the Python scientific ecosystem. Whether you’re just starting out or a seasoned developer, you’ll leave with clear ways to get involved and make an impact on the broader Python ecosystem in service of advancing scientific discovery.
+
+
+
+<div class="notice" markdown="1">
+
+<i class="fa-solid fa-users-line"></i> Connect with us!
+{: .header }
+
+There are many ways to get involved if you're interested!
+
+* If you read through our lessons and want to suggest changes, open an issue in our [lessons repository here](https://github.com/pyOpenSci/lessons)
+* [Volunteer to be a reviewer for pyOpenSci's software review process](https://forms.gle/GHfxvmS47nQFDcBM6)
+* [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)
+* [Donate to pyOpenSci](https://give.communityin.org/pyopensci_2024) to support scholarships for future training events and the development of new learning content.
+* Check out our [volunteer page](/volunteer.html) for other ways to get involved.
+
+You can also:
+
+* Keep an eye on our [events page](/events.html) for upcoming training events.
+
+Follow us on social platforms:
+
+* [<i class="fa-brands fa-discourse" style="color:#81c0aa;"></i> Discourse](https://pyopensci.discourse.group/)
+* [<i class="fa-brands fa-mastodon" style="color:#81c0aa;"></i> Mastodon](https://fosstodon.org/@pyopensci)
+* [<i class="fa-solid fa-cloud" style="color:#81c0aa;"></i> Bluesky](https://bsky.app/profile/pyopensci.bsky.social)
+* [<i class="fa-brands fa-linkedin" style="color:#81c0aa;"></i> LinkedIn](https://www.linkedin.com/company/pyopensci)
+* [<i class="fa-brands fa-github" style="color:#81c0aa;"></i> GitHub](https://github.com/pyOpenSci)
+
+If you are on LinkedIn, check out and [subscribe to our newsletter, too](https://www.linkedin.com/newsletters/7179551305344933888/?displayConfirmation=true).
+
+</div>

_posts/events/2025-06-24-stanford-ospo-peer-review-deep-dive.md

@@ -0,0 +1,99 @@
+---
+layout: single
+title: "pyOpenSci: Improving research software and code through open and accessible peer review"
+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."
+author: "pyopensci"
+event:
+  start_date: "2025-08-07"
+  location: Online
+permalink: /events/pyopensci-stanford-ospo-peer-review.html
+header:
+  overlay_image: images/headers/pyopensci-sustainability.png
+categories:
+  - events
+classes: wide
+type: "event"
+last_modified: 2025-07-03
+comments: true
+---
+
+## pyOpenSci: Improving research software and code through open and accessible peer review
+
+* **When:** Thursday, 7 August @ 11:00 AM Mountain Time
+* **Where:** Zoom: this event is for the Stanford Open Source Community
+
+This event, hosted in partnership with [Stanford’s Open Source Program
+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.
+
+You’ll learn how pyOpenSci’s community-driven review
+process supports open, sustainable Python software—and how to get
+involved as a contributor or reviewer.
+
+Peer review improves software quality, documentation, and long-term
+sustainability—and gives contributors academic recognition through our
+partnership with the [Journal of Open Source Software (JOSS)](
+https://www.pyopensci.org/software-peer-review/partners/joss.html).
+
+The process is grounded in our [community-developed packaging
+guidelines](https://www.pyopensci.org/python-package-guide/index.html)
+tailored to scientific software.
+
+Whether you're building tools or reviewing them, you're helping shape a
+more open, collaborative, and reproducible future for science. Join us
+to improve research software—and get recognized for doing it.
+
+### Why attend
+
+- <i class="fa-solid fa-magnifying-glass-chart"></i> Learn what peer review
+  looks like for research software
+- <i class="fa-solid fa-code"></i> Improve your own coding practices by reviewing
+  real-world tools
+- <i class="fa-solid fa-diagram-project"></i> See how others structure code, write
+  tests, and document their work
+- <i class="fa-solid fa-award"></i> Gain visibility and academic credit for
+  contributions
+- <i class="fa-solid fa-right-to-bracket"></i> Take a low-barrier first step into the
+  open-source research ecosystem
+
+
+### Building bridges: The power of our Stanford partnership
+
+Through our partnership with Stanford, we're building a bridge between
+the University Open Source Program Offices and the global open-source community that powers scientific
+Python. Researchers and students gain access to high-quality, community-based
+training in research software practices—without Stanford needing to create
+that infrastructure from scratch.
+
+This collaboration supports Stanford’s leadership in open, reproducible
+science while giving its researchers meaningful opportunities to engage with
+the pyOpenSci community and contribute to a broader, inclusive ecosystem of
+scientific software development.
+
+<div class="notice" markdown="1">
+
+<i class="fa-solid fa-users-line"></i> Connect with us!
+{: .header }
+
+There are many ways to get involved if you're interested!
+
+* If you read through our lessons and want to suggest changes, open an issue in our [lessons repository here](https://github.com/pyOpenSci/lessons)
+* [Volunteer to be a reviewer for pyOpenSci's software review process](https://forms.gle/GHfxvmS47nQFDcBM6)
+* [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)
+* [Donate to pyOpenSci](https://give.communityin.org/pyopensci_2024) to support scholarships for future training events and the development of new learning content.
+* Check out our [volunteer page](/volunteer.html) for other ways to get involved.
+
+You can also:
+
+* Keep an eye on our [events page](/events.html) for upcoming training events.
+
+Follow us on social platforms:
+
+* [<i class="fa-brands fa-discourse" style="color:#81c0aa;"></i> Discourse](https://pyopensci.discourse.group/)
+* [<i class="fa-brands fa-mastodon" style="color:#81c0aa;"></i> Mastodon](https://fosstodon.org/@pyopensci)
+* [<i class="fa-solid fa-cloud" style="color:#81c0aa;"></i> Bluesky](https://bsky.app/profile/pyopensci.bsky.social)
+* [<i class="fa-brands fa-linkedin" style="color:#81c0aa;"></i> LinkedIn](https://www.linkedin.com/company/pyopensci)
+* [<i class="fa-brands fa-github" style="color:#81c0aa;"></i> GitHub](https://github.com/pyOpenSci)
+
+If you are on LinkedIn, check out and [subscribe to our newsletter, too](https://www.linkedin.com/newsletters/7179551305344933888/?displayConfirmation=true).
+
+</div>