Closed whedon closed 2 years ago
@whedon generate pdf from branch joss-paper
Attempting PDF compilation from custom branch joss-paper. Reticulating splines etc...
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@whedon check references from branch joss-paper
Attempting to check references... from custom branch joss-paper
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.5281/zenodo.3509134 is OK
- 10.25080/Majora-92bf1922-00a is OK
- 10.1038/s41586-020-2649-2 is OK
- 10.1016/j.rser.2018.08.002 is OK
- 10.1016/j.apenergy.2021.116731 is OK
- 10.1016/j.rser.2020.110195 is OK
- 10.1038/sdata.2018.203 is OK
- 10.1016/j.enpol.2013.01.052 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@whedon set 10.5281/zenodo.5989170 as archive
OK. 10.5281/zenodo.5989170 is the archive.
@whedon set v1.1.2 as version
OK. v1.1.2 is the version.
Thanks @nick-gorman. It all looks good and I will now recommend your submission for acceptance.
@whedon recommend-accept
Attempting dry run of processing paper acceptance...
: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/2932
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/2932, then you can now move forward with accepting the submission by compiling again with the flag deposit=true
e.g.
@whedon accept deposit=true
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.5281/zenodo.3509134 is OK
- 10.25080/Majora-92bf1922-00a is OK
- 10.1038/s41586-020-2649-2 is OK
- 10.1016/j.rser.2018.08.002 is OK
- 10.1016/j.apenergy.2021.116731 is OK
- 10.1016/j.rser.2020.110195 is OK
- 10.1038/sdata.2018.203 is OK
- 10.1016/j.enpol.2013.01.052 is OK
MISSING DOIs
- None
INVALID DOIs
- None
Hi @nick-gorman! Items for wrapping up:
Thanks @kthyng
Not sure how that 2 got there, or how I didn't see it. Good tip with the curly brackets.
These issues should be resolved.
@whedon generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@whedon generate pdf from branch joss-paper
Attempting PDF compilation from custom branch joss-paper. Reticulating splines etc...
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@nick-gorman ok everything looks good! But, do you want me to accept this submission from the joss-paper
branch or were you going to merge it first? Either way is fine, I just need to know which.
@kthyng I've just merged joss-paper into master, so should be good to go from master
@whedon generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@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 on your new publication @nick-gorman! Many thanks to editor @timtroendle and reviewers @noah80 and @robinroche for your time, hard work, and expertise!!
: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.03596/status.svg)](https://doi.org/10.21105/joss.03596)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.03596">
<img src="https://joss.theoj.org/papers/10.21105/joss.03596/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.03596/status.svg
:target: https://doi.org/10.21105/joss.03596
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:
Thank you @noah80 @robinroche @timtroendle and @kthyng!
Submitting author: @nick-gorman (Nicholas Gorman) Repository: https://github.com/UNSW-CEEM/nempy Version: v1.1.2 Editor: @timtroendle Reviewer: @noah80, @robinroche Archive: 10.5281/zenodo.5989170
: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
@noah80 & @robinroche, 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 @timtroendle 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 @noah80
✨ 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 @robinroche
✨ 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