-
Notifications
You must be signed in to change notification settings - Fork 63
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
BLOG: editorial board updates-call for editors (#93)
Co-authored-by: David Nicholson <[email protected]>
- Loading branch information
1 parent
8e0ce7d
commit b1c8268
Showing
5 changed files
with
97 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
92 changes: 92 additions & 0 deletions
92
_posts/2022-09-27-call-for-python-software-review-editors.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,92 @@ | ||
--- | ||
layout: single | ||
title: "pyOpenSci Editorial Process - New Editor in Chief and a Call For Editors" | ||
excerpt: "pyOpenSci is developing its open peer review process for Python scientific software. Learn about our structure and if you are interested, apply to be on our editorial board." | ||
author: "Leah Wasser" | ||
permalink: /blog/python-software-review-process-editor-in-chief | ||
header: | ||
overlay_color: "#666" | ||
overlay_filter: 0.6 | ||
categories: | ||
- updates | ||
- blog-post | ||
- highlight | ||
- peer-review | ||
--- | ||
|
||
## An update on pyOpenSci's review process | ||
|
||
Hey there! I just wanted to update everyone about where pyOpenSci is with | ||
its peer review process. We are currently hard at work updating [our guides](https://www.pyopensci.org/contributing-guide/intro.html) to | ||
streamline the peer review process. For the next 2 months (October & November 2022) | ||
we will prioritize setting up an editorial board to support new reviews as they | ||
come in. | ||
|
||
With that below you will find a few updates. | ||
|
||
## A Warm welcome to our first Editor in Chief, David Nicholson! | ||
|
||
[David Nicholson](https://github.com/NickleDave), who has been working with pyOpenSci for the past few years as | ||
an editor will take on the Editor in Chief role! [You can learn more about that | ||
role here](https://www.pyopensci.org/contributing-guide/open-source-software-submissions/editor-in-chief-guide.html) in our peer review guide. This position will rotate once we have our editorial board setup. | ||
|
||
As Editor in Chief, David will: | ||
|
||
* Be the first person to reach out to anyone submitting a new review or a pre-submission. | ||
* Perform initial software checks to ensure your package is ready for | ||
* Facilitate kicking off the peer review process by finding an editor for your package | ||
|
||
David has a background in behavioral / neuro / cognitive science and is a machine learning guru. | ||
Of course, he's a Pythonista through and through. We are lucky to have David as a | ||
part of our pyOpenSci team. | ||
|
||
*Stay tuned for a blog post from David introducing himself.* | ||
|
||
## We are creating an editorial board! | ||
|
||
To support our open peer review, we want to bring on a few people (like yourself?!) | ||
to serve as guest editors / editors. Here's how this works: | ||
|
||
If you are new to our organization, we start you as a guest editor. What this | ||
means is that you will review one package and we will support you in that | ||
process to ensure you learn the ropes. Then if you are happy and work well | ||
with our editorial team we will bring you on officially as an editor. | ||
|
||
Editors at pyOpenSci make a minimum of a 1-year commitment with a possibility of | ||
longer given mutual consent. You will be responsible for handling 3-4 package | ||
reviews during that year. We may also bring on guest editors in other | ||
instances, e.g., because of their familiarity with a specific domain. | ||
|
||
You can read more about the [roles and responsibilities of and editor here](https://www.pyopensci.org/contributing-guide/open-source-software-submissions/editors-guide.html). | ||
|
||
We currently have a package in the queue that is spatial / remote sensing related | ||
that we'd love to have an editor onboard to review. But we are in need of editors | ||
from other domain backgrounds too. | ||
{: .notice } | ||
|
||
### What background do I need to be an editor for pyOpenSci? | ||
|
||
We welcome applications from potential editors with significant experience in | ||
one or more of the following areas: | ||
* open source software, | ||
* open science | ||
* software engineering | ||
* peer-review | ||
|
||
Members of the pyOpenSci editorial team have diverse backgrounds. We welcome | ||
editors from academia, government, and industry. We especially welcome | ||
applications from prospective editors who will contribute to the diversity | ||
(ethnic, gender, disciplinary, and geographical) of our board. We also value | ||
having a range of junior and senior editors. | ||
|
||
|
||
### How do I apply? | ||
|
||
To sign up to be considered as an editor for pyOpenSci, please fill out the | ||
form below: | ||
|
||
[Click here to apply to be an editor <i class="fa fa-4 fa-arrow-circle-right" aria-hidden="true"></i>](https://forms.gle/YH4kTeDFoYjDtefh7){: .btn .btn--info .btn--large} | ||
|
||
## Questions? | ||
If you have any questions, please reach out to me at leah at pyopensci.org or on | ||
twitter at [@LeahAWasser](https://twitter.com/LeahAWasser). |