Closed whedon closed 3 years ago
Great, thanks @arfon. We've released v0.2.4. We had existing automation set up with Zenodo to create DOIs for each new version, but the names don't match the paper title, although the authors are the same. Do we need to create a new version of the DOI for v0.2.4 and edit the title to match the paper title? Or should we create an entirely separate DOI for this paper submission? Here's what we currently have: https://doi.org/10.5281/zenodo.3406400
@jasonnance we can use what you have already.
@whedon set 10.5281/zenodo.3406400 as archive
OK. 10.5281/zenodo.3406400 is the archive.
@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-1-4614-3223-4_6 is OK
- 10.18653/v1/d16-1264 is OK
- 10.18653/v1/p19-1441 is OK
- 10.18653/v1/d19-1670 is OK
- 10.18653/v1/n18-1101 is OK
- 10.18653/v1/d15-1075 is OK
- 10.18653/v1/n18-2072 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/2410
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/2410, 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...
@W4ngatang, @ljvmiranda921, @sisco0 β many thanks for your reviews here and to @bmcfee 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 β¨
@jasonnance β 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.02395/status.svg)](https://doi.org/10.21105/joss.02395)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.02395">
<img src="https://joss.theoj.org/papers/10.21105/joss.02395/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.02395/status.svg
:target: https://doi.org/10.21105/joss.02395
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: @jasonnance (Jason Nance) Repository: https://github.com/RTIInternational/gobbli Version: v0.2.0 Editor: @arfon Reviewers: @w4ngatang, @ljvmiranda921, @sisco0
Archive: 10.5281/zenodo.3406400
: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
@w4ngatang, @ljvmiranda921, & @sisco0, 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 @bmcfee know.
β¨ Please try and complete your review in the next six weeks β¨
Review checklist for @w4ngatang
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @ljvmiranda921
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @sisco0
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper