|
| 1 | +--- |
| 2 | +layout: single |
| 3 | +title: "pyOpenSci Editorial Process - New Editor in Chief and a Call For Editors" |
| 4 | +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." |
| 5 | +author: "Leah Wasser" |
| 6 | +permalink: /blog/python-software-review-process-editor-in-chief |
| 7 | +header: |
| 8 | + overlay_color: "#666" |
| 9 | + overlay_filter: 0.6 |
| 10 | +categories: |
| 11 | + - updates |
| 12 | + - blog-post |
| 13 | + - highlight |
| 14 | + - peer-review |
| 15 | +--- |
| 16 | + |
| 17 | +## An update on pyOpenSci's review process |
| 18 | + |
| 19 | +Hey there! I just wanted to update everyone about where pyOpenSci is with |
| 20 | +its peer review process. We are currently hard at work updating [our guides](https://www.pyopensci.org/contributing-guide/intro.html) to |
| 21 | +streamline the peer review process. For the next 2 months (October & November 2022) |
| 22 | +we will prioritize setting up an editorial board to support new reviews as they |
| 23 | +come in. |
| 24 | + |
| 25 | +With that below you will find a few updates. |
| 26 | + |
| 27 | +## A Warm welcome to our first Editor in Chief, David Nicholson! |
| 28 | + |
| 29 | +[David Nicholson](https://github.com/NickleDave), who has been working with pyOpenSci for the past few years as |
| 30 | +an editor will take on the Editor in Chief role! [You can learn more about that |
| 31 | +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. |
| 32 | + |
| 33 | +As Editor in Chief, David will: |
| 34 | + |
| 35 | +* Be the first person to reach out to anyone submitting a new review or a pre-submission. |
| 36 | +* Perform initial software checks to ensure your package is ready for |
| 37 | +* Facilitate kicking off the peer review process by finding an editor for your package |
| 38 | + |
| 39 | +David has a background in behavioral / neuro / cognitive science and is a machine learning guru. |
| 40 | +Of course, he's a Pythonista through and through. We are lucky to have David as a |
| 41 | +part of our pyOpenSci team. |
| 42 | + |
| 43 | +*Stay tuned for a blog post from David introducing himself.* |
| 44 | + |
| 45 | +## We are creating an editorial board! |
| 46 | + |
| 47 | +To support our open peer review, we want to bring on a few people (like yourself?!) |
| 48 | +to serve as guest editors / editors. Here's how this works: |
| 49 | + |
| 50 | +If you are new to our organization, we start you as a guest editor. What this |
| 51 | +means is that you will review one package and we will support you in that |
| 52 | +process to ensure you learn the ropes. Then if you are happy and work well |
| 53 | +with our editorial team we will bring you on officially as an editor. |
| 54 | + |
| 55 | +Editors at pyOpenSci make a minimum of a 1-year commitment with a possibility of |
| 56 | +longer given mutual consent. You will be responsible for handling 3-4 package |
| 57 | +reviews during that year. We may also bring on guest editors in other |
| 58 | +instances, e.g., because of their familiarity with a specific domain. |
| 59 | + |
| 60 | +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). |
| 61 | + |
| 62 | +We currently have a package in the queue that is spatial / remote sensing related |
| 63 | +that we'd love to have an editor onboard to review. But we are in need of editors |
| 64 | +from other domain backgrounds too. |
| 65 | +{: .notice } |
| 66 | + |
| 67 | +### What background do I need to be an editor for pyOpenSci? |
| 68 | + |
| 69 | +We welcome applications from potential editors with significant experience in |
| 70 | +one or more of the following areas: |
| 71 | +* open source software, |
| 72 | +* open science |
| 73 | +* software engineering |
| 74 | +* peer-review |
| 75 | + |
| 76 | +Members of the pyOpenSci editorial team have diverse backgrounds. We welcome |
| 77 | +editors from academia, government, and industry. We especially welcome |
| 78 | +applications from prospective editors who will contribute to the diversity |
| 79 | +(ethnic, gender, disciplinary, and geographical) of our board. We also value |
| 80 | +having a range of junior and senior editors. |
| 81 | + |
| 82 | + |
| 83 | +### How do I apply? |
| 84 | + |
| 85 | +To sign up to be considered as an editor for pyOpenSci, please fill out the |
| 86 | +form below: |
| 87 | + |
| 88 | +[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} |
| 89 | + |
| 90 | +## Questions? |
| 91 | +If you have any questions, please reach out to me at leah at pyopensci.org or on |
| 92 | +twitter at [@LeahAWasser](https://twitter.com/LeahAWasser). |
0 commit comments