Closed editorialbot closed 1 year ago
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
:wave: @openjournals/bcm-eics, this paper is ready to be accepted and published.
Check final proof :point_right::page_facing_up: Download article
If the paper PDF and the deposit XML files look good in https://github.com/openjournals/joss-papers/pull/3773, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.32932/pjnh.2020.07.070 is OK
- 10.1053/j.ajkd.2005.07.031 is OK
- 10.1097/TP.0000000000001326 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@balima78 I am the AEiC for this track and here to help process this work for acceptance. There are some issues below which need to be addressed first:
@Kevin-Mattheus-Moerman , done and done! thank you for your attention
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@editorialbot accept
Doing it live! Attempting automated processing of paper acceptance...
π¦π¦π¦ π Tweet for this paper π π¦π¦π¦
πππ π Toot for this paper π πππ
π¨π¨π¨ THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! π¨π¨π¨
Here's what you must now do:
Any issues? Notify your editorial technical team...
Congratulations @balima78 on your publication in JOSS!
Thanks @crvernon for editing this work, and special thanks to the reviewers: @turgeonmaxime and @aj2duncan!!!
:tada::tada::tada: Congratulations on your paper acceptance! :tada::tada::tada:
If you would like to include a link to your paper from your README use the following code snippets:
Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.04807/status.svg)](https://doi.org/10.21105/joss.04807)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04807">
<img src="https://joss.theoj.org/papers/10.21105/joss.04807/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04807/status.svg
:target: https://doi.org/10.21105/joss.04807
This is how it will look in your documentation:
We need your help!
The Journal of Open Source Software is a community-run journal and relies upon volunteer effort. If you'd like to support us please consider doing either one (or both) of the the following:
Submitting author: !--author-handle-->@balima78<!--end-author-handle-- (Bruno A Lima) Repository: https://github.com/txopen/histoc Branch with paper.md (empty if default branch): Version: v0.2.1 Editor: !--editor-->@crvernon<!--end-editor-- Reviewers: @turgeonmaxime, @aj2duncan Archive: 10.5281/zenodo.7338242
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
@turgeonmaxime & @aj2duncan, 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 @crvernon 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 @turgeonmaxime
π Checklist for @aj2duncan