Skip to content

Commit 785a2b3

Browse files
authored
BLOG: call for editors post
posting with incorporated edits from Leah
2 parents 508b3f1 + c4ade43 commit 785a2b3

File tree

2 files changed

+51
-0
lines changed

2 files changed

+51
-0
lines changed
Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
---
2+
layout: single
3+
title: "Volunteers needed: pyOpenSci Editorial Board"
4+
excerpt: "pyOpenSci is looking for volunteers from a wide array of scientific backgrounds to join our Editorial Board."
5+
author: "Jesse Mostipak"
6+
permalink: /blog/pyos-call-for-editors-may-2024.html
7+
header:
8+
overlay_image: images/blog/headers/23-05-2024-call-for-editors.png
9+
overlay_filter: 0.6
10+
categories:
11+
- blog-post
12+
- community
13+
classes: wide
14+
toc: true
15+
comments: true
16+
---
17+
## Join the pyOpenSci Editorial Board
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 volunteer editors to our Editorial Board.
20+
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+
{: .notice}
23+
24+
The pyOpenSci Editorial Board is comprised of a diverse group of volunteers, with each editor being responsible for the following tasks:
25+
26+
* Finding reviewers from diverse backgrounds who have a mixture of scientific domain, software usability and Python experience.
27+
* Overseeing the entire review process for a package ensuring it runs in a timely and efficient manner.
28+
* Supporting the submitting authors and reviewers in answering questions related to the review.
29+
* Determining whether that package should be accepted into the pyOpenSci ecosystem once the review has wrapped up.
30+
31+
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!
32+
33+
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.
34+
35+
**IMPORTANT:** We do not expect any single editor to be an expert in all of these areas!
36+
37+
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!
38+
39+
If you're new to the pyOpenSci review process, we do also have Guest Editor volunteer roles, where you'll have more guidance or mentorship in order to complete the review.
40+
{: .notice}
41+
42+
### Apply to be a pyOpenSci editor
43+
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).
44+
45+
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).
46+
47+
## Meet our current Editorial Board
48+
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).
49+
50+
## Connect with pyOpenSci
51+
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)!
Loading

0 commit comments

Comments
 (0)