|
| 1 | +--- |
| 2 | +layout: splash |
| 3 | +permalink: /about-peer-review/ |
| 4 | +title: "About the pyOpenSci Open Peer Review Process" |
| 5 | +header: |
| 6 | + overlay_image: images/header.jpg |
| 7 | + overlay_filter: 0.6 |
| 8 | +intro: |
| 9 | + - excerpt: "Our open peer review process supports scientists getting credit for the work invested in open Python tools. It also supports standardization of packaging and improved package visibility." |
| 10 | +toc: false |
| 11 | +classes: wide |
| 12 | +--- |
| 13 | + |
| 14 | +{% include feature_row id="intro" type="center" %} |
| 15 | + |
| 16 | +<!--TODO: this into a template --> |
| 17 | + |
| 18 | +<div class="feature__wrapper"> |
| 19 | + <div class="feature__item "> |
| 20 | + <div class="archive__item cards"> |
| 21 | + <div class="archive__item-body"> |
| 22 | + <h2 class="archive__item-title">Ready to Submit a Package for Review?</h2> |
| 23 | + <div class="archive__item-excerpt"> |
| 24 | + <p>You're in the right place! Learn about the steps to submit a package |
| 25 | + for open peer review in our guidebook. </p> |
| 26 | + </div> |
| 27 | + <p><a href="https://www.pyopensci.org/peer-review-guide/software-peer-review-guide/author-guide.html" class="btn btn--inverse"><i class="fas fa-angle-right"></i> View our Author Guide </a></p> |
| 28 | + </div> |
| 29 | + </div> |
| 30 | + </div> |
| 31 | + |
| 32 | + <div class="feature__item"> |
| 33 | + <div class="archive__item cards"> |
| 34 | + <div class="archive__item-body"> |
| 35 | + <h2 class="archive__item-title">Want to Review a Python Package for Us?</h2> |
| 36 | + <div class="archive__item-excerpt"> |
| 37 | + <p>We could use your help! Fill our our reviewer form. We will |
| 38 | + contact you if we have a package that we need reviewers for. |
| 39 | + It's OK if you've never reviewed a package before! We'll walk you |
| 40 | + through it. </p> |
| 41 | + </div> |
| 42 | + <p><a href="https://forms.gle/GHfxvmS47nQFDcBM6" class="btn btn--inverse"><i class="fas fa-angle-right"></i> |
| 43 | + Signup Now (Google Form) </a></p> |
| 44 | + </div> |
| 45 | + </div> |
| 46 | + </div> |
| 47 | + |
| 48 | + <div class="feature__item"> |
| 49 | + <div class="archive__item cards"> |
| 50 | + <div class="archive__item-body"> |
| 51 | + <h2 class="archive__item-title">See Our Review Process in Action</h2> |
| 52 | + <div class="archive__item-excerpt"> |
| 53 | + <p>Our reviewers happen in GitHub issues. This means that anyone can |
| 54 | + check in on any part of any review and read all of the conversation. |
| 55 | + Check it out.</p> |
| 56 | + </div> |
| 57 | + <p><a href="https://github.com/pyOpenSci/software-review/issues" class="btn btn--inverse"><i class="fas fa-angle-right"></i> See Open Reviews </a></p> |
| 58 | + </div> |
| 59 | + </div> |
| 60 | + </div> |
| 61 | +</div> |
| 62 | + |
| 63 | +<div class="wide__p_text" markdown="1"> |
| 64 | +## Why Peer Review for Python Scientific Software? |
| 65 | +Peer review of Python scientific software addresses several challenges in the |
| 66 | +open source community: |
| 67 | + |
| 68 | +1. **Citations Support Credit & Acknowledgement:** Peer review provides credit and acknowledgement for the hard work invested in creating and supporting core tools that support open science workflows. |
| 69 | +2. **Standard Packaging & Documentation:** Currently there are numerous ways to create a Python package. Peer review enforces standards thus promoting standardization of Python packaging across the scientific Python ecosystem. |
| 70 | +3. **Removed Redundancy:** Peer review addresses the issue of multiple tools on pyPi that perform similar tasks but have varying levels of documenation, support and maintainence. One maintained package that is broadly useful and maintained will help scientists select tools that they can rely on. |
| 71 | +4. **Long Term Maintenance:** Package maintainers often use their free time to work on Python tools. Once a package is reviewed by pyOpenSci we will keep in touch with the maintainer to ensure continued maintainance of the tool. If a maintainer needs to step down, we will try to find someone new to take over, or sunset the tool as needed. |
| 72 | +5. **Community:** At the core of peer review is community around the tools that scientists need to process their data. |
| 73 | + |
| 74 | +### Who can submit a package? |
| 75 | +pyOpenSci packages are community developed, submitted and reviewed. Anyone is |
| 76 | +welcome to submit a package to pyOpenSci to be reviewed. Once the package is reviewed, |
| 77 | +and accepted, pyOpenSci will promote it as a peer-reviewed tool for science! |
| 78 | + |
| 79 | +### How do I decide whether to submit to you or the Journal of Open Source Software (JOSS) |
| 80 | + |
| 81 | +You don't have to chose between pyOpenSci and JOSS. We have a collaboration with |
| 82 | +JOSS where you can submit your package to us for review. If your package is accepted |
| 83 | +and if it is in scope for JOSS, it will then be fast tracked through their |
| 84 | +review process; they will only review your paper.md file. Consider this a |
| 85 | +win-win! |
| 86 | + |
| 87 | +</div> |
| 88 | + |
| 89 | +<!-- |
| 90 | +<div class="notice" markdown="1"> |
| 91 | +## What's the difference between pyOpenSci and JOSS? |
| 92 | +
|
| 93 | +> You don't have to chose between pyOpenSci and JOSS; You can submit your package to both. |
| 94 | +
|
| 95 | +pyOpenSci and [the Journal of Open Source Software (JOSS)](https://joss.theoj.org/) |
| 96 | +are complementary, partner organizations; and you don't have to chose one or the |
| 97 | +other! After a package to pyOpenSci has been reviewed and accepted by pyOpenSci |
| 98 | +you can chose to also register it with JOSS. JOSS has [more limited scope](https://joss.readthedocs.io/en/latest/review_criteria.html) of the |
| 99 | +for packages that it will review. For instance while pyOpenSci will review and |
| 100 | +accept API wrappers, JOSS won't. |
| 101 | +
|
| 102 | +If your package is accepted by pyOpenSci and in scope for JOSS, JOSS will fast |
| 103 | +track your package through their process given it was already reviewed by us. |
| 104 | +Once accepted by JOSS, you now have both a pyOpenSci acceptance and one by JOSS. |
| 105 | +Joss will then give you a cross-ref supported DOI for citation. |
| 106 | +
|
| 107 | +### Why Two Review Processes JOSS and pyOpenSci? |
| 108 | +
|
| 109 | +the pyOpenSci review process is different from that of JOSS in a few ways: |
| 110 | +* pyOpenSci is specific to the Python community and thus will enforce community specific python specific standards. |
| 111 | +* pyOpenSci places heavy emphasis on documentation and usability in our reviews and associated standardization of both. |
| 112 | +* pyOpenSci builds community around and visibility for it's tools. |
| 113 | +* pyOpenSci supports long term tool maintenance. |
| 114 | +
|
| 115 | +
|
| 116 | +JOSS reviews are [more limited in scope](https://joss.readthedocs.io/en/latest/review_criteria.html) compared to pyOpenSci and the |
| 117 | +[submission criteria](https://joss.readthedocs.io/en/latest/review_criteria.html) |
| 118 | +are, in places, less stringent than those of pyOpenSci. |
| 119 | +</div> |
| 120 | +
|
| 121 | +
|
| 122 | +
|
| 123 | +--> |
| 124 | + |
| 125 | +## Our editorial board |
| 126 | + |
| 127 | +We value our volunteer editors. Learn more about what editors do and how we select |
| 128 | +them here. |
| 129 | + |
| 130 | +{% assign editors = site.data.contributors | where: 'editor', true %} |
| 131 | + |
| 132 | +<div class="grid people"> |
| 133 | +{% for aperson in editors %} |
| 134 | + <article class="person__item" itemscope="" itemtype="https://schema.org/CreativeWork"> |
| 135 | + {% if aperson.github_image_id %} |
| 136 | + <div> |
| 137 | + <img src="https://avatars1.githubusercontent.com/u/{{ aperson.github_image_id }}?s=400&v=4" alt="image of {{ aperson.name}}" class="contrib_avatar"> |
| 138 | + </div> |
| 139 | + {% endif %} |
| 140 | + <div class="about_person"> |
| 141 | + <h4 class="grid_title" itemprop="headline"> |
| 142 | + <a href="https://www.github.com/{{ aperson.github_username }}" rel="permalink"> {{ aperson.name }} |
| 143 | + </a> |
| 144 | + </h4> |
| 145 | + <p class="page__meta title"> |
| 146 | + {% if aperson.title %} |
| 147 | + {{ aperson.title }} |
| 148 | + {% endif %} |
| 149 | + </p> |
| 150 | + <p class="page__meta focus-areas"> |
| 151 | + {% if aperson.focus-areas %} |
| 152 | + {% for anArea in aperson.focus-areas %} |
| 153 | + {{ anArea }}{% if forloop.last == false %}, {% endif %} |
| 154 | + {% endfor %} |
| 155 | + {% endif %} |
| 156 | + </p> |
| 157 | + </div> |
| 158 | + <!-- Contribution types --> |
| 159 | + <p class="page__meta bio"> |
| 160 | + <span> |
| 161 | + {{ aperson.name}} is also a |
| 162 | + {% for atype in aperson.contributor_type %} |
| 163 | + {{ atype }}{% if forloop.last == false %}, {% endif %} |
| 164 | + {% endfor %} for pyOpenSci. |
| 165 | + </span> |
| 166 | + </p> |
| 167 | + <p class="contrib_org" itemprop="organization"> Affiliation: {{ aperson.organization }} </p> |
| 168 | + </article> |
| 169 | +{% endfor %} |
| 170 | +</div> |
| 171 | + |
| 172 | +<br style="clear:both"> |
0 commit comments