Closed editorialbot closed 1 year ago
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@kungfugo looks good, thank you!
@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 @kungfugo on your article's publication in JOSS!
Many thanks to @meandmytram and @Roger-luo for reviewing this submission, and @jarvist for editing.
: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.04924/status.svg)](https://doi.org/10.21105/joss.04924)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04924">
<img src="https://joss.theoj.org/papers/10.21105/joss.04924/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04924/status.svg
:target: https://doi.org/10.21105/joss.04924
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:
(I'm going to reopen because it looks like the PDF is not yet appearingβI saw there were some systemic issues with GitHub Actions earlier.)
(I'm going to reopen because it looks like the PDF is not yet appearingβI saw there were some systemic issues with GitHub Actions earlier.)
Should be fixed now!
: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.04924/status.svg)](https://doi.org/10.21105/joss.04924)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04924">
<img src="https://joss.theoj.org/papers/10.21105/joss.04924/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04924/status.svg
:target: https://doi.org/10.21105/joss.04924
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-->@kungfugo<!--end-author-handle-- (Christopher Popp) Repository: https://github.com/kungfugo/BellDiagonalQudits.jl Branch with paper.md (empty if default branch): Version: v0.1.5 Editor: !--editor-->@jarvist<!--end-editor-- Reviewers: @meandmytram, @Roger-luo Archive: 10.5281/zenodo.7575767
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
@meandmytram & @Roger-luo, 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 @jarvist 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 @Roger-luo
π Checklist for @meandmytram