-
-
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]: **geostan**: An R package for Bayesian spatial analysis #4716
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 |
|
Dear @wcjochem and @becarioprecario This is the review thread. Firstly, type
to generate your own checklist. In that checklist, there are 20 check items. Whenever you complete the corresponding task, you can check off them. The review process is interactive so you can always interact with the authors, reviewers, and the editor. You can also create issues and pull requests in the target repo. Please do mention this thread's URL in the issues so we can keep tracking what is going on out of our world. Please do not hesitate to ask me anything, anytime. Thank you in advance! |
Dear @wcjochem and @becarioprecario Could you please update your status on how is going your review and generate your task lists? Thank you in advance. |
@editorialbot remind @wcjochem in two days |
Reminder set for @wcjochem in two days |
@editorialbot remind @becarioprecario in two days |
Reminder set for @becarioprecario in two days |
Thanks @editorialbot ! |
You are welcome |
👋 @wcjochem, please update us on how your review is going (this is an automated reminder). |
👋 @becarioprecario, please update us on how your review is going (this is an automated reminder). |
@editorialbot generate pdf |
@wcjochem, @becarioprecario - could you please update your status? Can I kindly ask you to create your check list first? Thank you in advance. |
Hi @jbytecode when I agreed to review this submission I said I couldn't start until after 15 September. So I have only started my review and it is ongoing. Thanks. |
@wcjochem - I am so sorry for bothering and pinging you too much, my bad! I totally forgot your deadline. Thank you for reminding that. |
@becarioprecario - could you please update your status? We have failed to get a life signal from you. Setting a deadline for us would be great, if possible. Thank you in advance. |
Dear @becarioprecario, This is the last reminder. Since you never sent a response, I assume that you are so much busy to reply messages, and/or you are not able to receive notifications. If you don't set a deadline for us until 15th October, I will try to find another reviewer for this issue. Thank you in advance. |
Hi,
Sorry for the delay. I will try to send the review by the end of the week.
Best,
Virgilio
El 13 oct 2022, a las 11:20, Mehmet Hakan Satman ***@***.******@***.***>> escribió:
Dear @becarioprecario<https://github.com/becarioprecario>,
This is the last reminder. Since you never sent a response, I assume that you are so much busy to reply messages, and/or you are not able to receive notifications. If you don't set a deadline for us until 15th October, I will try to find another reviewer for this issue.
Thank you in advance.
—
Reply to this email directly, view it on GitHub<#4716 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABYD6WSVIO4RWQRSZ6H5V7LWC7H6DANCNFSM573GXAFQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@editorialbot recommend-accept |
|
Thanks @jbytecode, @wcjochem and @jbytecode for a smooth and productive editorial experience. |
ID tblU003Amodels already defined |
|
@openjournals/dev - I need your help, thank you in advance! |
This looks like a pandoc bug. As a workaround, the |
@ConnorDonegan - could you please help changing the markdown as suggested? |
@editorialbot recommend-accept |
|
👋 @openjournals/sbcs-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#3717, then you can now move forward with accepting the submission by compiling again with the command |
|
@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... |
@wcjochem, @becarioprecario – many thanks for your reviews here and to @jbytecode for editing this submission! JOSS relies upon the volunteer effort of people like you and we simply wouldn't be able to do this without you ✨ @ConnorDonegan – your paper is now accepted and published in 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! 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: @ConnorDonegan (Connor Donegan)
Repository: https://github.com/ConnorDonegan/geostan
Branch with paper.md (empty if default branch): JOSS
Version: v0.4.1
Editor: @jbytecode
Reviewers: @wcjochem, @becarioprecario
Archive: 10.5281/zenodo.7311716
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
@wcjochem & @becarioprecario, 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 @jbytecode 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 @becarioprecario
📝 Checklist for @wcjochem
The text was updated successfully, but these errors were encountered: