search

openjournals / paper-JOSS-oneyear

Paper describing design and first-year of JOSS
Creative Commons Attribution 4.0 International
0 stars 0 forks source link

PeerJ R1C2 #7

Closed kyleniemeyer closed 6 years ago

kyleniemeyer commented 6 years ago

Given the JOSS review happens entirely via a Github issue and presumably most reviewers are often working with their own projects on Github, do the JOSS editors make use of any special customisations or additions to try and help JOSS review comments stand out from the general "noise" of Github notifications a reviewer is likely exposed to? Or any other thoughts from the editors to try and help make sure JOSS review notifications are not missed, as briefly mentioned as a reason for some delayed reviews.

arfon commented 6 years ago

Yeah, this is a challenge.

do the JOSS editors make use of any special customisations or additions to try and help JOSS review comments stand out from the general "noise" of Github notifications a reviewer is likely exposed to?

No.

Or any other thoughts from the editors to try and help make sure JOSS review notifications are not missed, as briefly mentioned as a reason for some delayed reviews.

We encourage people when they start reviewing to unsubscribe from the joss-reviews repository e.g this automate message from Whedon: https://github.com/openjournals/joss-reviews/issues/451#issuecomment-342592174 . That way, any notifications they do receive on this repository will only be for their review threads. It's tough though and one of the main challenges of working on GitHub.

We could mention that we could ask reviewers for emails to give them an automated reminder (as we do for editors)

karthik commented 6 years ago

We encourage people when they start reviewing to unsubscribe from the joss-reviews repository e.g this automate message from Whedon: openjournals/joss-reviews#451 (comment) . That way, any notifications they do receive on this repository will only be for their review threads. It's tough though and one of the main challenges of working on GitHub.

I don't think this is what they were getting at. The reviewers don't really understand the mechanics of Whedon or that a submission adds them to the repo. I think they just meant it more broadly (which is my biggest source of suffering) that tagging someone wont necessarily alert them to their review request amidst the other noise of github issues.

karthik commented 6 years ago

We could just acknowledge the issue and say that we are working to improve the workflow in the future.