-
-
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]: Pyafscgap.org: Open source multi-modal Python-based tools for NOAA AFSC RACE GAP #5593
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 |
|
This is a pyopensci related submission which was reviewed here: pyOpenSci/software-submission#93 |
@sampottinger please try to address the potentially missing DOI listed ☝️ , you can use |
@sampottinger I have checked your paper and noticed some minor typos, please address them, see below. I also recommend that you proof read your paper once more and amend where needed.
Relating to the ZENODO archive:
|
Post-Review Checklist for Editor and AuthorsAdditional Author Tasks After Review is Complete
Editor Tasks Prior to Acceptance
|
@editorialbot set 10.5281/zenodo.7991875 as archive |
Done! archive is now 10.5281/zenodo.7991875 |
@editorialbot set 1.0.2 as version |
Done! version is now 1.0.2 |
Thanks for all of this @Kevin-Mattheus-Moerman!
Thank you for flagging those I’ll address shortly.
I’ll confirm these items shortly!
Thanks! ORDS does not have a DOI as far as I can tell. The one suggested is a book for Oracle Cloud Services. Please advise how you want to continue but the current citation may be best. |
@sampottinger On the DOI, if you believe not having the DOI is correct then just leave it the way it is. |
Phenomenal! I’ll take care of the other items today or tomorrow. Thanks again! |
@editorialbot set 1.0.3 as version |
I'm sorry @sampottinger, I'm afraid I can't do that. That's something only editors are allowed to do. |
@editorialbot generate pdf |
@editorialbot check references |
|
(Sorry that DOI check keeps catching ORDS which doesn't have a DOI... the DOI it recommends is incorect) |
@editorialbot accept |
|
@Kevin-Mattheus-Moerman - can you change to version Sorry I should have bolded that request in my earlier message. 😬 The only practical difference is a typo fix in the paper and correction of zenodo metadata. |
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... |
@Kevin-Mattheus-Moerman - My apologies we should be good to go... you can ignore my earlier message unless you want to update the reference here. We reference latest in linking to zenodo 10.5281/zenodo.7991875. Either way, thanks so much for your review! |
@sampottinger it would be better to update the version and archive DOI here. We should be able to do that. Sorry I missed that in your comment! @openjournals/dev @arfon can you help process the following changes for this paper:
|
@Kevin-Mattheus-Moerman: Running those two commands to update the version and the archive values and then |
@editorialbot set 1.0.4 as version |
Done! version is now 1.0.4 |
@editorialbot set 10.5281/zenodo.8091843 as archive |
Done! archive is now 10.5281/zenodo.8091843 |
@editorialbot reaccept |
|
🌈 Paper updated! New PDF and metadata files 👉 openjournals/joss-papers#4361 |
@sampottinger this looks good to me now, and the paper available on the website points to the updated archive already. I'll close this issue now shortly. Congratulations again! |
🎉🎉🎉 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: @sampottinger (A Samuel Pottinger)
Repository: https://github.com/SchmidtDSE/afscgap
Branch with paper.md (empty if default branch):
Version: 1.0.4
Editor: @Kevin-Mattheus-Moerman
Reviewers: @Kevin-Mattheus-Moerman
Archive: 10.5281/zenodo.8091843
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
@Kevin-Mattheus-Moerman, 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 @Kevin-Mattheus-Moerman 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
@Kevin-Mattheus-Moerman, please create your checklist typing:
@editorialbot generate my checklist
The text was updated successfully, but these errors were encountered: