Skip to content

Commit d3f0d17

Browse files
committed
post drafted
1 parent 20f089e commit d3f0d17

File tree

1 file changed

+22
-5
lines changed

1 file changed

+22
-5
lines changed

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

Lines changed: 22 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,22 +15,39 @@ toc: true
1515
comments: true
1616
---
1717
## Join the pyOpenSci Editorial Board
18+
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.
1819

20+
The pyOpenSci Editorial Board is comprised of a diverse group of volunteers, with each editor being responsible for the following tasks:
1921

20-
### How to apply to be a pyOpenSci editor
22+
* Finding reviewers from diverse backgrounds who have a mixture of scientific domain and Python experience.
23+
* Overseeing the entire review process for a package ensuring it runs in a timely and efficient manner.
24+
* Supporting the submitting authors and reviewers in answering questions related to the review.
25+
* Determining whether that package should be accepted into the pyOpenSci ecosystem once the review has wrapped up.
2126

27+
It's critical to our 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!
2228

23-
### Who can apply to be a pyOpenSci editor
29+
### Guest and Full editors
30+
pyOpenSci has two primary types of editors: guest and full. Both types of editors are considered a part of the editorial board for pyOpenSci. The major difference between guest and full editors is that a guest editor may only join the board for a single review, and may be new to pyOpenSci’s review process and thus require a bit more support in their first review.
2431

32+
In addition, a new editor will be considered “guest” for the first 3 months of their tenure and/or until they have completed their first review. Once they have a completed a review they can be considered to be a full editor as deemed appropriate by the software review lead and the current editorial board.
2533

26-
## About the pyOpenSci Editorial Board
34+
#### Guest editors
35+
A guest editor is is invited to lead a review in the case where we need specific expertise for a single review. We also consider editors who are performing their first review as guest editors as they may require more guidance or mentorship to complete the review (if they are new to our organization).
2736

37+
New editors who wish to continue on as full editors for pyOpenSci may do so as long as both parties (pyOpenSci and the guest editors) feel like it is a healthy fit for them and the organization.
2838

29-
## About pyOpenSci's open peer review process
39+
#### Full editors
40+
A full editor is most often someone who has experience with the pyOpenSci open package review process. A full editor ideally has completed a review for at least 1 package for pyOpenSci, and/or has submitted and gone through the pyOpenSci package review process, and/or has experience reviewing for an organization such as JOSS or rOpenSci.
3041

42+
We also appreciate when editors have experience working with or in the Python open source software community be it maintaining packages, contributing to packages, or supporting the community. This is certainly not a requirement however if you are interested in getting involved with pyOpenSci!
3143

32-
## About pyOpenSci
44+
### Apply to be a pyOpenSci editor
45+
We're currently looking for editors from a wide variety of scientific backgrounds, with a current focus on climatology and energy. If you feel you'd be a good fit for the pyOpenSci Editorial Board, please fill out [this form](https://docs.google.com/forms/d/e/1FAIpQLScRQHQ7NKVEAG3BKAphiUdVFvQ5nkez0IpyXBMZDzXjuBPloQ/viewform).
3346

47+
If you're interested in joining our Editorial Board, but have questions or would like to chat with someone from pyOpenSci about volunteering to be an editor, please email us at [media@pyopensci.org](mailto:media@pyopensci.org).
48+
49+
## Meet our current Editorial Board
50+
You can explore [our current directory of pyOpenSci editors](https://www.pyopensci.org/about-peer-review/index.html#meet-our-editorial-board) on our website, and also read [a series of short interviews](https://www.linkedin.com/pulse/meet-pyopensci-editorial-team-pyopensci-robpc/?trackingId=gE1IVxw%2BRX6P6NGP%2B%2BbM4Q%3D%3D) with many of our editors in a recent issue of [our weekly newsletter](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7179551305344933888).
3451

3552
## Connect with pyOpenSci
3653
Stay up-to-date with all things pyOpenSci by following us on [LinkedIn](https://www.linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci), and you can connect with the broader pyOpenSci community on our [Discourse forum](https://pyopensci.discourse.group/). Interested in our newsletters? We share news, blog posts, and monthly updates [in our LinkedIn newsletter](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7179551305344933888), and a monthly recap newsletter to [our mailing list](https://eepurl.com/iM7SOM)!

0 commit comments

Comments
 (0)