Closed whedon closed 3 years ago
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1007/BF02464423 is OK
- 10.1021/j100540a008 is OK
- 10.1186/1471-2334-11-37 is OK
- 10.18637/jss.v084.i08 is OK
- 10.6084/m9.figshare.1164194 is OK
- 10.21105/joss.01731 is OK
- 10.1016/j.physrep.2020.07.005 is OK
- 10.1016/j.cpc.2019.02.008 is OK
- 10.7717/peerj-cs.103 is OK
- 10.1038/s41592-019-0686-2 is OK
- 10.18452/20950 is OK
- 10.1016/j.jtbi.2011.07.015 is OK
- 10.21105/joss.00565 is OK
- 10.1007/978-3-319-50806-1 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: https://github.com/openjournals/joss-papers/pull/2182
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/2182, then you can now move forward with accepting the submission by compiling again with the flag deposit=true
e.g.
@whedon accept deposit=true
@whedon accept deposit=true
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:
Party like you just published a paper! πππ¦ππ»π€
Any issues? Notify your editorial technical team...
Congratulations to @benmaier (Benjamin F. Maier)!!
And thanks to @chrisvoncsefalvay, @esteinig for reviewing, and @fboehm 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.03097/status.svg)](https://doi.org/10.21105/joss.03097)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.03097">
<img src="https://joss.theoj.org/papers/10.21105/joss.03097/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.03097/status.svg
:target: https://doi.org/10.21105/joss.03097
This is how it will look in your documentation:
We need your help!
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: @benmaier (Benjamin F. Maier) Repository: https://github.com/benmaier/epipack Version: v0.1.2 Editor: @fboehm Reviewer: @chrisvoncsefalvay, @esteinig Archive: 10.5281/zenodo.4655616
:warning: JOSS reduced service mode :warning:
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
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
@chrisvoncsefalvay & @esteinig, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:
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 β¨
Review checklist for @chrisvoncsefalvay
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @esteinig
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper