Closed editorialbot closed 1 year ago
Hello humans, I'm @editorialbot, a robot that can help you with some common editorial tasks.
For a list of things I can do to help you, just type:
@editorialbot commands
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
@editorialbot generate pdf
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1175/JPO-D-17-0100.1 is OK
- 10.1007/s13137-019-0123-9 is OK
MISSING DOIs
- None
INVALID DOIs
- None
Software report:
github.com/AlDanial/cloc v 1.88 T=1.39 s (185.9 files/s, 291013.4 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
C++ 174 39318 96505 204359
C/C++ Header 23 9112 29337 20386
Python 28 655 303 1680
Markdown 17 409 0 1136
make 6 106 103 230
Bourne Shell 8 46 76 130
TeX 1 3 0 25
YAML 1 1 4 18
-------------------------------------------------------------------------------
SUM: 258 49650 126328 227964
-------------------------------------------------------------------------------
gitinspector failed to run statistical information for the repository
Wordcount for paper.md
is 363
@NoraLoose, @kris-rowe Here is the review issue! Please read through the instructions above for how to proceed with the review, and don't hesitate to reach out with any questions as they arise. Thank you!
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
/ooo April 15 until July 15
@bastorer I am going to be on leave for a few months, but never fear β another editor will take over here.
While @kthyng is ooo (or ideally until we finish this review), I'll take over as editor.
It looks like everything is started:
@editorialbot generate my checklist
) and then get startedIf you have any questions, please let me know!
@editorialbot assign me as editor
Assigned! @danielskatz is now the editor
Hi @danielskatz, thanks for the ping - I have started the review. I will go on vacation for 2 weeks, but finishing up this review is my number 1 priority when I'm back (the week of May 2). Sorry for the delay and thanks for understanding!
π @kris-rowe - A couple of weeks in, I just wanted to check on how your review is coming.
@bastorer - have you been able to make any progress on any of the issues @NoraLoose created before her vacation?
π @kris-rowe - A couple of weeks in, I just wanted to check on how your review is coming.
The last couple of weeks have been hectic, so this has slipped a bit. I will aim to get most of my review completed by the end of the week to keep the process moving along.
π @bastorer (repeating) - have you been able to make any progress on any of the issues @NoraLoose created before her vacation?
π @bastorer - note in particular that https://github.com/husseinaluie/FlowSieve/issues/5 is a showstopper here. The license you have chosen is
JOSS cannot publish papers about software that does not have an OSI-approved license.
π @bastorer - Please let us know your status.
I'll also try to email you, but without you as the author responding to comments and issues, we can't make progress and may need to close this submission.
Hi @danielskatz
Sorry about the slow response. I'll work through the issues Nora's created tomorrow, including the license (thanks for pointing that out!).
π @bastorer - any updates?
π @bastorer - we really do need to make progress on this
@danielskatz Should I continue to work on my review for this, or should I wait for the license issue to be resolved?
It's hard to say, given the lack of response from @bastorer over the last 5 weeks - I would have liked a response saying that this wouldn't be a problem and could be changed, or that it is a problem and that the submission needs to be withdrawn. I now wonder if we will need to reject this submission if we don't hear back soon.
I'm sorry I can't be more clear.
π @bastorer - I plan to reject this submission in 2 weeks if I don't hear anything from you.
Hi @danielskatz
I'm very sorry about the slow responses. It also looks like my in-line email responses didn't show up like I thought they would, but I was also very slow to respond.
I've submitted commits addressing the issues posted on the FlowSieve repository, including changing the license to one on the OSI-approved list.
@bastorer - thanks. Perhaps you can add some comments in the issues that you think are now resolved, and the creators of those issues can then potentially close them and continue their reviews
@NoraLoose & @kris-rowe - I hope we can now continue your reviews.
@NoraLoose & @kris-rowe - I've been on vacation the last 2 weeks and now want to check in with you again on this. Can you update me on any more you can do on your reviews?
@danielskatz I need to get caught up on my review. Will push on this today/tomorrow now that the license issue has been resolved.
@danielskatz I can make some progress on this review within the next 2 weeks.
Thanks @NoraLoose & @kris-rowe
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@danielskatz I need to get caught up on my review. Will push on this today/tomorrow now that the license issue has been resolved.
@kris-rowe - do you have an update?
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@kris-rowe - do you have an update?
Everyone - as @kthyng has returned from her leave, I'm going to give this submission back to her as editor again
@editorialbot assign @kthyng as editor
Assigned! @kthyng is now the editor
Hello! I have just looked through the page, looks like we are a bit stuck. What can we do to keep moving forward?
@kris-rowe Looks like you need to pick up your review now that the license situation has been worked out.
@NoraLoose I see you've opened some issuesΒ β they all look like the author has responded, so please check that out and see if the issues still need to be open. And otherwise can you carry on with your review?
@bastorer What is the status on your end? Are you waiting for reviews or are you still working on anything?
Thanks all.
Hello all,
Sorry about the slow responses. Commits have been submitted responding to the issues posted on the github page, except for the paper changes, which I will have by early next week.
Regards Ben
On Wed, Jun 29, 2022, 23:30 Daniel S. Katz @.***> wrote:
It's hard to say, given the lack of response from @bastorer https://github.com/bastorer over the last 5 weeks - I would have liked a response saying that this wouldn't be a problem and could be changed, or that it is a problem and that the submission needs to be withdrawn. I now wonder if we will need to reject this submission if we don't hear back soon.
I'm sorry I can't be more clear.
β Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/4277#issuecomment-1170710125, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB7LPK5JG4D65C64W2NBJE3VRUIDPANCNFSM5R324ODA . You are receiving this because you were mentioned.Message ID: @.***>
Thanks for the ping @kthyng! I will carry on with my review next week (probably Friday).
Hi @kthyng thanks for the reminders! I think I've responded to all of the open issues.
Thanks @NoraLoose and @bastorer!
@kris-rowe Will you be able to complete your review in the next week or two? Totally understandable if not β just let me know either way so we know plans or I can recruit a new reviewer if needed.
@kthyng I will finish the review this week so there aren't any further delays.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Submitting author: !--author-handle-->@bastorer<!--end-author-handle-- (Benjamin Storer) Repository: https://github.com/husseinaluie/FlowSieve Branch with paper.md (empty if default branch): Version: v3.3.0 Editor: !--editor-->@kthyng<!--end-editor-- Reviewers: @NoraLoose, @ashwinvis Archive: 10.5281/zenodo.7818192
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
@NoraLoose & @kris-rowe, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review. First of all you need to run this command in a separate comment to create the checklist:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @kthyng 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 β¨
Checklists
π Checklist for @NoraLoose
π Checklist for @ashwinvis