Skip to content

Commit cea4839

Browse files
committed
CONTENT: fix guide links throughout
1 parent 7bc9335 commit cea4839

6 files changed

+9
-5
lines changed

_pages/python-packages.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ classes: wide
2727
<p>You're in the right place! Learn about the steps to submit a package
2828
for open peer review in our guidebook. </p>
2929
</div>
30-
<p><a href="https://www.pyopensci.org/peer-review-guide/open-source-software-submissions/author-guide.html" class="btn btn--inverse"><i class="fas fa-angle-right"></i> View our Author Guide </a></p>
30+
<p><a href="https://www.pyopensci.org/peer-review-guide/software-peer-review-guide/author-guide.html" class="btn btn--inverse"><i class="fas fa-angle-right"></i> View our Author Guide </a></p>
3131
</div>
3232
</div>
3333
</div>

_posts/2019-11-18-pandera-dataframe-validation.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@ categories:
1414
- data-validation
1515
- dataframes
1616
- highlight
17+
comments: true
1718
---
1819

1920
Modern data engineering and analysis workflows will often involve using data

_posts/2020-04-29-movingpandas-movement-data-analysis.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ categories:
1212
- blog-post
1313
- pandas
1414
- spatial
15+
comments: true
1516
---
1617

1718
Movement data is everywhere: from tracking apps that record human or vehicle movement to ecologists monitoring wildlife behavior. Movement data analysis is challenging since movement data combines time series and spatial data analyses questions. Existing spatial analysis libraries, such as GeoPandas, are great at handling spatial data but they don't support moving objects.

_posts/2022-09-10-executive-director-pyopensci-leah-wasser-updates.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ There are a few ways to get involved with us now.
101101
1. [You can sign up to be a reviewer by filling out our reviewer form](https://forms.gle/B6zAukLCvJot5nws6). If you do this, we will reach out to you if a package is submitted that suits your background and interests!
102102
* We will also be growing our editorial board in the upcoming months. Once you have reviewed for us you are eligible to be considered as an editor. We will be posting more about this process in the upcoming months.
103103
1. Our open peer review process is running! If you have a package that you are working on, [you can submit it to our peer review process](https://github.com/pyOpenSci/software-review/issues).
104-
* You can learn more about our review process here in our [community guide (which will be updated in the upcoming months so that it is more clear)](https://www.pyopensci.org/peer-review-guide/open-source-software-peer-review/aims-and-scope.html).
104+
* You can learn more about our review process here in our [community guide (which will be updated in the upcoming months so that it is more clear)](https://www.pyopensci.org/peer-review-guide/about-peer-review/aims-and-scope.html).
105105
* If you have a package that you wish to submit but need some guidance, you can also submit a presubmission inquiry or a request for help here.
106106
2. You can [follow us on twitter](https://www.twitter.com/pyopensci) to keep tabs on our progress.
107107

_posts/2022-09-27-call-for-python-software-review-editors.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ categories:
1212
- blog-post
1313
- highlight
1414
- peer-review
15+
comments: true
1516
---
1617

1718
## An update on pyOpenSci's review process
@@ -28,7 +29,7 @@ With that below you will find a few updates.
2829

2930
[David Nicholson](https://github.com/NickleDave), who has been working with pyOpenSci for the past few years as
3031
an editor will take on the Editor in Chief role! [You can learn more about that
31-
role here](https://www.pyopensci.org/peer-review-guide/open-source-software-submissions/editor-in-chief-guide.html) in our peer review guide. This position will rotate once we have our editorial board setup.
32+
role here](https://www.pyopensci.org/peer-review-guide/software-peer-review-guide/editor-in-chief-guide.html) in our peer review guide. This position will rotate once we have our editorial board setup.
3233

3334
As Editor in Chief, David will:
3435

@@ -57,7 +58,7 @@ longer given mutual consent. You will be responsible for handling 3-4 package
5758
reviews during that year. We may also bring on guest editors in other
5859
instances, e.g., because of their familiarity with a specific domain.
5960

60-
You can read more about the [roles and responsibilities of and editor here](https://www.pyopensci.org/peer-review-guide/open-source-software-submissions/editors-guide.html).
61+
You can read more about the [roles and responsibilities of and editor here](https://www.pyopensci.org/peer-review-guide/software-peer-review-guide/editors-guide.html).
6162

6263
We currently have a package in the queue that is spatial / remote sensing related
6364
that we'd love to have an editor onboard to review. But we are in need of editors

_posts/2022-10-24-why-should-python-open-source-matter-science.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@ categories:
1313
- python-packaging
1414
- peer-review
1515
toc: false
16+
comments: true
1617
---
1718

1819
## Why Python open source package health should matter to you as a scientist
@@ -192,7 +193,7 @@ So how do we track open source tool health (for science)?
192193

193194
### Peer review is actually the second step in our process.
194195

195-
We won't begin to review a package [without bare minimum checks](https://www.pyopensci.org/contributing-guide/open-source-software-submissions/author-guide.html#pyopensci-review-guide-for-python-open-source-package-authors).
196+
We won't begin to review a package [without bare minimum checks](https://www.pyopensci.org/peer-review-guide/software-peer-review-guide/author-guide.html#does-your-package-meet-packaging-requirements).
196197
We hope that these bare minimal checks help maintainers as they try to decide
197198
what is good enough infrastructure for their package.
198199

0 commit comments

Comments
 (0)