Closed whedon closed 3 years ago
@whedon set version as 1.0
I'm sorry human, I don't understand that. You can see what commands I support by typing:
@whedon commands
@whedon set 1.0 as version
OK. 1.0 is the version.
@whedon set 10.5281/zenodo.5552605 as archive
OK. 10.5281/zenodo.5552605 is the archive.
@whedon recommend accept
I'm sorry human, I don't understand that. You can see what commands I support by typing:
@whedon commands
@whedon recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1038/sdata.2018.205 is OK
- 10.2307/2333730 is OK
- 10.1126/science.283.5406.1310 is OK
- 10.32942/osf.io/e3xnr is OK
- 10.1093/sysbio/syr029 is OK
- 10.1093/molbev/msw046 is OK
- 10.1126/science.1219669 is OK
- 10.16993/baj.h is OK
- 10.1093/bioinformatics/btu181 is OK
- 10.1093/bioinformatics/bty633 is OK
- 10.1371/journal.pone.0180908 is OK
- 10.1371/journal.pcbi.1006650 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/2648
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/2648, then you can now move forward with accepting the submission by compiling again with the flag deposit=true
e.g.
@whedon accept deposit=true
Hi @tresoldi! I am just doing some final checks before accepting. I noticed some very minor issues in the paper, could you fix these and let me know in here?
@whedon generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Hi @kyleniemeyer ! Thanks for catching those, they are now fixed.
@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...
Great! Thank you everybody! :smiley:
It seems I can't close the issue, I guess there is one last thing I need to bother you, @majensen
@tresoldi I am waiting for the PDF to show up before closing the issue.
... which it looks like is now working!
: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.03173/status.svg)](https://doi.org/10.21105/joss.03173)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.03173">
<img src="https://joss.theoj.org/papers/10.21105/joss.03173/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.03173/status.svg
:target: https://doi.org/10.21105/joss.03173
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:
@tresoldi congratulations! Thanks very much to @DavidNickle and @rvosa for your reviews.
Thanks again for all the support, @majensen , and @DavidNickle and @rvosa for the review work. :)
Submitting author: @tresoldi (Tiago Tresoldi) Repository: https://github.com/tresoldi/ngesh Version: 1.0 Editor: @majensen Reviewer: @DavidNickle, @rvosa Archive: 10.5281/zenodo.5552605
: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
@DavidNickle & @rvosa, 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 @majensen 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 @DavidNickle
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @rvosa
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper