Closed editorialbot closed 1 year ago
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...
Thank you @faroit for serving as our editor, and both reviewers @hayesall @AoifeHughes for your valuable comments and suggestions to make this package better! π€
@xinyiguan congratulations! π₯³ And yes, big thanks for reviewing and editing to @faroit and @hayesall and @AoifeHughes! β€οΈ
: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.04738/status.svg)](https://doi.org/10.21105/joss.04738)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04738">
<img src="https://joss.theoj.org/papers/10.21105/joss.04738/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04738/status.svg
:target: https://doi.org/10.21105/joss.04738
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:
@xinyiguan congratulations to the accepted paper π₯³. I am very happy how this review process turned out. Both in terms of timing, quality of the reviews and the reactions/changes being made.
Thanks to @AoifeHughes @hayesall!
Submitting author: !--author-handle-->@xinyiguan<!--end-author-handle-- (Xinyi Guan) Repository: https://github.com/xinyiguan/py2lispIDyOM Branch with paper.md (empty if default branch): Version: v.1.0.2 Editor: !--editor-->@faroit<!--end-editor-- Reviewers: @AoifeHughes, @hayesall Archive: 10.5281/zenodo.7272236
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
@AoifeHughes & @hayesall, 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 @faroit 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 @hayesall
π Checklist for @AoifeHughes