Closed whedon closed 2 years ago
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @dvysardana, @drj11 it looks like you're currently assigned to review this paper :tada:.
:warning: JOSS reduced service mode :warning:
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
:star: Important :star:
If you haven't already, you should seriously consider unsubscribing from GitHub notifications for this (https://github.com/openjournals/joss-reviews) repository. As a reviewer, you're probably currently watching this repository which means for GitHub's default behaviour you will receive notifications (emails) for all reviews 😿
To fix this do the following two things:
For a list of things I can do to help you, just type:
@whedon commands
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
@whedon generate pdf
Software report (experimental):
github.com/AlDanial/cloc v 1.88 T=0.06 s (1133.7 files/s, 66119.8 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Python 22 586 955 1207
reStructuredText 32 204 252 342
YAML 5 18 1 79
HTML 2 1 0 66
Bourne Shell 1 31 16 62
Markdown 3 26 0 52
DOS Batch 1 8 1 26
CSS 1 2 0 11
make 1 4 7 9
-------------------------------------------------------------------------------
SUM: 68 880 1232 1854
-------------------------------------------------------------------------------
Statistical information for the repository 'ab4397100d0d540f281a770c' was
gathered on 2021/10/28.
The following historical commit information, by author, was found:
Author Commits Insertions Deletions % of changes
Tiago Toledo Junior 30 3619 786 100.00
Below are the number of rows from each author that have survived and are still
intact in the current revision:
Author Rows Stability Age % in comments
Tiago Toledo Junior 2833 78.3 3.3 6.99
PDF failed to compile for issue #3864 with the following error:
Can't find any papers to compile :-(
@osorensen the PDF isn't compiling. Should it be? Is that where i would expect to find the full author list?
Thanks for letting me know @drj11. The paper is in a separate branch, so we need some special syntax.
@whedon generate pdf from branch docs/joss_paper
Attempting PDF compilation from custom branch docs/joss_paper. Reticulating splines etc...
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Good work whedon!
@osorensen, @whedon, I have completed my review.
Thanks @dvysardana. Do I understand correctly that you think a statement of need is missing but otherwise everything is fine?
Hello @osorensen
Yes, I have completed my review. The statement of need needs to be updated to clearly mention the target audience. Further, the paper lacks a description and comparison of other similar packages that already exist in the community.
Can you please confirm that all the review requirements are complete now?
Thanks Divya Sardana
On Sun, Oct 31, 2021 at 12:01 AM Øystein Sørensen @.***> wrote:
Thanks @dvysardana https://github.com/dvysardana. Do I understand correctly that you think a statement of need is missing but otherwise everything is fine?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/3864#issuecomment-955647768, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE6FQXZNUKIWGDXEBZKIQXLUJTSTLANCNFSM5G4K4XNQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Thanks a lot for your review @dvysardana . I can confirm that you have done what is requested for now, but once the authors report in this thread that they have added a statement if need and a target audience, please come back and compete the review checklist. I will tag you in this thread to make sure you get notified.
@whedon generate pdf from branch docs/joss_paper
Attempting PDF compilation from custom branch docs/joss_paper. Reticulating splines etc...
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Hello @dvysardana
I've added more information about the target audience on the README and on the sphinx documentation. Also, I added more information about other packages on the paper.
Do those changes meet the criteria for your revision? If not, do you have any suggestions on how to improve it to make it acceptable?
Thank you for your review!
Hello @tnanukem
Thanks for adding the additional information. These changes look good to me. I have no other suggestions for improvement.
Best Regards Divya Sardana
On Tue, Nov 2, 2021 at 4:50 AM Tiago Toledo Junior @.***> wrote:
Hello @dvysardana https://github.com/dvysardana
I've added more information about the target audience on the README and on the sphinx documentation. Also, I added more information about other packages on the paper.
Do those changes meet the criteria for your revision? If not, do you have any suggestions on how to improve it to make it acceptable?
Thank you for your review!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/3864#issuecomment-957368556, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE6FQX4DTPGPHTF3NHD7WV3UJ7GATANCNFSM5G4K4XNQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Thank you @dvysardana.
If anything else comes up I'm available for the changes proposed by you or @drj11 :)
@dvysardana, please also remember to check the two reminaing boxes in your review checklist at the top of this issue.
@osorensen Checked all the boxes in my review.
On Thu, Nov 4, 2021 at 6:25 AM Øystein Sørensen @.***> wrote:
@dvysardana https://github.com/dvysardana, please also remember to check the two reminaing boxes in your review checklist at the top of this issue.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/3864#issuecomment-960921508, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE6FQX2LSEM4HYBHFYEPWB3UKKCUDANCNFSM5G4K4XNQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
:wave: @drj11, please update us on how your review is going (this is an automated reminder).
Oh good reminder @whedon I'll have a look this afternoon.
@drj11, how is it going with your review? If there are issues which you think the authors should address, please mention them in this thread or by opening an issue in the source repository.
Dear @drj11, could you please update us on how it is going with your review of this submission?
Hello @osorensen and @drj11. If there is anything I can do to make the reviewing process easier, just let me know.
@TNanukem, thanks for reaching out. I'll see if we can find another reviewer, and hopefully we can finish this.
:wave: @imw, would you be willing to review this submission for JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
Yes, happy to do so by this weekend.
Thanks a lot @imw!
@whedon add @imw as reviewer
OK, @imw is now a reviewer
@imw, I have added a review checklist for you at the top of this thread, which you can use for your review. You find the reviewer guidelines here. Please let me know if you need any assistance in the process.
tbh this dropped off my radar. I'm happy to complete the review today (GMT) if you still want, but it looks like you've found another reviewer.
To be honest there is one concrete thing that you can change to improve the process slightly: put the review deadline either at the top, at the bottom, or in any of the nagging comments.
Sorry I dropped the ball on this one.
Thanks for getting back to us @drj11. I've tried to ping you a few times, but I completely understand that it's easy to loose track of e-mails. It would be very much appreciated if you could complete your review, even though we have already secured a third reviewer. Having three reviewers rather than two is a good thing.
And thanks for your comment regarding deadlines. However, this might be slightly problematic to implement, since the reviews in JOSS are supposed to be interactive. Sometimes, when the reviewers have a large number of suggestions, it can take many months for the submitting authors to fix the issues proposed by the reviewers, so it's hard to set deadlines for reviews.
@TNanukem I have opened a few issues, but only two block the review:
https://github.com/TNanukem/scikit-net/issues/35
https://github.com/TNanukem/scikit-net/issues/37
I think that these should be easy to resolve.
In the written paper I particularly appreciated the Statement of Need and the catalogue of implemented algorithms.
Hello @drj11. Thanks for the feedback, I will solve the issues during the weekend
@TNanukem I also opened a couple of issues.: https://github.com/TNanukem/scikit-net/issues/39 https://github.com/TNanukem/scikit-net/issues/40 Also quite minor. Nice library!
@whedon generate pdf from branch docs/joss_paper
Attempting PDF compilation from custom branch docs/joss_paper. Reticulating splines etc...
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Hello @imw and @drj11
Thank you for your review! I think I solved most of the issues.
Only the one related to the warning on the unit tests is still open. Since it will change the expected value of the test, I will tackle it after. However, I think the blocking issues are all solved.
If there is any additional point I will be happy to work on it.
Have a good weekend everyone!
@whedon @osorensen my review is complete and i have no further reasons to delay publication. Thank you to everyone involved!
I'm sorry human, I don't understand that. You can see what commands I support by typing:
@whedon commands
Thank you very much @drj11!
@imw, when you have time, please let us know if the two Issues you opened in the source repository have been properly addressed.
Yes, all addressed well!
@TNanukem, I'll read through the manuscript once more, and get back to you if there are any suggested changes. In the meantime, could you please do the following?
@whedon generate pdf from branch docs/joss_paper
Attempting PDF compilation from custom branch docs/joss_paper. Reticulating splines etc...
Submitting author: @TNanukem (Tiago Toledo Junior) Repository: https://github.com/TNanukem/scikit-net/ Version: v0.0.1 Editor: @osorensen Reviewers: @dvysardana, @drj11, @imw Archive: 10.5281/zenodo.5783027
:warning: JOSS reduced service mode :warning:
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
Status
Status badge code:
Reviewers and authors:
Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the target repository and link to those issues (especially acceptance-blockers) by leaving comments in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)
Reviewer instructions & questions
@dvysardana & @drj11, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @osorensen know.
✨ Please start on your review when you are able, and be sure to complete your review in the next six weeks, at the very latest ✨
Review checklist for @dvysardana
✨ Important: Please do not use the Convert to issue functionality when working through this checklist, instead, please open any new issues associated with your review in the software repository associated with the submission. ✨
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @drj11
✨ Important: Please do not use the Convert to issue functionality when working through this checklist, instead, please open any new issues associated with your review in the software repository associated with the submission. ✨
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @imw
✨ Important: Please do not use the Convert to issue functionality when working through this checklist, instead, please open any new issues associated with your review in the software repository associated with the submission. ✨
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper