You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all,
as I am doing my first Review for JOSS, I am missing a small documentation about Issues that are created in the repository of the reviewed software:
As I understood, a lot of the Review work happens in the Issue tracker of the submitted software. Could you propose something like a 'typical Issue workflow' in the Reviewing for JOSS section of your documentation? Questions that could be answered there:
How to name Issues (maybe a tag in brackets at the beginning: [JOSS Review] You could improve this part of your software)
Who closes an issues? The Reviewer if he / she is happy with the implemented changes?
I think a short guide like this could avoid confusion for both Reviewers and Software Maintainers. And of course it would not be mandatory, but it would be a great orientation.
The text was updated successfully, but these errors were encountered:
Hi all,
as I am doing my first Review for JOSS, I am missing a small documentation about Issues that are created in the repository of the reviewed software:
As I understood, a lot of the Review work happens in the Issue tracker of the submitted software. Could you propose something like a 'typical Issue workflow' in the Reviewing for JOSS section of your documentation? Questions that could be answered there:
[JOSS Review] You could improve this part of your software
)I think a short guide like this could avoid confusion for both Reviewers and Software Maintainers. And of course it would not be mandatory, but it would be a great orientation.
The text was updated successfully, but these errors were encountered: