Merge branch 'main' into contribs

Author: willingc

.github/workflows/build-site.yml

@@ -37,7 +37,7 @@ jobs:
         uses: lycheeverse/lychee-action@8646ba30535128ac92d33dfc9133794bfdd9b411 #v2.8.0
         with:
           fail: true
-          args: --no-progress --root-dir _site --exclude 'zenodo\.org' --accept 403 _site
+          args: --no-progress --root-dir _site --exclude 'zenodo\.org' --accept '200..=403' _site
         env:
           GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
 

.github/workflows/linkcheck.yml

@@ -36,7 +36,7 @@ jobs:
             --no-progress
             --root-dir ${{ github.workspace }}/_site
             --exclude 'zenodo\.org'
-            --accept 403
+            --accept '200..=403'
             _site
         env:
           GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}

.github/workflows/main.yml

@@ -13,7 +13,6 @@ jobs:
     steps:
       - uses: actions/checkout@v6
       - name: Check workflow files
-        run: |
-          bash <(curl https://raw.githubusercontent.com/rhysd/actionlint/main/scripts/download-actionlint.bash)
-          ./actionlint -color -ignore SC2129
-        shell: bash
+        uses: rhysd/actionlint@393031adb9afb225ee52ae2ccd7a5af5525e03e8 # v1.7.11
+        with:
+          args: -color -ignore SC2129

.lycheeignore

@@ -8,3 +8,12 @@ https://dl.acm.org/*
 https://commons.datacite.org/*
 https://pandas.pydata.org/*
 https://www.earthdatascience.org/*
+https://www.bloomberg.com/*
+https://doi.org/*
+https://bsky.app/*
+https://chanzuckerberg.com/*
+https://communityinitiatives.org/*
+https://discord.gg/*
+https://fosstodon.org/*
+https://give.communityin.org/*
+https://sloan.org/*

_posts/2023-06-13-pycon2023-peer-review-david-nicholson-crowsetta.md

@@ -40,7 +40,7 @@ Just a few months prior, David had submitted a package he's been developing call
 In his talk (which was NOT about ChatGPT in case you were wondering :) ), David talked about who was involved and what the process and his experience was like. Check out the video below to learn more!
 
 The talk itself is about 5 minutes long but you can always keep it running to see the other lightning talks posted by the pyCon organizers. All of the pyCon 2023 US talks are online if you want to check out some of the others! [You can also check out our
-pyOpenSci presentation about Python Packaging and experiences with the sprints here if you'd like.](pycon-2023-packaging-presentation-sprints-leah-wasser.html)
+pyOpenSci presentation about Python Packaging and experiences with the sprints here if you'd like.](/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html)
 
 ## About the pyOpenSci peer review process
 

_posts/2023-10-18-rse-2023-pyopensci-bof.md

@@ -163,7 +163,7 @@ A few things that popped out to me included:
 The broad take away from this graphic is that there are a LOT of tools
 available for scientists to use. And becoming familiar with all of these is a big ask for a scientist who just wanted their code to be reusable by others.
 
-We have some work to do at pyOpenSci to [demystify this ecosystem](demystifying-python-packaging.html)!
+We have some work to do at pyOpenSci to [demystify this ecosystem](/blog/demystifying-python-packaging.html)!
 
 ## Challenges in the ecosystem
 

_posts/2024-05-30-pyos-pyconus-2024-recap.md

@@ -56,7 +56,7 @@ many people. I had never led a [mentored sprint](https://www.mentored-sprints.de
 And I wasn't sure how my packaging talk, [Friends Don't Let Friends Package Alone](https://us.pycon.org/2024/schedule/presentation/34/) would be received; you see, packaging is a notoriously thorny
 topic.
 
-[Last year turned out pretty great - read more here.](pycon-2023-packaging-presentation-sprints-leah-wasser.html)
+[Last year turned out pretty great - read more here.](/blog/pycon-2023-packaging-presentation-sprints-leah-wasser.html)
 
 However, rather than feeling like an outsider, I met a lot of new people
 who became new Python friends and colleagues. I learned about a lot of cool

_posts/2024-07-31-pyconus-pyopensci-sprints.md

@@ -19,9 +19,9 @@ last_modified: 2024-08-29
 
 In previous posts, I talked about:
 
-* Our [incredible experience at PyCon US 2024](recap-pyos-pyconus-2024.html).
+* Our [incredible experience at PyCon US 2024](/blog/recap-pyos-pyconus-2024.html).
 * My [personal experiences with the Python packaging ecosystem and building consensus
-  within the scientific Python community](python-packaging-friends-dont-let-friends-package-alone.html).
+  within the scientific Python community](/blog/python-packaging-friends-dont-let-friends-package-alone.html).
 
 Here, I will share with you what we have learned at pyOpenSci through holding
 beginner-friendly sprints over the past two years.

_posts/2024-08-02-pyopensci-at-scipy-2024.md

@@ -113,7 +113,7 @@ ridiculously hilarious as it sounds.
   <figcaption><i class="fa-solid fa-heart-pulse"></i> It's well-known that lightning talk organizers enjoy heckling presenters. Sometimes they do so using props, such as the lobster claw seen here <i class="fa-solid fa-heart-pulse"></i>. Photo Credit: SciPyConf Fosstodon </figcaption>
 </figure>
 
-[Did someone mention sharks? More here on my experience last year giving a SciPy lighting talk.](scipy-2023-community.html)
+[Did someone mention sharks? More here on my experience last year giving a SciPy lighting talk.](/blog/scipy-2023-community.html)
 {: .notice }
 
 Another cool thing about SciPy is that the entire meeting is community-driven. The scientific Python community really
@@ -140,7 +140,7 @@ had to say about it:
 
 This tutorial was an
 expanded version of the [Create Your First Python Package tutorial that
-pyOpenSci ran in April 2024](pyos-education-announcement.html). In our first
+pyOpenSci ran in April 2024](/blog/pyos-education-announcement.html). In our first
 workshop, we had over 20 people create their first Python package. We had
 similar success in our SciPy tutorial.
 
@@ -402,7 +402,7 @@ This year was the first time I stayed for both days of the sprints.
 If you haven't been to an open-source sprint before, a sprint is an open
 session where contributors join a project and help address specific issues and
 tasks that the project needs help with. I wrote [more about how pyOpenSci runs
-beginner-friendly sprints here](pyopensci-pyconus-2024-sprints.html).
+beginner-friendly sprints here](/blog/pyopensci-pyconus-2024-sprints.html).
 
 Sprints are a lot of fun because,
 given enough time, you can make significant progress on a project and support

_posts/2024-09-17-pyopensci-sustainability-plan-2024.md

@@ -22,7 +22,7 @@ Funding is critical to the success of any nonprofit organization. In this blog p
 
 ## How funding has propelled pyOpenSci forward
 
-Funding from [Sloan Foundation](https://sloan.org/) catalyzed pyOpenSci's growth by enabling me to dedicate full-time effort to growing the organization's impact in September 2022. This full-time commitment, paired with support from a fiscal sponsor, [catalyzed pyOpenSci's recent growth and success](what-pyopensci-accomplished-with-two-years-of-funding.html).
+Funding from [Sloan Foundation](https://sloan.org/) catalyzed pyOpenSci's growth by enabling me to dedicate full-time effort to growing the organization's impact in September 2022. This full-time commitment, paired with support from a fiscal sponsor, [catalyzed pyOpenSci's recent growth and success](/blog/what-pyopensci-accomplished-with-two-years-of-funding.html).
 
 <figure>
     <a href="{{ site.baseurl }}/images/pyopensci-general/pyopensci-timeline2019-2024.png"><img src="{{ site.baseurl }}/images/pyopensci-general/pyopensci-timeline2019-2024.png" alt="An image titled pyOpenSci timeline. showing key milestones from 2018 to 2024. The timeline is marked with flower icons and a small rocket to represent significant events. Key points include: 2018: Community Meetings Begin, 2019: Software Peer Review Launch,2021-2022: Sloan Funding, Fall 2022: Packaging Guide Rewrite Begins, January 2023: Peer Review Relaunched, Fall 2023: CZI funds pyOpenSci, Spring 2024: pyOpenSci launches training and tutorials. The timeline progresses diagonally from the bottom left to the top right, with a rocket heading toward a bright light in the top right corner." ></a>