Skip to content

Commit 8ed2f27

Browse files
committed
Fix: remove commented text
1 parent 255b95a commit 8ed2f27

File tree

1 file changed

+4
-71
lines changed

1 file changed

+4
-71
lines changed

_pages/about-peer-review.md

Lines changed: 4 additions & 71 deletions
Original file line numberDiff line numberDiff line change
@@ -140,8 +140,10 @@ classes: flowing
140140

141141
## Our editorial board
142142

143-
We value our volunteer editors. Learn more about what editors do and how we
144-
select them here.
143+
The peer review process is lead by a volunteer team of expert editors who
144+
find reviewers and ensure the review process is run efficiency from beginning
145+
to end. Learn more about the
146+
editor role at pyOpenSci [in our peer review guide, here.](https://www.pyopensci.org/software-peer-review/how-to/editors-guide.html)
145147

146148
{% assign editors = site.data.contributors | where: 'editorial_board', true %}
147149
{% assign editors = editors | sort: 'sort' %}
@@ -156,19 +158,6 @@ select them here.
156158

157159
<br clear="both">
158160
</div>
159-
<div class="wide__p_text" markdown="1">
160-
161-
162-
163-
164-
165-
<!-- ### Who can submit a package?
166-
167-
pyOpenSci packages are community developed, submitted and reviewed. Anyone is
168-
welcome to submit a package to pyOpenSci to be reviewed. Once the package is reviewed,
169-
and accepted, pyOpenSci will promote it as a peer-reviewed tool for science! -->
170-
171-
</div>
172161

173162

174163
<div class="content">
@@ -190,59 +179,3 @@ and accepted, pyOpenSci will promote it as a peer-reviewed tool for science! -->
190179
</div>
191180

192181
</div>
193-
194-
195-
196-
197-
198-
199-
200-
201-
<!--
202-
<div class="notice" markdown="1">
203-
## What's the difference between pyOpenSci and JOSS?
204-
205-
> You don't have to chose between pyOpenSci and JOSS; You can submit your package to both.
206-
207-
pyOpenSci and [the Journal of Open Source Software (JOSS)](https://joss.theoj.org/)
208-
are complementary, partner organizations; and you don't have to chose one or the
209-
other! After a package to pyOpenSci has been reviewed and accepted by pyOpenSci
210-
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
211-
for packages that it will review. For instance while pyOpenSci will review and
212-
accept API wrappers, JOSS won't.
213-
214-
If your package is accepted by pyOpenSci and in scope for JOSS, JOSS will fast
215-
track your package through their process given it was already reviewed by us.
216-
Once accepted by JOSS, you now have both a pyOpenSci acceptance and one by JOSS.
217-
Joss will then give you a cross-ref supported DOI for citation.
218-
219-
### Why Two Review Processes JOSS and pyOpenSci?
220-
221-
the pyOpenSci review process is different from that of JOSS in a few ways:
222-
* pyOpenSci is specific to the Python community and thus will enforce community specific python specific standards.
223-
* pyOpenSci places heavy emphasis on documentation and usability in our reviews and associated standardization of both.
224-
* pyOpenSci builds community around and visibility for it's tools.
225-
* pyOpenSci supports long term tool maintenance.
226-
227-
228-
JOSS reviews are [more limited in scope](https://joss.readthedocs.io/en/latest/review_criteria.html) compared to pyOpenSci and the
229-
[submission criteria](https://joss.readthedocs.io/en/latest/review_criteria.html)
230-
are, in places, less stringent than those of pyOpenSci.
231-
</div>
232-
233-
-->
234-
235-
236-
<!--
237-
## Benefits of peer review of scientific Python software?
238-
239-
Peer review of Python scientific software addresses several challenges in the open science and
240-
open source communities:
241-
242-
* Peer review gives scientists credit for the important work they are doing to support open science
243-
* Peer review improves the quality and usability of scientific Python packages making them easier for scientists to use and maintain
244-
* Peer review makes it easier for scientists to find trusted tools to support their workflows
245-
4. ** Long Term Maintenance in support of open science:** Scientists need to trust the tools that they are using in their open science workflow development. So what happens when a popular scientific tool's maintainer needs to step down from their critical open source work?
246-
247-
Once a package is reviewed by pyOpenSci we will keep in touch with the maintainer to ensure continued maintenance 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.
248-
5. **Community:** At the core of peer review is community around the tools that scientists need to process their data. -->

0 commit comments

Comments
 (0)