Closed whedon closed 4 years ago
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @olebole, @zpace it looks like you're currently assigned to review this paper :tada:.
: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.
:star: Important :star:
If you haven't already, you should seriously consider unsubscribing from GitHub notifications for this (https://github.com/openjournals/joss-reviews) repository. As a reviewer, you're probably currently watching this repository which means for GitHub's default behaviour you will receive notifications (emails) for all reviews πΏ
To fix this do the following two things:
For a list of things I can do to help you, just type:
@whedon commands
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
@whedon generate pdf
Reference check summary:
OK DOIs
- 10.1146/annurev-astro-091916-055240 is OK
- 10.3847/1538-4357/aa7d04 is OK
- 10.3847/1538-4357/aa7e2d is OK
- 10.3847/1538-4357/aadd03 is OK
- 10.3847/1538-4357/aa87b4 is OK
- 10.1088/0004-637X/731/1/6 is OK
- 10.1088/0004-637X/791/1/64 is OK
- 10.3847/1538-4357/ab0654 is OK
MISSING DOIs
- None
INVALID DOIs
- None
π @olebole & @zpace - thanks again for agreeing to review!
This is the review thread for the paper. All of our communications will happen here from now on.
Please read the "Reviewer instructions & questions" in the first comment above.
Both reviewers have checklists at the top of this thread (in that first comment) with the JOSS requirements. As you go over the submission, please check any items that you feel have been satisfied. There are also links to the JOSS reviewer guidelines.
The JOSS review is different from most other journals. Our goal is to work with the authors to help them meet our criteria instead of merely passing judgment on the submission. As such, the reviewers are encouraged to submit issues and pull requests on the software repository. When doing so, please mention https://github.com/openjournals/joss-reviews/issues/2581
so that a link is created to this thread (and I can keep an eye on what is happening). Please also feel free to comment and ask questions on this thread. In my experience, it is better to post comments/questions/suggestions as you come across them instead of waiting until you've reviewed the entire package.
We aim for reviews to be completed within about 2-4 weeks. Please let me know if any of you require some more time. We can also use Whedon (our bot) to set automatic reminders if you know you'll be away for a known period of time.
Please feel free to ping me (@danielskatz) if you have any questions/concerns.
@whedon generate pdf
I am now happy with the paper and would recommend to accept it.
Thanks @olebole!
π @zpace - it looks like you are close to finishing as well, other than the references checkbox
Is this correct?
@danielskatz everything looks good to me, as well. The authors have addressed my relatively few suggestions. I recommend accepting this submission.
Thanks @olebole and @zpace - that was remarkably fast and easy
π @biboyd (Brendan Boyd) - At this point could you:
I can then move forward with accepting the submission.
@danielskatz I made a new release and archived on zenodo. Here is the information
Release: v1.0.0
zenodo archive: https://zenodo.org/record/4002068#.X0aJKxl7lhE
DOI: 10.5281/zenodo.4002067
@whedon set v1.0.0 as version
OK. v1.0.0 is the version.
@whedon set 10.5281/zenodo.4002067 as archive
OK. 10.5281/zenodo.4002067 is the archive.
@whedon check references
Reference check summary:
OK DOIs
- 10.1146/annurev-astro-091916-055240 is OK
- 10.3847/1538-4357/aa7d04 is OK
- 10.1088/0067-0049/192/1/9 is OK
- 10.3847/1538-4357/aa7e2d is OK
- 10.3847/1538-4357/aadd03 is OK
- 10.3847/1538-4357/aa87b4 is OK
- 10.1088/0004-637X/731/1/6 is OK
- 10.1088/0004-637X/791/1/64 is OK
- 10.3847/1538-4357/ab0654 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@whedon generate pdf
I found a few small fixes needed in the paper - https://github.com/biboyd/SALSA/pull/5
Otherwise, this looks ready to go to me
Please let me know when you have merged this, or what you disagree with
@whedon generate pdf
I merged in your small changes. I also reopened one of the reviewers issues https://github.com/biboyd/SALSA/issues/2 because it wasn't properly addressed. I just added a short snippet referencing the yt software in the paper and then edited the annotations accordingly.
@whedon accept
Attempting dry run of processing paper acceptance...
Reference check summary:
OK DOIs
- 10.1146/annurev-astro-091916-055240 is OK
- 10.3847/1538-4357/aa7d04 is OK
- 10.1088/0067-0049/192/1/9 is OK
- 10.3847/1538-4357/aa7e2d is OK
- 10.3847/1538-4357/aadd03 is OK
- 10.3847/1538-4357/aa87b4 is OK
- 10.1088/0004-637X/731/1/6 is OK
- 10.1088/0004-637X/791/1/64 is OK
- 10.3847/1538-4357/ab0654 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/1676
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/1676, 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...
Thanks to @olebole & @zpace for reviewing!
And congratulations to @biboyd (Brendan Boyd) and co-authors!!
: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.02581/status.svg)](https://doi.org/10.21105/joss.02581)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.02581">
<img src="https://joss.theoj.org/papers/10.21105/joss.02581/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.02581/status.svg
:target: https://doi.org/10.21105/joss.02581
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:
π @biboyd - sorry I forgot to ask you this before - is this submission associated with an AAS publication?
@danielskatz No it is not
Thanks - there's a slightly more complicated process that links the two publications together in that case, and it was pointed out to me that we might have missed it - great to know!
Submitting author: @biboyd (Brendan Boyd) Repository: https://github.com/biboyd/SALSA Version: v1.0.0 Editor: @danielskatz Reviewer: @olebole, @zpace Archive: 10.5281/zenodo.4002067
: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
@olebole & @zpace, 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 @danielskatz 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 @olebole
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @zpace
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper