Open editorialbot opened 1 month 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
Software report:
github.com/AlDanial/cloc v 1.90 T=0.09 s (992.8 files/s, 223111.5 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
HTML 27 1778 81 7910
SVG 1 0 0 2671
Python 22 1078 1200 1666
JavaScript 12 138 228 911
CSS 4 190 35 780
Markdown 2 61 0 163
TeX 1 11 0 156
reStructuredText 8 79 163 90
XML 6 0 0 52
YAML 2 6 21 28
DOS Batch 1 8 1 26
make 1 4 7 9
-------------------------------------------------------------------------------
SUM: 87 3353 1736 14462
-------------------------------------------------------------------------------
Commit count by author:
128 Junxiang Wang
12 junwang
6 dependabot[bot]
2 xianggebenben
Paper file info:
š Wordcount for paper.md
is 882
ā
The paper includes a Statement of need
section
License info:
ā
License found: MIT License
(Valid open source OSI approved license)
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
š @xianggebenben, @range-et, @mbeyss, and @rkdan - This is the review thread for the paper. All of our communications will happen here from now on.
Please read the "Reviewer instructions & questions" in the first comment above.
Both reviewers have checklists at the top of this thread (in that first comment) with the JOSS requirements. As you go over the submission, please check any items that you feel have been satisfied. There are also links to the JOSS reviewer guidelines.
The JOSS review is different from most other journals. Our goal is to work with the authors to help them meet our criteria instead of merely passing judgment on the submission. As such, the reviewers are encouraged to submit issues and pull requests on the software repository. When doing so, please mention https://github.com/openjournals/joss-reviews/issues/6796 so that a link is created to this thread (and I can keep an eye on what is happening). Please also feel free to comment and ask questions on this thread. In my experience, it is better to post comments/questions/suggestions as you come across them instead of waiting until you've reviewed the entire package.
We aim for the review process to be completed within about 4-6 weeks but please make a start well ahead of this as JOSS reviews are by their nature iterative and any early feedback you may be able to provide to the author will be very helpful in meeting this schedule.
cc. @majensen
:wave: @majensen - I'm turning this one back over to you to attend to. Let me know if you need anything.
Hello! Nice to meet everyone. I'm out for about the next week for a short holiday but will get back with comments when I get back!
@rkdan @range-et @mbeyss - how are your reviews coming? Please check in when you have a chance. Thanks and apologies @xianggebenben for the long delay.
Hello, @majensen Im down with COVID right now will get back asap
@range-et no problem - main thing is to take care of yourself!
Submitting author: !--author-handle-->@xianggebenben<!--end-author-handle-- (Junxiang Wang) Repository: https://github.com/xianggebenben/GraphSL Branch with paper.md (empty if default branch): Version: v 0.8 Editor: !--editor-->@majensen<!--end-editor-- Reviewers: @range-et, @mbeyss, @rkdan Archive: Pending
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
@range-et & @mbeyss & @rkdan, 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 @majensen 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 @mbeyss
š Checklist for @rkdan