Closed whedon closed 2 years ago
Great, ty @WildfireXIII !
At this point could you:
I can then move forward with accepting the submission. I don't think your DOEcode entry counts as an "archival deposit" in our sense of the word since it just points to the GH repo in general, not a specific tagged commit in the repo.
Release tag: v1.0.0 Zenodo DOI: 10.5281/zenodo.5796089
@whedon set 10.5281/zenodo.5796089 as archive
OK. 10.5281/zenodo.5796089 is the archive.
@whedon set v1.0.0 as version
OK. v1.0.0 is the version.
@whedon recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.18653/v1/2020.emnlp-demos.15 is OK
- 10.21105/joss.00861 is OK
- 10.18653/v1/P19-3007 is OK
- 10.1145/3366424.3383542 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/2841
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/2841, 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...
@assenmacher-mat, @deniederhut – many thanks for your reviews here and to @fabian-s for editing this submission! JOSS relies upon the volunteer effort of people like you and we simply wouldn't be able to do this without you ✨
@WildfireXIII – your paper is now accepted and published in JOSS :zap::rocket::boom:
: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.03652/status.svg)](https://doi.org/10.21105/joss.03652)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.03652">
<img src="https://joss.theoj.org/papers/10.21105/joss.03652/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.03652/status.svg
:target: https://doi.org/10.21105/joss.03652
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 everyone!
🎉 congratulations!
Submitting author: @WildfireXIII (Nathan Martindale) Repository: https://github.com/ORNL/tx2 Version: v1.0.0 Editor: @fabian-s Reviewers: @assenmacher-mat, @deniederhut Archive: 10.5281/zenodo.5796089
: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
@assenmacher-mat & @sara-02, 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 @fabian-s 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 @assenmacher-mat
✨ 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 @deniederhut
✨ 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