deploy: a8e7b20

pyOpenSci · Jul 14, 2024 · 5f18b6f · 5f18b6f
1 parent 2cd2edc
commit 5f18b6f
Show file tree

Hide file tree

Showing 17 changed files with 12 additions and 14 deletions.
diff --git a/.doctrees/about/intro.doctree b/.doctrees/about/intro.doctree
diff --git a/.doctrees/appendices/package-approval-template.doctree b/.doctrees/appendices/package-approval-template.doctree
diff --git a/.doctrees/environment.pickle b/.doctrees/environment.pickle
diff --git a/.doctrees/how-to/author-guide.doctree b/.doctrees/how-to/author-guide.doctree
diff --git a/.doctrees/how-to/editors-guide.doctree b/.doctrees/how-to/editors-guide.doctree
diff --git a/.doctrees/index.doctree b/.doctrees/index.doctree
diff --git a/_sources/about/intro.md.txt b/_sources/about/intro.md.txt
@@ -121,7 +121,7 @@ You can identify pyOpenSci packages that have been peer-reviewed by the green
 :::{figure-md} pyos-badge
 :class: myclass
 
-<img src="https://tinyurl.com/y22nb8up" alt="The pyOpenSci badge" class="bg-primary mb-1" width="200px">
+<img src="https://pyopensci.org/badges/peer-reviewed.svg" alt="The pyOpenSci Peer Reviewed badge" class="bg-primary mb-1" width="200px">
 
 pyOpenSci Peer Review Badge
 :::

diff --git a/_sources/appendices/package-approval-template.md.txt b/_sources/appendices/package-approval-template.md.txt
@@ -9,7 +9,7 @@ There are a few things left to do to wrap up this submission:
 
 - [ ] Activate [Zenodo](https://zenodo.org/) watching the repo if you haven't already done so.
 - [ ] Tag and create a release to create a Zenodo version and DOI.
-- [ ] Add the badge for pyOpenSci peer-review to the README.md of <package-name-here>. The badge should be `[![pyOpenSci](https://tinyurl.com/y22nb8up)](https://github.com/pyOpenSci/software-review/issues/issue-number)`.
+- [ ] Add the badge for pyOpenSci peer-review to the README.md of <package-name-here>. The badge should be `[![pyOpenSci Peer-Reviewed](https://pyopensci.org/badges/peer-reviewed.svg)](https://github.com/pyOpenSci/software-review/issues/issue-number)`.
 - [ ] Please fill out the [post-review survey](https://forms.gle/BLGVCfUdiJHS5YJY7). All maintainers and reviewers should fill this out.
 
 <IF JOSS SUBMISSION>

diff --git a/_sources/how-to/author-guide.md.txt b/_sources/how-to/author-guide.md.txt
@@ -250,7 +250,7 @@ Once your package is approved, a few things will happen:
 1. We will ask you to ensure that your package is being tracked / archived using
    Zenodo. You will then want to created a tagged release representing the version of the
    package accepted by pyOpenSci.
-1. We will ask you to add the pyOpenSci badge [![pyOpenSci](https://tinyurl.com/y22nb8up)](https://github.com/pyOpenSci/software-review/issues/issue-number) to the
+1. We will ask you to add the pyOpenSci badge [![pyOpenSci Peer Reviewed](https://pyopensci.org/badges/peer-reviewed.svg)](https://github.com/pyOpenSci/software-review/issues/issue-number) to the
    top of your **README.md** file.
 1. We will promote your package on our social media channels!
 1. We will invite you to write a blog on our website spotlighting your package. The blogs that our maintainers write are some of the most popular content on the website!

diff --git a/_sources/how-to/editors-guide.md.txt b/_sources/how-to/editors-guide.md.txt
@@ -407,7 +407,7 @@ interested in this option, consider doing the following:
     -   Go to the repository settings in the "pyOpenSci" GitHub organization and give the author "Admin" access to the repository.
 -   Ask the author to:
     -  Change any needed links, such as those for CI badges.
-    -  Add pyOpenSci badge: `[![pyOpenSci](https://tinyurl.com/y22nb8up)](link-to-issue)`.
+    -  Add pyOpenSci badge: `[![pyOpenSci Peer Reviewed](https://pyopensci.org/badges/peer-reviewed.svg)](link-to-issue)`.
     -   Re-activate CI services:
         -  For Travis, activating the project in the pyOpenSci account should be sufficient.
         -  For AppVeyor, tell the author to update the GitHub link in their badge, but do not transfer the project: AppVeyor projects should remain under the authors' account. The badge is `[![AppVeyor Build Status](https://ci.appveyor.com/api/projects/status/github/pyOpenSci/pkgname?branch=main&svg=true)](https://ci.appveyor.com/project/individualaccount/pkgname)`.

diff --git a/_sources/index.md.txt b/_sources/index.md.txt
@@ -115,7 +115,7 @@ programmers and researchers.
 :::{figure-md} pyos-badge-home
 :class: myclass
 
-<img src="https://tinyurl.com/y22nb8up" alt="The pyOpenSci badge- On the left is the badge in grey and it says pyOpenSci. On the right it is bright green and says Peer Reviewed." class="bg-primary mb-1" width="200px">
+<img src="https://pyopensci.org/badges/peer-reviewed.svg" alt="The pyOpenSci badge- On the left is the badge in grey and it says pyOpenSci. On the right it is bright green and says Peer Reviewed." class="bg-primary mb-1" width="200px">
 
 **pyOpenSci Peer Review Badge will appear on the README.md file of packages that have been
 reviewed and vetted by us.**

diff --git a/about/intro.html b/about/intro.html
@@ -603,8 +603,7 @@ <h3>How do I know that a Python package has been reviewed by pyOpenSci?<a class=
 <p>You can identify pyOpenSci packages that have been peer-reviewed by the green
 “peer-reviewed” badge at the top of their <code class="docutils literal notranslate"><span class="pre">README.md</span></code> file.</p>
 <figure class="myclass align-default" id="pyos-badge">
-<a class="bg-primary mb-1 reference internal image-reference" href="https://tinyurl.com/y22nb8up"><img alt="The pyOpenSci badge" class="bg-primary mb-1" src="https://tinyurl.com/y22nb8up" style="width: 200px;" />
-</a>
+<a class="bg-primary mb-1 reference internal image-reference" href="https://pyopensci.org/badges/peer-reviewed.svg"><img alt="The pyOpenSci Peer Reviewed badge" class="bg-primary mb-1" src="https://pyopensci.org/badges/peer-reviewed.svg" width="200px" /></a>
 <figcaption>
 <p><span class="caption-text">pyOpenSci Peer Review Badge</span><a class="headerlink" href="#pyos-badge" title="Link to this image">#</a></p>
 </figcaption>

diff --git a/appendices/package-approval-template.html b/appendices/package-approval-template.html
@@ -485,7 +485,7 @@
 
 <span class="k">- [ ]</span> Activate [<span class="nt">Zenodo</span>](<span class="na">https://zenodo.org/</span>) watching the repo if you haven&#39;t already done so.
 <span class="k">- [ ]</span> Tag and create a release to create a Zenodo version and DOI.
-<span class="k">- [ ]</span> Add the badge for pyOpenSci peer-review to the README.md of &lt;package-name-here&gt;. The badge should be <span class="sb">`[![pyOpenSci](https://tinyurl.com/y22nb8up)](https://github.com/pyOpenSci/software-review/issues/issue-number)`</span>.
+<span class="k">- [ ]</span> Add the badge for pyOpenSci peer-review to the README.md of &lt;package-name-here&gt;. The badge should be <span class="sb">`[![pyOpenSci Peer-Reviewed](https://pyopensci.org/badges/peer-reviewed.svg)](https://github.com/pyOpenSci/software-review/issues/issue-number)`</span>.
 <span class="k">- [ ]</span> Please fill out the [<span class="nt">post-review survey</span>](<span class="na">https://forms.gle/BLGVCfUdiJHS5YJY7</span>). All maintainers and reviewers should fill this out.
 
 &lt;IF JOSS SUBMISSION&gt;

diff --git a/how-to/author-guide.html b/how-to/author-guide.html
@@ -757,7 +757,7 @@ <h2>My Package is Approved, Now What?<a class="headerlink" href="#my-package-is-
 <li><p>We will ask you to ensure that your package is being tracked / archived using
 Zenodo. You will then want to created a tagged release representing the version of the
 package accepted by pyOpenSci.</p></li>
-<li><p>We will ask you to add the pyOpenSci badge <a class="reference external" href="https://github.com/pyOpenSci/software-review/issues/issue-number"><img alt="pyOpenSci" src="https://tinyurl.com/y22nb8up" /></a> to the
+<li><p>We will ask you to add the pyOpenSci badge <a class="reference external" href="https://github.com/pyOpenSci/software-review/issues/issue-number"><img alt="pyOpenSci Peer Reviewed" src="https://pyopensci.org/badges/peer-reviewed.svg" /></a> to the
 top of your <strong>README.md</strong> file.</p></li>
 <li><p>We will promote your package on our social media channels!</p></li>
 <li><p>We will invite you to write a blog on our website spotlighting your package. The blogs that our maintainers write are some of the most popular content on the website!</p></li>

diff --git a/how-to/editors-guide.html b/how-to/editors-guide.html
@@ -893,7 +893,7 @@ <h3>✔️ 6. How to accept a package into the pyOpenSci ecosystem<a class="head
 
 <span class="k">- [ ]</span> Activate [<span class="nt">Zenodo</span>](<span class="na">https://zenodo.org/</span>) watching the repo if you haven&#39;t already done so.
 <span class="k">- [ ]</span> Tag and create a release to create a Zenodo version and DOI.
-<span class="k">- [ ]</span> Add the badge for pyOpenSci peer-review to the README.md of &lt;package-name-here&gt;. The badge should be <span class="sb">`[![pyOpenSci](https://tinyurl.com/y22nb8up)](https://github.com/pyOpenSci/software-review/issues/issue-number)`</span>.
+<span class="k">- [ ]</span> Add the badge for pyOpenSci peer-review to the README.md of &lt;package-name-here&gt;. The badge should be <span class="sb">`[![pyOpenSci Peer-Reviewed](https://pyopensci.org/badges/peer-reviewed.svg)](https://github.com/pyOpenSci/software-review/issues/issue-number)`</span>.
 <span class="k">- [ ]</span> Please fill out the [<span class="nt">post-review survey</span>](<span class="na">https://forms.gle/BLGVCfUdiJHS5YJY7</span>). All maintainers and reviewers should fill this out.
 
 &lt;IF JOSS SUBMISSION&gt;
@@ -1015,7 +1015,7 @@ <h2>Last Steps Before Closing the Review Issue<a class="headerlink" href="#last-
     -   Go to the repository settings in the "pyOpenSci" GitHub organization and give the author "Admin" access to the repository.
 -   Ask the author to:
     -  Change any needed links, such as those for CI badges.
-    -  Add pyOpenSci badge: `[![pyOpenSci](https://tinyurl.com/y22nb8up)](link-to-issue)`.
+    -  Add pyOpenSci badge: `[![pyOpenSci Peer Reviewed](https://pyopensci.org/badges/peer-reviewed.svg)](link-to-issue)`.
     -   Re-activate CI services:
         -  For Travis, activating the project in the pyOpenSci account should be sufficient.
         -  For AppVeyor, tell the author to update the GitHub link in their badge, but do not transfer the project: AppVeyor projects should remain under the authors' account. The badge is `[![AppVeyor Build Status](https://ci.appveyor.com/api/projects/status/github/pyOpenSci/pkgname?branch=main&svg=true)](https://ci.appveyor.com/project/individualaccount/pkgname)`.

diff --git a/index.html b/index.html
@@ -541,8 +541,7 @@ <h2>Why pyOpenSci?<a class="headerlink" href="#why-pyopensci" title="Link to thi
 among scientific Python users so that we can help each other become better
 programmers and researchers.</p>
 <figure class="myclass align-default" id="pyos-badge-home">
-<a class="bg-primary mb-1 reference internal image-reference" href="https://tinyurl.com/y22nb8up"><img alt="The pyOpenSci badge- On the left is the badge in grey and it says pyOpenSci. On the right it is bright green and says Peer Reviewed." class="bg-primary mb-1" src="https://tinyurl.com/y22nb8up" style="width: 200px;" />
-</a>
+<a class="bg-primary mb-1 reference internal image-reference" href="https://pyopensci.org/badges/peer-reviewed.svg"><img alt="The pyOpenSci badge- On the left is the badge in grey and it says pyOpenSci. On the right it is bright green and says Peer Reviewed." class="bg-primary mb-1" src="https://pyopensci.org/badges/peer-reviewed.svg" width="200px" /></a>
 <figcaption>
 <p><span class="caption-text"><strong>pyOpenSci Peer Review Badge will appear on the README.md file of packages that have been
 reviewed and vetted by us.</strong></span><a class="headerlink" href="#pyos-badge-home" title="Link to this image">#</a></p>

diff --git a/searchindex.js b/searchindex.js