BLOG: editorial board updates-call for editors

_data/authors.yml

@@ -1,6 +1,6 @@
 Leah Wasser:
   name        : "Leah Wasser"
-  bio         : "Director of Earth Analytics Education at Earth Lab, CU Boulder."
+  bio         : "Executive Director, pyOpenSci"
   avatar      : "/images/people/leah-wasser-pyopensci-leadership.jpg"
   links:
     - label: "Email"

_pages/contributors.md

@@ -7,6 +7,8 @@ classes:
 header:
     overlay_image: images/header.jpg
     overlay_filter: 0.6
+redirect_from:
+  - /contributors/
 ---
 
 ## Our pyOpenSci Community 

_pages/home.md

@@ -56,7 +56,7 @@ programs:
    {% endfor %}
 </div>
 
-<p><a href="/python-packages/" class="btn btn--info btn--large">View All Posts <i class="fa fa-4 fa-arrow-circle-right" aria-hidden="true"></i></a></p>
+<p><a href="/blog/" class="btn btn--info btn--large">View All Posts <i class="fa fa-4 fa-arrow-circle-right" aria-hidden="true"></i></a></p>
 </div>
 
 

_posts/2020-04-29-movingpandas-movement-data-analysis.md

@@ -12,10 +12,9 @@ categories:
   - blog-post
   - pandas
   - spatial
-  - highlight
 ---
 
-Movement data is everywhere: from tracking apps that record human or vehicle movement to ecologists monitoring wildlife behaviour. Movement data analysis is challenging since movement data combines time series and spatial data analyses questions. Existing spatial analysis libraries, such as GeoPandas, are great at handling spatial data but they don't support moving objects. 
+Movement data is everywhere: from tracking apps that record human or vehicle movement to ecologists monitoring wildlife behavior. Movement data analysis is challenging since movement data combines time series and spatial data analyses questions. Existing spatial analysis libraries, such as GeoPandas, are great at handling spatial data but they don't support moving objects. 
 
 MovingPandas aims to fill the gap of missing tools for exploring movement data. It provides data structures and methods for dealing with data of moving objects. MovingPandas has been accepted by pyOpenSci as part of its ecosystem in March 2020. 
 

_posts/2022-09-27-call-for-python-software-review-editors.md

@@ -0,0 +1,90 @@
+---
+layout: single
+title: "pyOpenSci Editorial Process - New Editor in Chief and a Call For Editors"
+excerpt: "pyOpenSci is developing it's 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 
+it's peer review process. We are currently hard at work updating [our peer 
+review 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 a editorial board to support new reviews as they 
+come in. 
+
+With that below you will find a few updates.
+
+## Welcome 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. David will:
+
+* Be the first person to reach out to anyone submitting a new review or a pre-submission. 
+* He will perform initial software checks to ensure your package is ready for  
+* He will also facilitate kicking off the peer review process by finding an editor for your package
+
+David has a background behavioral / neuro / cognitive science and is a ML guru. 
+Of course,  he's a Pythonista thru and thru. 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:
+
+Editors at pyOpenSci make a minimum of a 1-year commitment with a possibility
+of longer given mutual consent. We also 
+support guest editors in some instances. You will be responsible for handling 3-4 
+package reviews during that year. 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 as a 
+"full editor".
+
+
+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).
+
+### 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 JOSS editorial team have diverse backgrounds. We welcome 
+JOSS 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.
+
+
+
+