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 (1721.6 files/s, 282165.8 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
R 25 988 1408 2647
C++ 4 319 354 664
Markdown 8 126 0 540
C/C++ Header 7 186 130 442
Rmd 5 284 336 404
TeX 1 4 0 162
YAML 4 33 12 120
SVG 1 0 0 18
C 1 0 0 1
-------------------------------------------------------------------------------
SUM: 56 1940 2240 4998
-------------------------------------------------------------------------------
Commit count by author:
437 Tommy Jones
9 Tommy
3 Brendan Knapp
Paper file info:
π Wordcount for paper.md
is 1518
β
The paper includes a Statement of need
section
License info:
π‘ License found: Other
(Check here for OSI approval)
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.21105/joss.01686 is OK
- 10.18637/jss.v091.i02 is OK
- 10.18637/jss.v083.b01 is OK
- 10.21105/joss.00774 is OK
- 10.21105/joss.00037 is OK
MISSING DOIs
- No DOI given, and none found for title: text2vec
- No DOI given, and none found for title: textmineR: Functions for Text Mining and Topic Mod...
- No DOI given, and none found for title: lda
- No DOI given, and none found for title: broom: An R Package for Converting Statistical Ana...
- No DOI given, and none found for title: R: A Language and Environment for Statistical Comp...
- No DOI given, and none found for title: topicmodels: An R Package for Fitting Topic Model...
- No DOI given, and none found for title: Software Framework for Topic Modelling with Large ...
- No DOI given, and none found for title: Text Mining Infrastructure in R
- No DOI given, and none found for title: MALLET: A Machine Learning for Language Toolkit
- 10.1002/wics.1212 may be a valid DOI for title: The Comprehensive R Archive Network
- No DOI given, and none found for title: Latent Dirichlet Allocation
- No DOI given, and none found for title: Latent Dirichlet Allocation for Natural Language S...
- No DOI given, and none found for title: Conventions for R Modeling Packages
- No DOI given, and none found for title: Tidy data
- No DOI given, and none found for title: Tidymodels
INVALID DOIs
- None
@TommyJones, @maximelenormand, @hassaniazi, 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.
For @maximelenormand, @hassaniazi - 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.
As you are probably already aware, 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/6800 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.
Thanks in advance and let me know if you have any questions!!
Hi @maximelenormand, @hassaniazi- Just wanted to check in briefly. How's the review going thus far? Do let me know if you need anything from my side with respect to the same.
Thanks for reviewing this manuscript again!
Hi @kanishkan91, everything is going well. I have opened two issues regarding the general checks and documentation. One of them is already closed. I will go more in-depth into the review of functionalities, documentation, and the paper by the end of the month.
Hi @kanishkan91, I've finished my review.
@hassaniazi and @maximelenormand Thanks so much for review comments thus far!
Submitting author: !--author-handle-->@tommyjones<!--end-author-handle-- (Tommy Jones) Repository: https://github.com/TommyJones/tidylda Branch with paper.md (empty if default branch): main Version: v0.0.5 Editor: !--editor-->@kanishkan91<!--end-editor-- Reviewers: @maximelenormand, @hassaniazi 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
@maximelenormand & @hassaniazi, 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 @kanishkan91 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 @maximelenormand
π Checklist for @hassaniazi