Closed whedon closed 2 years ago
@Kevin-Mattheus-Moerman Note, I merged the JOSS branch into master and the paper needs to be compiled from master.
@whedon set v0.1.0 as version
OK. v0.1.0 is the version.
@whedon set 10.6084/m9.figshare.16688695.v1 as archive
OK. 10.6084/m9.figshare.16688695.v1 is the archive.
@Kevin-Mattheus-Moerman I think I am done with the tasks.
@whedon accept
To recommend a paper to be accepted use @whedon recommend-accept
@whedon recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1137/17m1112236 is OK
- 10.1002/nme.2579 is OK
- 10.1016/j.cma.2019.03.024 is OK
- 10.1007/s42102-019-00010-0 is OK
- 10.1007/s10659-018-9672-7 is OK
- 10.1007/s10704-020-00480-0 is OK
- 10.2172/1226115 is OK
- 10.1016/j.cpc.2008.06.011 is OK
- 10.1016/j.ijimpeng.2016.09.003 is OK
- 10.1016/j.camwa.2017.06.045 is OK
- 10.18419/opus-2879 is OK
- 10.1007/978-3-319-06898-5_5 is OK
- 10.1007/s10659-007-9125-1 is OK
- 10.1007/s10659-013-9463-0 is OK
- 10.1007/s10659-015-9564-z is OK
- 10.1016/j.compstruc.2004.11.026 is OK
- 10.1007/978-3-319-22977-5_33-1 is OK
- 10.21105/joss.02352 is OK
- 10.1109/hpcsim.2012.6266939 is OK
- 10.1007/s42102-018-0004-x is OK
- 10.1007/s42452-020-03784-x is OK
- 10.6084/m9.figshare.12320726.v1 is OK
- 10.31224/osf.io/gty2b 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/2628
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/2628, 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 @diehlpk on getting this work published in JOSS!
@vijaysm, @chennachaos thank you so much for your hard work and dedication here! This was a longer process than usual but you stuck with it and helped us throughout and did a great job providing detailed and valuable feedback so again, thank you indeed!!
: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.03020/status.svg)](https://doi.org/10.21105/joss.03020)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.03020">
<img src="https://joss.theoj.org/papers/10.21105/joss.03020/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.03020/status.svg
:target: https://doi.org/10.21105/joss.03020
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: @diehlpk (Patrick Diehl) Repository: https://github.com/nonlocalmodels/NLMech Version: v0.1.0 Editor: @Kevin-Mattheus-Moerman Reviewer: @vijaysm, @chennachaos Archive: 10.6084/m9.figshare.16688695.v1
: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
@vijaysm & @chennachaos, 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 @Kevin-Mattheus-Moerman 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 @vijaysm
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @chennachaos
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper