Closed whedon closed 2 years ago
great, thanks @oyvinht and @khinsen !
@whedon recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1007/978-3-642-17685-2_8 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/2887
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/2887, 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 @lungsi (B. Lungsi Sharma)!!
And thanks to @oyvinht and @khinsen for reviewing, and to @mjsottile for editing! We couldn't do this without all your efforts!
: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.03735/status.svg)](https://doi.org/10.21105/joss.03735)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.03735">
<img src="https://joss.theoj.org/papers/10.21105/joss.03735/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.03735/status.svg
:target: https://doi.org/10.21105/joss.03735
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:
Thank you very much (reviewers: @oyvinht and @khinsen, and editors: @mjsottile and @danielskatz).
Comments by @oyvinht and @khinsen were very helpful, I learned some new stuffs. I really appreciated the generous comments from @khinsen, it was very encouraging. I would also like to point out that @mjsottile 's feedback greatly improved the manuscript.
Overall, my experience with JOSS has been highly rewarding (regardless of the paper being accepted, although this helps :) ).
Submitting author: @lungsi (B. Lungsi Sharma) Repository: https://github.com/neuralgraphs/diman Version: v1.1.0 Editor: @mjsottile Reviewers: @oyvinht, @khinsen Archive: 10.5281/zenodo.5837630
: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
@oyvinht & @khinsen, 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 @mjsottile 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 @oyvinht
✨ Important: Please do not use the Convert to issue functionality when working through this checklist, instead, please open any new issues associated with your review in the software repository associated with the submission. ✨
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @khinsen
✨ Important: Please do not use the Convert to issue functionality when working through this checklist, instead, please open any new issues associated with your review in the software repository associated with the submission. ✨
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper