-
-
Notifications
You must be signed in to change notification settings - Fork 36
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]: polyCub: An R package for Integration over Polygons #1056
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @wrathematics it looks like you're currently assigned as the reviewer for this paper 🎉. ⭐ 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:
|
|
Sorry this took me so long. I think everything basically looks good. A few very minor comments:
As far as the JOSS review is concerned, I don't consider any of these issues blockers. |
Thanks very much @wrathematics! |
Thanks a lot for the review, @wrathematics! (BTW: I wouldn't judge two weeks as a long review period.) |
👋 @bastistician — We haven't heard from you in a while. What's your status? Are you able to work on this revision soon? |
Thanks for asking. I had this on my todo list for a while... and have now started to implement the above suggestions. Sorry for the delay! |
@whedon generate pdf |
|
I have
@wrathematics : May I include your name as a reviewer in the package DESCRIPTION (with role="rev")? @karthik : How do we proceed? Is there an intended release schedule at JOSS? I would like the package to be cited using this JOSS publication, so I have included a reference in the package CITATION file. However, the DOI will only be registered later, and the volume and issue number are probably not yet fixed (or can I assume "4(33)" as indicated in the footnote of the current proof?). Should I release the package on CRAN prior to or after JOSS acceptance and archiving on Zenodo? |
@whedon generate pdf |
|
@whedon commands |
@whedon check references |
|
|
@bastistician Can you please deposit the latest version of your package on Zenodo and share the DOI with me here? 🙏 |
@karthik Today, I have released the package on CRAN (version 0.7.1) and created a corresponding GitHub release, which has subsequently been pushed to Zenodo. Here is the DOI: |
@whedon set zenodo.2559486 as archive |
zenodo.2559486 doesn't look like an archive DOI. |
@whedon set 10.5281/zenodo.2559486 as archive |
OK. 10.5281/zenodo.2559486 is the archive. |
@whedon accept |
|
|
Check final proof 👉 openjournals/joss-papers#478 If the paper PDF and Crossref deposit XML look good in openjournals/joss-papers#478, then you can now move forward with accepting the submission by compiling again with the flag
|
LGTM. EICs, this is ready to accept. |
Thanks @karthik. In the future can you ping @openjournals/joss-eics? |
@whedon accept deposit=true |
|
🚨🚨🚨 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... |
@wrathematics - many thanks for your review here and to @karthik for editing this submission ✨ @bastistician - your paper is now accepted into JOSS ⚡🚀💥 |
🎉🎉🎉 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: @bastistician (Sebastian Meyer)
Repository: https://github.com/bastistician/polyCub
Version: 0.7.0
Editor: @karthik
Reviewer: @wrathematics
Archive: 10.5281/zenodo.2559486
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) 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
@wrathematics, 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.theoj.org/about#reviewer_guidelines. Any questions/concerns please let @karthik know.
✨ Please try and complete your review in the next two weeks ✨
Review checklist for @wrathematics
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
paper.md
file include a list of authors with their affiliations?The text was updated successfully, but these errors were encountered: