Skip to content

Commit 7ea8044

Browse files
committed
Merge branch '2024-05-23-call-for-editors' of https://github.com/kierisi/pyopensci.github.io into 2024-05-23-call-for-editors
2 parents 0f8eace + ae05639 commit 7ea8044

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

_posts/2024-05-23-pyos-call-for-editors.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,9 @@ Thanks to the efforts of our incredible team of volunteers, pyOpenSci is growing
2020

2121
> Learn more about the Volunteer Editor role in our [Editor Guide](https://www.pyopensci.org/software-peer-review/how-to/editors-guide.html).
2222
23-
The pyOpenSci Editorial Board is comprised of a diverse group of volunteers. As an editor, you join a diverse group of volunteers who care deeply about supporting the scientific Python software that scientists need to do their science. You will lead 2--4 package reviews a year, and the typical amount of time per review is anywhere from 1--3 hours a week. You may, however, spend a bit more time upfront finding reviewers, which is normally the trickiest part.
23+
The pyOpenSci Editorial Board is comprised of a diverse group of volunteers, with each editor being responsible for the following tasks:
2424

25-
As an editor, you are responsible for the following tasks:
26-
27-
* Finding reviewers from diverse backgrounds who have a mixture of scientific domain and Python experience.
25+
* Finding reviewers from diverse backgrounds who have a mixture of scientific domain, software usability and Python experience.
2826
* Overseeing the entire review process for a package ensuring it runs in a timely and efficient manner.
2927
* Supporting the submitting authors and reviewers in answering questions related to the review.
3028
* Determining whether that package should be accepted into the pyOpenSci ecosystem once the review has wrapped up.

0 commit comments

Comments
 (0)