Closed whedon closed 4 years 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:
Party like you just published a paper! ššš¦šš»š¤
Any issues? notify your editorial technical team...
Thanks to @xwang862 & @malramsay64 for reviewing, and @dfm for editing!
And congratulations to @hema-ted and co-authors!
: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.02160/status.svg)](https://doi.org/10.21105/joss.02160)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.02160">
<img src="https://joss.theoj.org/papers/10.21105/joss.02160/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.02160/status.svg
:target: https://doi.org/10.21105/joss.02160
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:
Thanks all of you for your great help!
Submitting author: @hema-ted (He Ma) Repository: https://github.com/hema-ted/pyzfs Version: v1.3 Editor: @dfm Reviewer: @xwang862, @malramsay64 Archive: 10.5281/zenodo.3728346
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
@xwang862 & @malramsay64, 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 @dfm know.
āØ Please try and complete your review in the next two weeks āØ
Review checklist for @xwang862
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @malramsay64
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper