Editor Role Description#

Thank you for your time in serving as an editor for a pyOpenSci package! Below, you will find some information about the role that editors have in the pyOpenSci Python open peer review process.

Experience needed to become an editor#

Editors generally should:

  • Have completed a review for at least 1 package for pyOpenSci.

  • Have some experience with open-source software that supports the scientific Python community. This experience could be maintaining or contributing to packages. It could also be experience related to usability of open-source software and/or documentation, tutorials, etc. Alternatively, it could involve participation in the broader scientific Python community in another capacity.

Two types of editors#

There are two types of editors involved in our open peer review process:

  • Guest editors and

  • Full editors

Both types of editors are considered a part of the editorial board for pyOpenSci. The significant differences between guest and full editors are:

  • A guest editor may only join the board for a single review.

  • A guest editor may be new to pyOpenSci’s review process and thus require a bit more support in their first review.

Guest editors#

A guest editor is invited to lead a review in the case where we need specific expertise for a single review. We also consider editors who are performing their first review as guest editors, as they may require more guidance or mentorship to complete the review (if they are new to our organization).

New editors who wish to continue as full editors for pyOpenSci may do so as long as both parties (pyOpenSci and the guest editors) feel like it is a healthy fit for them and the organization.

“Full” editors#

A full editor is most often someone who has experience with the pyOpenSci open package review process. A full editor ideally:

  • has completed a review for at least 1 package for pyOpenSci

  • and/or has submitted and gone through the pyOpenSci package review process

  • and/or has experience reviewing for an organization such as JOSS or rOpenSci.

We also appreciate when editors have experience working with or in the Python open source software community, be it maintaining packages, contributing to packages, or supporting the community. However, prior open source experience is not required. pyOpenSci offers many opportunities to get started as a contributor to open source.

Note

There could be certain situations when an editor is onboarded with less experience! The above are simply guidelines that we like to follow.

What does an editor do? (Responsibilities)#

An editor is usually recruited by the Editor in Chief, other editors on the board, or the software review lead. More on recruiting editors can be found here.

An editor is responsible for:

  • Leading the review process for 3-4 packages a year

  • Weighing in on group editorial decisions such as whether a package is in scope, and making updates to the pyOpenSci policies.

Note

Decisions surrounding policy, updates to peer review guides, and decisions on package review are generally made in the private editorial-board channel in the pyOpenSci Slack organization. Please make sure that you are comfortable with checking Slack regularly.

Editor support of other reviews#

Editors are not charged with tracking other submissions that they are not leading. However, if you are serving as an editor and notice an issue with another review, please raise that issue either directly with the editor for that review. Or you can raise the issue in the private-editorial-team Slack channel.

Editor-in-Chief rotation#

The editorial board normally participates in the Editor in Chief rotation. You are eligible to enter this rotation after 3 months of serving on the editorial board and/or after your first review as it makes sense. Read more about the roles and responsibilities of the Editor in Chief, here.

If the Editor in Chief role feels like too much responsibility, an editor can also decline being a part of this rotation.

How long does an editor serve on the editorial board?#

Ideally, an editor can commit to serving for at least one year as an editor for pyOpenSci. During that year, we expect that you will lead the review of 3-4 packages. However, we understand that in certain situations, an editor may need to step down before the 1 year time period has ended.

We also understand that life gets busy. You are always welcome to “say no” to a review during a busy time.

We welcome editors staying on for longer as long as they are happy serving with us and they get along well with other members of the editorial board, the software review lead and the current Editor in Chief.

Closing notes about the editorial process#