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]: concstats: Market Structure, Concentration and Inequality Measures, with R #5885
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 |
|
@SebastianWojcik86, @christopherkenny – just to confirm., there's nothing for you to do here as you've already completed the rOpenSci review 😸 |
@schneiderpy, could you please merge this PR? ropensci/concstats#2 Also, please check the possible missing DOI ( |
@arfon, thank you for you message. I have fixed the mentioned DOI and updated the bib. file accordingly. Furthermore, I have added the JOSS badge (Under review). Thank you. |
@editorialbot recommend-accept |
Paper is not ready for acceptance yet, the archive is missing |
@editorialbot set 10.5281/zenodo.7803764 as archive |
Done! archive is now 10.5281/zenodo.7803764 |
@editorialbot recommend-accept |
|
|
IDREFS attribute rid references an unknown ID "figU003Amstruct" |
@schneiderpy – looks like the |
@arfon - to understand the error .. the error ocurrs when generating the paper? (however, generating the draft worked fine) |
@arfon - Error is fixed. Thank you |
@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#4628, then you can now move forward with accepting the submission by compiling again with the command |
@editorialbot accept |
|
Ensure proper citation by uploading a plain text CITATION.cff file to the default branch of your repository. If using GitHub, a Cite this repository menu will appear in the About section, containing both APA and BibTeX formats. When exported to Zotero using a browser plugin, Zotero will automatically create an entry using the information contained in the .cff file. You can copy the contents for your CITATION.cff file here: CITATION.cff
If the repository is not hosted on GitHub, a .cff file can still be uploaded to set your preferred citation. Users will be able to manually copy and paste the citation. |
🐘🐘🐘 👉 Toot 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... |
@SebastianWojcik86, @christopherkenny – many thanks for your reviews here! JOSS relies upon the volunteer effort of people like you and we simply wouldn't be able to do this without you ✨ @schneiderpy – 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: @schneiderpy (Andreas Schneider)
Repository: https://github.com/ropensci/concstats
Branch with paper.md (empty if default branch):
Version: v.0.1.6
Editor: @arfon
Reviewers: @SebastianWojcik86, @christopherkenny
Archive: 10.5281/zenodo.7803764
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
@SebastianWojcik86 & @christopherkenny, 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 @arfon 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
@SebastianWojcik86, please create your checklist typing:
@editorialbot generate my checklist
@christopherkenny, please create your checklist typing:
@editorialbot generate my checklist
The text was updated successfully, but these errors were encountered: