Closed editorialbot closed 2 years ago
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1002/ejsp.2023 is OK
- 10.1093/biomet/64.2.191 is OK
- 10.1177/0146167220913363 is OK
- 10.4324/9780203771587 is OK
- 10.5334/irsp.181 is OK
- 10.5964/meth.2811 is OK
- 10.1111/2041-210X.12504 is OK
- 10.1177/2515245920951503 is OK
MISSING DOIs
- None
INVALID DOIs
- None
:wave: @openjournals/joss-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/3483, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@gasparl - an editor-in-chief will soon review the submission before accepting it for publication. Monitor this thread to see their comments.
@editorialbot accept
Doing it live! Attempting automated processing of paper acceptance...
🐦🐦🐦 👉 Tweet 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...
@mingzehuang, @mmrabe – many thanks for your reviews here and to @fboehm for editing this submission! JOSS relies upon the volunteer effort of people like you and we simply wouldn't be able to do this without you ✨
@gasparl – your paper is now accepted and published in JOSS :zap::rocket::boom:
: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.04643/status.svg)](https://doi.org/10.21105/joss.04643)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04643">
<img src="https://joss.theoj.org/papers/10.21105/joss.04643/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04643/status.svg
:target: https://doi.org/10.21105/joss.04643
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:
Thanks very much @arfon, and once again to @fboehm as well. Always a pleasure to publish with JOSS.
Submitting author: !--author-handle-->@gasparl<!--end-author-handle-- (Gáspár Lukács) Repository: https://github.com/gasparl/possa/ Branch with paper.md (empty if default branch): Version: v0.6.1 Editor: !--editor-->@fboehm<!--end-editor-- Reviewers: @mingzehuang, @mmrabe Archive: 10.5281/zenodo.7027767
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
@mingzehuang & @mmrabe, 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 @fboehm 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 @mmrabe
📝 Checklist for @mingzehuang