-
-
Notifications
You must be signed in to change notification settings - Fork 37
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]: overviewR - Easily Explore Your Data in R #4740
Comments
Hello humans, I'm @editorialbot, a robot that can help you with some common editorial tasks. 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:
|
|
Wordcount for |
|
Hi @drmowinckels, @milenamilena, please see the instructions at the top of the review thread. Once you've generated your checklist you can use this as the basis for your review. |
Review checklist for @drmowinckelsConflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
|
Review checklist for @milenamilenaConflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
|
@editorialbot generate pdf |
@editorialbot check references |
|
@milenamilena @drmowinckels Many thanks for your feedback so far - I highly appreciate your time and energy going into it! I incorporated your suggested changes that we have received so far and updated the PDF. |
I have completed my review, and I found this package very useful and holistic in giving an overview of data. The functions are very clear and well explained. The latex tables were beneficial, as the format is very clear. I also found very interesting the use of the Venn diagram and the ability to customise some gglots. I agree with the comments made by @drmowinckels and am happy to see that they were addressed. It is very promising to see that there are open issues in the repository, mainly for further enhancement. The whole paper is very explanatory, even for a naive R user. |
I have completed my review and am happy with the responses and changes made to the package and paper. The package functionality is well documented and covers something that has no real alternative in the R eco-system as I know it. Its clearly well-thought out and tested, and the implementation is great. @samhforbes I believe both reviewers are happy with the package and paper status. |
@editorialbot generate pdf |
Maybe adding it as a second affiliation for both authors? |
@editorialbot generate pdf |
@editorialbot check references |
|
Thanks @editorialbot |
You are welcome |
Excellent suggestion, thanks @xuanxu. |
@editorialbot set 10.5281/zenodo.7097560 as archive |
Done! Archive is now 10.5281/zenodo.7097560 |
@editorialbot recommend-accept |
|
|
👋 @openjournals/joss-eics, this paper is ready to be accepted and published. Check final proof 👉📄 Download article If the paper PDF and the deposit XML files look good in openjournals/joss-papers#3542, then you can now move forward with accepting the submission by compiling again with the command |
This looks great 🚀 What a wonderful way to (possibly) finish a workday! :) |
Hi @cosimameyer, I just made a PR with a few minor edits to the paper, could you merge that? cosimameyer/overviewR#34 Then I can proceed with accepting the paper. |
Thanks, @kyleniemeyer - it's merged 😊 |
@editorialbot generate pdf |
@editorialbot accept |
|
🐦🐦🐦 👉 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... |
Congratulations @cosimameyer on your article's publication in JOSS! Many thanks to @drmowinckels and @milenamilena for reviewing this, and @samhforbes 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! The 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: @cosimameyer (Cosima Meyer)
Repository: https://github.com/cosimameyer/overviewR
Branch with paper.md (empty if default branch): master
Version: v0.0.12
Editor: @samhforbes
Reviewers: @drmowinckels, @milenamilena
Archive: 10.5281/zenodo.7097560
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
@drmowinckels & @milenamilena, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review.
First of all you need to run this command in a separate comment to create the checklist:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @samhforbes 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 ✨
Checklists
📝 Checklist for @drmowinckels
📝 Checklist for @milenamilena
The text was updated successfully, but these errors were encountered: