-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating draft 2024 call for editors #34
Conversation
|
||
Once again, we're looking to grow our editorial team at JOSS! | ||
|
||
Since our launch in [May 2016](https://www.arfon.org/announcing-the-journal-of-open-source-software), our [existing editorial team](http://joss.theoj.org/about#editorial_board) has handled nearly 4500 submissions (~2700 published at the time of writing, 340 under review) and the demand from the community continues to be strong. JOSS now consistently publishes a little over one paper per day, and we see no sign of this demand dropping. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So we're rejected 1/3 of our submissions? This seems high, but maybe so...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue count on openjournals/joss-reviews
might be more reliable here. There are 4134 pre-review issues that have ever existed. Assuming a few testing ones along the way, I think 4100 would be a pretty safe number.
|
||
The [JOSS editorial team](http://joss.theoj.org/about#editorial_board) will review your applications and make their recommendations. Highly-ranked candidates will then have a short (~30 minute) phone call/video conference interview with the editor(s)-in-chief. Successful candidates will then join the JOSS editorial team for a probational period of 3 months before becoming a full member of the editorial team. You will get an onboarding “buddy” from the experienced editors to help you out during that time. | ||
|
||
_Dan Foreman-Mackey, Olivia Guest, Daniel S. Katz, Kevin M. Moerman, Kyle E. Niemeyer, Arfon M. Smith, Kristen Thyng_ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add Sam?
Co-authored-by: Daniel S. Katz <[email protected]>
Co-authored-by: Daniel S. Katz <[email protected]>
Co-authored-by: Daniel S. Katz <[email protected]>
Co-authored-by: Daniel S. Katz <[email protected]>
@@ -48,8 +42,19 @@ We are especially interested in recruiting editors in the following disciplines, | |||
|
|||
The JOSS editorial team has a diverse background and there is no requirement for JOSS editors to be working in academia. | |||
|
|||
### Expected level of committment | |||
|
|||
Editing for JOSS is a substantial committment, and we would encourage you to read our [editorial guide](https://joss.readthedocs.io/en/latest/editing.html), and in particular our [expectations of editors](https://joss.readthedocs.io/en/latest/expectations.html). While the guide has a bunch more information, some things we think are particulatly important include 1) pay ongoing attention to the submissions they are handling (i.e., checking in on papers ~twice per week for a few minutes at a time), 2) responding in a timely fashion to invites to edit, and 3) contributing to the overall editorial team (e.g., participating in scope reviews, giving feedback to colleagues in Slack). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggested edit
Editing for JOSS is a substantial commitment, and we would encourage you to read our editorial guide, and in particular our expectations of editors. While the guide has a bunch more information, some things we think are particularly important include 1) paying ongoing attention to the submissions they are handling (i.e., checking in on papers ~twice per week for a few minutes at a time), 2) responding in a timely fashion to invites to edit, and 3) contributing to the overall editorial team (e.g., participating in scope reviews, giving feedback to colleagues in Slack).
EOM