Closed editorialbot closed 4 months ago
Hello human, 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.06 s (1342.3 files/s, 139110.6 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Python 41 1360 2102 3712
reStructuredText 23 298 394 158
CSV 4 0 0 128
YAML 6 11 9 99
Markdown 2 36 0 72
TeX 1 13 0 41
DOS Batch 1 8 1 26
make 1 4 7 9
JavaScript 2 0 0 7
JSON 1 0 0 3
-------------------------------------------------------------------------------
SUM: 82 1730 2513 4255
-------------------------------------------------------------------------------
Commit count by author:
197 Alexey Izmailov
55 mjachi
32 gdeskos
27 Matthew Meeker
10 Brendan Keith
1 Georgios (Yorgos) Deskos
1 dependabot[bot]
Paper file info:
📄 Wordcount for paper.md
is 883
✅ The paper includes a Statement of need
section
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1063/5.0064394 is OK
- 10.5281/zenodo.7254149 is OK
- 10.1017/S0022112094001886 is OK
MISSING DOIs
- None
INVALID DOIs
- https://doi.org/10.1016/S0266-8920(97)00036-2 is INVALID because of 'https://doi.org/' prefix
License info:
✅ License found: BSD 3-Clause "New" or "Revised" 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:
@alizma - thanks for your submission to JOSS. We're currently managing a large backlog of submissions and the editor most appropriate for your area is already rather busy.
For now, we will need to waitlist this paper and process it as the queue reduces. Thanks for your patience!
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Hi @arfon is there any chance we could get an update regarding the timeline for this review? Thank you!
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@alizma we are working down the backlog steadily, thanks for your patience!
@jbytecode I know this one may be a little out of area of interest a little, but would you mind taking this one on as editor?
@editorialbot invite @jbytecode as editor
Invitation to edit this submission sent!
@crvernon - Though this submission isn't within my expertise area, I could have edited this perhaps (because of DS area), but I currently have too much workload. Hoping to help out in future submissions.
No problem at all @jbytecode! Thanks for the quick notification!
@editorialbot invite @HaoZeke as editor
:wave: @HaoZeke do you have availability to take this one on?
Invitation to edit this submission sent!
Thanks for the ping @crvernon. It isn't directly in my area of expertise but I think I can handle this one :)
@editorialbot assign @HaoZeke as editor
Excellent @HaoZeke! Thanks so much!
Assigned! @HaoZeke is now the editor
👋 @alizma I will facilitate the review of your paper/software as the editor. The first step will be to find reviewers, so I will start contacting potential reviewers over the weekend.
If you have any suggestions for potential reviewers, then please mention them here in this thread (without tagging them with an @). Feel free to use the list of volunteers here or the authors of the similar papers.
hi @ashwinvis @dl11g11 👋 would you be interested in and available to review this JOSS submission? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
If not, could you recommend any potential reviewers?
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Hi @HaoZeke, thank you for being our editor!
We'd like to suggest @msandre and @philbucher as potential reviewers. We also reached out to others, we'll let you know if they would be interested.
hi @msandre @philbucher 👋 would you be interested in and available to review this JOSS submission? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
If not, could you recommend any potential reviewers?
Hi, Thanks for the offer. Unfortunately this seems very far from my personal field of expertise, so I cannot do it. I think the group of Thorsten Lutz at the IAG of the university of Stuttgart could be a good fit. To my knowledge they are not using GitHub, so you would have to reach out via email
@HaoZeke thanks for the invite. It looks like a novel and interesting work. Unfortunately I am occupied with some work related commitments for the coming months.
I can suggest @paroomk and @lguas who should have the expertise to review this.
hi @parmook, @lguas and @p-costa 👋 would you be interested in and available to review this JOSS submission? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
If not, could you recommend any potential reviewers?
P.S. Thanks @ashwinvis and @philbucher for the prompt response and potential reviewers.
Hi @HaoZeke, thanks for the invitation. Unfortunately I have too much on my plate right now, so I won't be able to review it.
@HaoZeke You have a typo in your mention it should be @paroomk
.
hi @paroomk 👋 would you be interested in and available to review this JOSS submission? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
If not, could you recommend any potential reviewers?
P.S. Thanks @ashwinvis for catching the typo.
Hi @HaoZeke, sure. Happy to do it!
On Wed, May 1, 2024 at 6:00 AM Rohit Goswami @.***> wrote:
hi @paroomk https://github.com/paroomk 👋 would you be interested in and available to review this JOSS submission? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
If not, could you recommend any potential reviewers?
P.S. Thanks @ashwinvis https://github.com/ashwinvis for catching the typo.
— Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/6506#issuecomment-2088290873, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC5RYZ7D7KL7BC4LX5ENU6LZADDLRAVCNFSM6AAAAABE5BMLHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBYGI4TAOBXGM . You are receiving this because you were mentioned.Message ID: @.***>
@editorialbot add @paroomk as reviewer
@paroomk thanks for the prompt response, once we have one more reviewer I will start the review thread :)
@paroomk added to the reviewers list!
Hi, we'd also like to suggest jaimeliew1 as a potential reviewer who has done similar work.
hi @jaimeliew1 👋 would you be interested in and available to review this JOSS submission? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
If not, could you recommend any potential reviewers?
:wave: @HaoZeke - could you staring pinging a more reviewers to see if we can get this one in review? It looks like you only need one more to get it going. Thanks!
hi @olivecha, @atismer 👋 would you be interested in and available to review this JOSS submission? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
If not, could you recommend any potential reviewers?
@HaoZeke - thank you for keeping me in mind for the review. But, I'm sorry, I don't have time to review your collaboration in time.
hi @bhajay, @antviro 👋 would you be interested in and available to review this JOSS submission? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
If not, could you recommend any potential reviewers?
Hi,
I would be available to review this.
On Jun 3, 2024, at 5:09 PM, Rohit Goswami @.***> wrote:
hi @bhajay https://github.com/bhajay, @antviro https://github.com/antviro 👋 would you be interested in and available to review this JOSS submission? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html https://joss.readthedocs.io/en/latest/review_criteria.html If not, could you recommend any potential reviewers?
— Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/6506#issuecomment-2146127659, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASX4ZJM7TIQCLEFEERJPPSDZFTLQLAVCNFSM6AAAAABE5BMLHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBWGEZDONRVHE. You are receiving this because you were mentioned.
@editorialbot add @olivecha as reviewer
Thanks for accepting
@olivecha added to the reviewers list!
@editorialbot start review
OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/6838.
hi @bhajay, @antviro 👋 would you be interested in and available to review this JOSS submission? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
If not, could you recommend any potential reviewers?
I see there are already two assigned reviewers, perhaps I am not needed anymore... But otherwise i can review it.
Submitting author: !--author-handle-->@alizma<!--end-author-handle-- (Alexey Izmailov) Repository: https://github.com/METHODS-Group/DRDMannTurb Branch with paper.md (empty if default branch): main Version: v1.0.0 Editor: !--editor-->@HaoZeke<!--end-editor-- Reviewers: @paroomk, @olivecha Managing EiC: Arfon Smith
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @alizma. Currently, there isn't a JOSS editor assigned to your paper.
@alizma if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.
Editor instructions
The JOSS submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type: