Closed editorialbot closed 8 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/4903, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
Thanks @mstimberg! @daniellerch - I'll now proofread this and let you know the next steps
π @daniellerch - I've suggested some minor changes in the paper text in https://github.com/daniellerch/aletheia/pull/34 - please merge this, or let me know what you disagree with, then we can proceed to acceptance and publication
Thank you for your input @danielskatz, I've merged the suggested changes.
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1109/TIFS.2018.2871749 is OK
- 10.1145/1288869.1288872 is OK
- 10.1109/TIFS.2014.2312817 is OK
- 10.1007/11552055_12 is OK
- 10.1186/1687-417X-2014-1 is OK
- 10.1145/2482513.2482965 is OK
- 10.1145/3335203.3335738 is OK
- 10.1109/tdsc.2022.3154967 is OK
- 10.1109/icip.2014.7025854 is OK
- 10.1007/3-540-45496-9_2 is OK
- 10.1109/WIFS49906.2020.9360897 is OK
MISSING DOIs
- None
INVALID DOIs
- None
: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/4912, 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: Lerch-Hostalot given-names: Daniel orcid: "https://orcid.org/0000-0003-2602-672X" - family-names: MegΓas given-names: David orcid: "https://orcid.org/0000-0002-0507-7731" doi: 10.5281/zenodo.10497963 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Lerch-Hostalot given-names: Daniel orcid: "https://orcid.org/0000-0003-2602-672X" - family-names: MegΓas given-names: David orcid: "https://orcid.org/0000-0002-0507-7731" date-published: 2024-01-16 doi: 10.21105/joss.05982 issn: 2475-9066 issue: 93 journal: Journal of Open Source Software publisher: name: Open Journals start: 5982 title: "Aletheia: an open-source toolbox for steganalysis" type: article url: "https://joss.theoj.org/papers/10.21105/joss.05982" volume: 9 title: "Aletheia: an open-source toolbox for steganalysis" ```
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 @daniellerch (Daniel Lerch-Hostalot) and co-author on your publication!!
And thanks to @YassineYousfi and @ragibson for reviewing, and to @mstimberg for editing! JOSS depends on volunteers and couldn't be successful 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.05982/status.svg)](https://doi.org/10.21105/joss.05982)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.05982">
<img src="https://joss.theoj.org/papers/10.21105/joss.05982/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.05982/status.svg
:target: https://doi.org/10.21105/joss.05982
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:
Thanks @YassineYousfi, @ragibson, @mstimberg and @danielskatz for your great work on the JOSS publication. Really appreciate your insightful reviews and edits!
Submitting author: !--author-handle-->@daniellerch<!--end-author-handle-- (Daniel Lerch-Hostalot) Repository: https://github.com/daniellerch/aletheia Branch with paper.md (empty if default branch): master Version: v0.3 Editor: !--editor-->@mstimberg<!--end-editor-- Reviewers: @YassineYousfi, @ragibson Archive: 10.5281/zenodo.10497963
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
@YassineYousfi & @ragibson, 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 @mstimberg 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 @ragibson
π Checklist for @YassineYousfi