Closed whedon closed 3 years ago
Great - yes, everything sounds good! Thank you so much! Hopefully the remaining issue can be resolved. We're very excited and happy about the paper and process.
Best wishes again! Volker
@whedon accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1016/j.cpc.2009.06.022 is OK
- 10.1088/0953-8984/26/36/363202 is OK
- 10.1088/1361-648X/aa680e is OK
- 10.1016/j.commatsci.2010.05.010 is OK
- 10.1186/1758-2946-4-17 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/2018
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/2018, 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
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1016/j.cpc.2009.06.022 is OK
- 10.1088/0953-8984/26/36/363202 is OK
- 10.1088/1361-648X/aa680e is OK
- 10.1016/j.commatsci.2010.05.010 is OK
- 10.1186/1758-2946-4-17 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/2019
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/2019, 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...
@marshallmcdonnell, @jgostick - many thanks for your reviews here and to @jgostick for editing this submission too! JOSS relies upon the volunteer efforts of folks like yourselves and we simply wouldn't be able to do this without you β¨.
@Kokookster - 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.02767/status.svg)](https://doi.org/10.21105/joss.02767)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.02767">
<img src="https://joss.theoj.org/papers/10.21105/joss.02767/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.02767/status.svg
:target: https://doi.org/10.21105/joss.02767
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:
@jgostick, @marshallmcdonnell, @arfon Thanks for this terrific review! It was very helpful for me and the whole project! Not only this review, but all the requirements for submission are an excellent guide for bringing the software project into good shape!
Submitting author: @kokookster (Sebastian Kokott) Repository: https://gitlab.com/gims-developers/gims Version: v1.0.2 Editor: @jgostick Reviewers: @marshallmcdonnell, @jgostick Archive: 10.5281/zenodo.4386436
: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
@marshallmcdonnell & @arose, 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 @jgostick 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 @marshallmcdonnell
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @jgostick
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper