Closed editorialbot closed 2 weeks ago
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
ā
OK DOIs
- 10.3389/friot.2022.1073780 is OK
- 10.1186/s40537-019-0268-2 is OK
š” SKIP DOIs
- No DOI given, and none found for title: I/O Completion Ports
- No DOI given, and none found for title: Mac OS X Manual Page For kqueue(2)
- No DOI given, and none found for title: IOBluetooth
- No DOI given, and none found for title: liburing
- No DOI given, and none found for title: Coroutines (C++20)
ā 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/5823, 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: Sun given-names: Aidan orcid: "https://orcid.org/0009-0000-6282-2497" doi: 10.5281/zenodo.13328366 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Sun given-names: Aidan orcid: "https://orcid.org/0009-0000-6282-2497" date-published: 2024-08-27 doi: 10.21105/joss.06964 issn: 2475-9066 issue: 100 journal: Journal of Open Source Software publisher: name: Open Journals start: 6964 title: "WhaleConnect: A General-Purpose, Cross-Platform Network Communication Application" type: article url: "https://joss.theoj.org/papers/10.21105/joss.06964" volume: 9 title: "WhaleConnect: A General-Purpose, Cross-Platform Network Communication Application" ```
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 @AidanSun05 (Aidan Sun) on your publication!!
And thanks to @harshadjs and @wob86 for reviewing, and to @mahfuz05062 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.06964/status.svg)](https://doi.org/10.21105/joss.06964)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.06964">
<img src="https://joss.theoj.org/papers/10.21105/joss.06964/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.06964/status.svg
:target: https://doi.org/10.21105/joss.06964
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:
Many thanks to @harshadjs @wob86 @mahfuz05062 @danielskatz for your time and effort during this review!
Submitting author: !--author-handle-->@AidanSun05<!--end-author-handle-- (Aidan Sun) Repository: https://github.com/WhaleConnect/whaleconnect Branch with paper.md (empty if default branch): paper Version: v1.0.2 Editor: !--editor-->@mahfuz05062<!--end-editor-- Reviewers: @harshadjs, @wob86 Archive: 10.5281/zenodo.13328366
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
@harshadjs & @wob86, 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 @wob86
š Checklist for @harshadjs