You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2024-05-23-pyos-call-for-editors.md
+7-3Lines changed: 7 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -16,11 +16,13 @@ comments: true
16
16
---
17
17
## Join the pyOpenSci Editorial Board
18
18
### We're currently in need of editors with domain expertise in climatology and/or energy, and also accepting applications from all scientific domains
19
-
Thanks to the efforts of our incredible team of volunteers, pyOpenSci is growing! As a result, we're currently seeing a large number of package submissions to [our open peer review process](https://www.pyopensci.org/about-peer-review/index.html). In order to continue supporting scientists in the development of open source scientific software, we're looking to add volunteers to our Editorial Board.
19
+
Thanks to the efforts of our incredible team of volunteers, pyOpenSci is growing! As a result, we're currently seeing a large number of package submissions to [our open peer review process](https://www.pyopensci.org/about-peer-review/index.html). In order to continue supporting scientists in the development of open source scientific software, we're looking to add volunteer editors to our Editorial Board.
20
20
21
21
> Learn more about the Volunteer Editor role in our [Editor Guide](https://www.pyopensci.org/software-peer-review/how-to/editors-guide.html).
22
22
23
-
The pyOpenSci Editorial Board is comprised of a diverse group of volunteers, with each editor being responsible for the following tasks:
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.
24
+
25
+
As an editor, you are responsible for the following tasks:
24
26
25
27
* Finding reviewers from diverse backgrounds who have a mixture of scientific domain and Python experience.
26
28
* Overseeing the entire review process for a package ensuring it runs in a timely and efficient manner.
@@ -29,7 +31,9 @@ The pyOpenSci Editorial Board is comprised of a diverse group of volunteers, wit
29
31
30
32
We often find that people interested in joining our Editorial Board are more than capable of performing the role, but sometimes doubt themselves. We want to strongly encourage you to apply if you're interested in the role. Not only do we offer support and guidance in your role as an Editor, we also have a warm, welcoming community that is always happy to help. Everyone starts somewhere, and we'd love for you to join us!
31
33
32
-
It's also critical to the pyOpenSci mission that our Editorial Board have a combined expertise in various scientific domains, technical expertise in Python packaging, awareness of the importance of documentation in package usability, and awareness of the importance of CI/test suites in order to ensure robust software development. We do not expect any single editor to be an expert in all of these areas!
34
+
It's also critical to the pyOpenSci mission that our Editorial Board have a combined expertise in various scientific domains, technical expertise in Python packaging, awareness of the importance of documentation in package usability, and awareness of the importance of CI/test suites in order to ensure robust software development.
35
+
36
+
**IMPORTANT:** We do not expect any single editor to be an expert in all of these areas!
33
37
34
38
We also appreciate when editors have experience working with or in the Python open source software community be it maintaining packages, contributing to packages, previously reviewing a pyOpenSci package, or supporting the community. This is certainly not a requirement, however, if you are interested in getting involved with pyOpenSci!
0 commit comments