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.03 s (1189.8 files/s, 155400.9 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Python 16 951 579 1875
Markdown 10 249 0 459
TeX 1 25 0 185
YAML 6 40 44 172
TOML 1 7 4 57
DOS Batch 1 8 1 26
make 1 4 7 9
-------------------------------------------------------------------------------
SUM: 36 1284 635 2783
-------------------------------------------------------------------------------
Commit count by author:
120 JeanMainguy
79 Jean Mainguy
Paper file info:
📄 Wordcount for paper.md
is 850
✅ The paper includes a Statement of need
section
License info:
✅ License found: MIT License
(Valid open source OSI approved license)
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1038/s41586-019-1058-x is OK
- 10.1038/s42003-021-02112-2 is OK
- 10.7717/peerj.7359 is OK
- 10.1038/nmeth.3103 is OK
- 10.1038/s41587-020-00777-4 is OK
- 10.1038/s41564-018-0171-1 is OK
- 10.1093/bioinformatics/btac694 is OK
- 10.1186/s40168-018-0541-1 is OK
- 10.1038/s41592-022-01431-4 is OK
- 10.1101/gr.186072.114 is OK
- 10.1038/s41592-023-01940-w is OK
- 10.1038/nmeth.3176 is OK
- 10.21105/joss.04296 is OK
- 10.1186/1471-2105-11-119 is OK
- 10.1038/s41592-018-0046-7 is OK
- 10.1038/s41592-018-0046-7 is OK
MISSING DOIs
- No DOI given, and none found for title: MetagWGS, a complete workflow to analyse metagenom...
INVALID DOIs
- None
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@lskatz, @beardymcjohnface – 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. Please create your checklist typing:
@editorialbot generate my checklist
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/6782
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.
Some general comments on the paper
Any questions/concerns please let @arfon know.
@arfon does JOSS allow for in preparation citations?
@arfon does JOSS allow for in preparation citations?
I think that's fine.
Submitting author: !--author-handle-->@JeanMainguy<!--end-author-handle-- (Jean Mainguy) Repository: https://github.com/genotoul-bioinfo/Binette Branch with paper.md (empty if default branch): Version: v1.0.0 Editor: !--editor-->@arfon<!--end-editor-- Reviewers: @lskatz, @beardymcjohnface 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
@lskatz & @beardymcjohnface, 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 @arfon 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 @lskatz
📝 Checklist for @beardymcjohnface