Closed editorialbot closed 5 months ago
:wave: @openjournals/csism-eics, this paper is ready to be accepted and published.
Check final proof :point_right::page_facing_up: Download article
If the paper PDF and the deposit XML files look good in https://github.com/openjournals/joss-papers/pull/5188, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@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: Brown given-names: Shael orcid: "https://orcid.org/0000-0001-8868-2867" - family-names: Farivar-Mohseni given-names: Reza orcid: "https://orcid.org/0000-0002-3123-2627" doi: 10.5281/zenodo.10814141 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Brown given-names: Shael orcid: "https://orcid.org/0000-0001-8868-2867" - family-names: Farivar-Mohseni given-names: Reza orcid: "https://orcid.org/0000-0002-3123-2627" date-published: 2024-03-27 doi: 10.21105/joss.06321 issn: 2475-9066 issue: 95 journal: Journal of Open Source Software publisher: name: Open Journals start: 6321 title: "TDApplied: An R package for machine learning and inference with persistence diagrams" type: article url: "https://joss.theoj.org/papers/10.21105/joss.06321" volume: 9 title: "TDApplied: An R package for machine learning and inference with persistence diagrams" ```
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 to @shaelebrown (Shael Brown) and co-author on your publication!!
And thanks to @EduPH and @peekxc for reviewing, and to @mahfuz05062 for editing! JOSS depends on volunteers and we couldn't do this without you
: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.06321/status.svg)](https://doi.org/10.21105/joss.06321)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.06321">
<img src="https://joss.theoj.org/papers/10.21105/joss.06321/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.06321/status.svg
:target: https://doi.org/10.21105/joss.06321
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:
@danielskatz @mahfuz05062 @peekxc @EduPH thank you all so much for your invaluable feedback, suggestions, time and effort. It is a pleasure to see our paper up on JOSS! Thank you all!
Submitting author: !--author-handle-->@shaelebrown<!--end-author-handle-- (Shael Brown) Repository: https://github.com/shaelebrown/TDApplied Branch with paper.md (empty if default branch): JOSS Version: v3.0.3 Editor: !--editor-->@mahfuz05062<!--end-editor-- Reviewers: @EduPH, @peekxc Archive: 10.5281/zenodo.10814141
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
@EduPH & @peekxc, 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 @mahfuz05062 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 @EduPH
📝 Checklist for @peekxc