-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REVIEW]: statsExpressions: R Package for Tidy Dataframes and Expressions with Statistical Details #3236
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @humanfactors, @tomfaulkenberry it looks like you're currently assigned to review this paper 🎉. 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. ⭐ Important ⭐ 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:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
Failed to discover a |
|
@humanfactors, @tomfaulkenberry: Thanks for agreeing to review. Please carry out your review in this issue by updating the checklist above and giving feedback in this issue. The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. If possible create issues (and cross-reference) in the submission's repository to avoid too specific discussions in this review thread. If you have any questions or concerns please let me know. @IndrajeetPatil Please note the error above "Failed to discover a |
|
@mikldk Thanks, I have renamed the relevant section. I have also added a sentence about how the software differs from |
@whedon generate pdf |
@whedon generate pdf |
@mikldk I am guessing this issue has been unintentionally tagged as |
I noticed that |
|
@humanfactors Thanks for pointing that out! Yes, it was a minor release to fix some issues. The whedon version should be updated, but I don't know how to do it. |
@whedon set v1.0.1 as version |
OK. v1.0.1 is the version. |
Thanks! |
This comment has been minimized.
This comment has been minimized.
@whedon generate pdf |
@mikldk Thanks for providing the checklist.
The doi is Please let me know if you need any other details from my end. :) |
@whedon set 10.5281/zenodo.4773886 as archive |
OK. 10.5281/zenodo.4773886 is the archive. |
@whedon generate pdf |
|
Thanks for pointing out these inconsistencies:
Done! The new title is the same as the paper
Good catch! This was a mistake on my part. Let me know if there is anything else to fix. |
Zenodo: JOSS: |
Oops, sorry, fixed: https://zenodo.org/record/4773886#.YKZT5JMzZQI |
@whedon accept |
|
👋 @openjournals/joss-eics, this paper is ready to be accepted and published. Check final proof 👉 openjournals/joss-papers#2326 If the paper PDF and Crossref deposit XML look good in openjournals/joss-papers#2326, then you can now move forward with accepting the submission by compiling again with the flag
|
|
Thanks everyone for your feedback and one of the smoothest and most helpful reviews processes ever! ❤️ |
@whedon accept deposit=true |
|
🐦🐦🐦 👉 Tweet for this paper 👈 🐦🐦🐦 |
🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨 Here's what you must now do:
Any issues? Notify your editorial technical team... |
Congrats @IndrajeetPatil on your article's publication in JOSS! Many thanks to @humanfactors and @tomfaulkenberry for reviewing this, and @mikldk for editing. |
🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉 If you would like to include a link to your paper from your README use the following code snippets:
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: @IndrajeetPatil (Indrajeet Patil)
Repository: https://github.com/IndrajeetPatil/statsExpressions
Version: v1.0.1
Editor: @mikldk
Reviewer: @humanfactors, @tomfaulkenberry
Archive: 10.5281/zenodo.4773886
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
@humanfactors & @tomfaulkenberry, 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 @mikldk 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 @humanfactors
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @tomfaulkenberry
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
The text was updated successfully, but these errors were encountered: