Skip to content

Commit 7bb0d2f

Browse files
committed
Fix: broken links
1 parent 16b149a commit 7bb0d2f

File tree

1 file changed

+12
-8
lines changed

1 file changed

+12
-8
lines changed

_pages/about-peer-review.md

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -15,13 +15,13 @@ scientists:
1515
benefits_scientists:
1616
- image_path: images/pyopensci-people-at-computer.jpg
1717
alt: "A pencil sketch of a round table with people sitting around it from different backgrounds working on laptops and also writing together."
18-
excerpt: "Scientists need trusted and vetted tools to support their open science workflows. Through our [partnerships with domain specific communities](partners.html) our catalog of trusted tools for scientists will grow. "
18+
excerpt: "Scientists need trusted and vetted tools to support their open science workflows. Through our [partnerships with domain specific communities](/partners.html) our catalog of trusted tools for scientists will grow. "
1919
title: "Benefits of software peer review for scientists"
2020
benefits_maintainers:
2121
- image_path: images/pyopensci-people-at-computer.jpg
2222
alt: "A pencil sketch of a round table with people sitting around it from different backgrounds working on laptops and also writing together."
2323
excerpt: "Peer review provides a form of academic credit currently unavailable to scientists developing software. Further, peer review multiplies shared knowledge, such as navigating the Python packaging ecosystem, which is challenging, even for seasoned Pythonistas. Our diverse community supports scientific package maintainers in their efforts to develop and build robust software."
24-
title: "Benefits of review & a supportive community for maintainers"
24+
title: "Benefits for open source maintainers"
2525
peer_review:
2626
- image_path: images/pyopensci-people-at-computer.jpg
2727
alt: "A pencil sketch of a round table with people sitting around it from different backgrounds working on laptops and also writing together."
@@ -125,10 +125,8 @@ classes: flowing
125125
</div>
126126
</div>
127127
</div>
128-
<!-- END template TODO -->
129-
130-
<!-- {% include feature_row id="joss" type="right" %} -->
131128

129+
<!-- END template TODO -->
132130

133131
</div>
134132
</div>
@@ -140,9 +138,15 @@ classes: flowing
140138

141139
## Our editorial board
142140

143-
The peer review process is lead by a volunteer team of expert editors who
144-
find reviewers and ensure the review process is run efficiency from beginning
145-
to end. Learn more about the
141+
The pyOpenSci software peer review process is lead by a volunteer team of
142+
editors from the scientific Python community. Editors do the following things:
143+
144+
* They find reviewers from diverse backgrounds for each package that is submitted that have a mixture of scientific domain and Python experience.
145+
* They oversee the entire review process for a package ensuring it runs in a timely and efficient manner
146+
* They support the submitting authors and reviewers in answering questions related to the review
147+
* They determine whether that package should be accepted into the pyOpenSci ecosystem once the review has wrapped up.
148+
149+
Learn more about the
146150
editor role at pyOpenSci [in our peer review guide, here.](https://www.pyopensci.org/software-peer-review/how-to/editors-guide.html)
147151

148152
{% assign editors = site.data.contributors | where: 'editorial_board', true %}

0 commit comments

Comments
 (0)