Closed editorialbot closed 4 months ago
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Hi @kthyng we have addressed your comments above, thanks!
Ok everything looks good!
@editorialbot accept
Doing it live! Attempting automated processing of paper acceptance...
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:
``` cff-version: "1.2.0" authors: - family-names: Gupta given-names: Rohini S. orcid: "https://orcid.org/0000-0003-3538-0675" - family-names: Vernon given-names: Chris R. orcid: "https://orcid.org/0000-0002-3406-6214" - family-names: Thurber given-names: Travis orcid: "https://orcid.org/0000-0002-4370-9971" - family-names: Gold given-names: David F. orcid: "https://orcid.org/0000-0002-0854-1819" - family-names: Hirsch given-names: Zachary M. orcid: "https://orcid.org/0009-0007-5356-5354" - family-names: Hadjimichael given-names: Antonia orcid: "https://orcid.org/0000-0001-7330-6834" - family-names: Reed given-names: Patrick M. orcid: "https://orcid.org/0000-0002-7963-6102" doi: 10.5281/zenodo.11061890 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Gupta given-names: Rohini S. orcid: "https://orcid.org/0000-0003-3538-0675" - family-names: Vernon given-names: Chris R. orcid: "https://orcid.org/0000-0002-3406-6214" - family-names: Thurber given-names: Travis orcid: "https://orcid.org/0000-0002-4370-9971" - family-names: Gold given-names: David F. orcid: "https://orcid.org/0000-0002-0854-1819" - family-names: Hirsch given-names: Zachary M. orcid: "https://orcid.org/0009-0007-5356-5354" - family-names: Hadjimichael given-names: Antonia orcid: "https://orcid.org/0000-0001-7330-6834" - family-names: Reed given-names: Patrick M. orcid: "https://orcid.org/0000-0002-7963-6102" date-published: 2024-04-25 doi: 10.21105/joss.06325 issn: 2475-9066 issue: 96 journal: Journal of Open Source Software publisher: name: Open Journals start: 6325 title: "statemodify: a Python framework to facilitate accessible exploratory modeling for discovering drought vulnerabilities" type: article url: "https://joss.theoj.org/papers/10.21105/joss.06325" volume: 9 title: "statemodify: a Python framework to facilitate accessible exploratory modeling for discovering drought vulnerabilities" ```
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...
Congratulations on your new publication @rg727! Many thanks to @cheginit and to reviewers @barneydobson and @ekblad for your time, hard work, and expertise!! JOSS wouldn't be able to function nor succeed without your efforts.
:tada::tada::tada: Congratulations on your paper acceptance! :tada::tada::tada:
If you would like to include a link to your paper from your README use the following code snippets:
Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.06325/status.svg)](https://doi.org/10.21105/joss.06325)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.06325">
<img src="https://joss.theoj.org/papers/10.21105/joss.06325/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.06325/status.svg
:target: https://doi.org/10.21105/joss.06325
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:
@rg727 If you're interested in reviewing for JOSS, you can sign up at: https://reviewers.joss.theoj.org/
Thank you @ekblad and @barneydobson for all your help reviewing and @kthyng @cheginit for facilitating the review process!
Submitting author: !--author-handle-->@rg727<!--end-author-handle-- (Rohini Gupta) Repository: https://github.com/IMMM-SFA/statemodify Branch with paper.md (empty if default branch): Version: 0.2.1 Editor: !--editor-->@cheginit<!--end-editor-- Reviewers: @barneydobson, @ekblad Archive: 10.5281/zenodo.11061890
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
@barneydobson & @ekblad, 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 @cheginit 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 @barneydobson
π Checklist for @ekblad