-
-
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]: harmonize-wq: Standardize, clean and wrangle Water Quality Portal data into more analytic-ready formats #7305
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:
|
|
Software report:
Commit count by author:
|
Paper file info: 📄 Wordcount for ✅ The paper includes a |
License info: ✅ License found: |
This submission was already reviewed through |
@jbousquin Do you have a Zenodo or similar archive of your code? |
After these checks are complete, I will publish your submission!
|
Current Zenodo DOI: 10.5281/zenodo.13356847 |
|
@editorialbot set 10.5281/zenodo.13356847 as archive |
Done! archive is now 10.5281/zenodo.13356847 |
@kthyng I'm new to using zenodo - would it better to do a 0.5.1 release that includes the paper_JOSS merged? |
How the paper file is arranged in the archive or if it is the most up to date isn't important since the words will be present in the paper itself, so no need from our perspective to do a new release for any changes in the paper. |
I think I was able to edit the authors (moved other types of contributors from creators to contributors) and title, everything else about that zenodo archive is auto-populated from github. Please let me know if any other fields need to be updated or anything doesn't match as it should. |
@jbousquin Looks good! Ready to wrap up. |
@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 👈 🐘🐘🐘 |
🦋🦋🦋 👉 Bluesky post 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 on your new publication @jbousquin! |
🎉🎉🎉 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: @jbousquin (Justin Bousquin)
Repository: https://github.com/USEPA/harmonize-wq
Branch with paper.md (empty if default branch): paper_JOSS
Version: 0.5.0
Editor: @kthyng
Reviewers: @kthyng
Archive: 10.5281/zenodo.13356847
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
@kthyng, 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 @kthyng 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
@kthyng, please create your checklist typing:
@editorialbot generate my checklist
The text was updated successfully, but these errors were encountered: