From 43b905ffc3197dd9c639db86924756bf90e211b7 Mon Sep 17 00:00:00 2001 From: Leah Wasser Date: Tue, 27 Sep 2022 11:08:06 -0600 Subject: [PATCH 1/3] BLOG: editorial board updates-call for editors --- _data/authors.yml | 2 +- _pages/contributors.md | 2 + _pages/home.md | 2 +- ...-29-movingpandas-movement-data-analysis.md | 3 +- ...call-for-python-software-review-editors.md | 90 +++++++++++++++++++ 5 files changed, 95 insertions(+), 4 deletions(-) create mode 100644 _posts/2022-09-27-call-for-python-software-review-editors.md diff --git a/_data/authors.yml b/_data/authors.yml index ba36145d..1d9fe42a 100644 --- a/_data/authors.yml +++ b/_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" diff --git a/_pages/contributors.md b/_pages/contributors.md index 315ca702..9c89fe97 100644 --- a/_pages/contributors.md +++ b/_pages/contributors.md @@ -7,6 +7,8 @@ classes: header: overlay_image: images/header.jpg overlay_filter: 0.6 +redirect_from: + - /contributors/ --- ## Our pyOpenSci Community diff --git a/_pages/home.md b/_pages/home.md index e7eb89ee..861dcf43 100644 --- a/_pages/home.md +++ b/_pages/home.md @@ -56,7 +56,7 @@ programs: {% endfor %} -

View All Posts

+

View All Posts

diff --git a/_posts/2020-04-29-movingpandas-movement-data-analysis.md b/_posts/2020-04-29-movingpandas-movement-data-analysis.md index 0cc00131..a48c4e65 100644 --- a/_posts/2020-04-29-movingpandas-movement-data-analysis.md +++ b/_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. diff --git a/_posts/2022-09-27-call-for-python-software-review-editors.md b/_posts/2022-09-27-call-for-python-software-review-editors.md new file mode 100644 index 00000000..8284a0bf --- /dev/null +++ b/_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 ](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. + + + + From 4b706289f5e68ef79a0c1fc499140073cb8f385f Mon Sep 17 00:00:00 2001 From: Leah Wasser Date: Mon, 3 Oct 2022 12:13:07 -0600 Subject: [PATCH 2/3] REVIEW: edits from David Co-authored-by: David Nicholson --- ...call-for-python-software-review-editors.md | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/_posts/2022-09-27-call-for-python-software-review-editors.md b/_posts/2022-09-27-call-for-python-software-review-editors.md index 8284a0bf..a56e2340 100644 --- a/_posts/2022-09-27-call-for-python-software-review-editors.md +++ b/_posts/2022-09-27-call-for-python-software-review-editors.md @@ -1,7 +1,7 @@ --- 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." +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: @@ -17,10 +17,10 @@ categories: ## 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 +its 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 +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. @@ -32,11 +32,11 @@ 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 +* 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 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 +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. @@ -83,7 +83,10 @@ form below: ## Questions? If you have any questions, please reach out to me at leah at pyopensci.org or on -twitter at @leahawasser. +twitter at [@LeahAWasser](https://twitter.com/LeahAWasser)``` + +* twitter can be case-sensitive when you try to @ user names +* might as well link to your twitter profile while you're at it From 3fbd3230ff3af8f3e3debd4768ded942d05a9995 Mon Sep 17 00:00:00 2001 From: Leah Wasser Date: Mon, 3 Oct 2022 12:22:44 -0600 Subject: [PATCH 3/3] CONTENT: final editor in chief blog :sparkles : --- ...call-for-python-software-review-editors.md | 47 +++++++++---------- 1 file changed, 23 insertions(+), 24 deletions(-) diff --git a/_posts/2022-09-27-call-for-python-software-review-editors.md b/_posts/2022-09-27-call-for-python-software-review-editors.md index a56e2340..5d9ff732 100644 --- a/_posts/2022-09-27-call-for-python-software-review-editors.md +++ b/_posts/2022-09-27-call-for-python-software-review-editors.md @@ -17,19 +17,20 @@ categories: ## 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 peer -review guides](https://www.pyopensci.org/contributing-guide/intro.html) to +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. -## Welcome Editor in Chief David Nicholson +## 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. David will: +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 @@ -39,24 +40,29 @@ David has a background in behavioral / neuro / cognitive science and is a machin 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. +*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". +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). -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? @@ -67,8 +73,8 @@ one or more of the following areas: * 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 +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. @@ -83,11 +89,4 @@ form below: ## 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)``` - -* twitter can be case-sensitive when you try to @ user names -* might as well link to your twitter profile while you're at it - - - - +twitter at [@LeahAWasser](https://twitter.com/LeahAWasser).