Closed editorialbot closed 1 month ago
editorialbot
commented
1 month 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/6008, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
danielskatz
commented
1 month ago @editorialbot accept
editorialbot
commented
1 month ago 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: Barbie given-names: Alexander orcid: "https://orcid.org/0000-0001-5352-6039" - family-names: Hasselbring given-names: Wilhelm orcid: "https://orcid.org/0000-0001-6625-4335" contact: - family-names: Barbie given-names: Alexander orcid: "https://orcid.org/0000-0001-5352-6039" doi: 10.5281/zenodo.13937454 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Barbie given-names: Alexander orcid: "https://orcid.org/0000-0001-5352-6039" - family-names: Hasselbring given-names: Wilhelm orcid: "https://orcid.org/0000-0001-6625-4335" date-published: 2024-10-16 doi: 10.21105/joss.07179 issn: 2475-9066 issue: 102 journal: Journal of Open Source Software publisher: name: Open Journals start: 7179 title: "ARCHES PiCar-X: Software for Digital Twin Research" type: article url: "https://joss.theoj.org/papers/10.21105/joss.07179" volume: 9 title: "ARCHES PiCar-X: Software for Digital Twin Research" ```
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.
editorialbot
commented
1 month ago 🐘🐘🐘 👉 Toot for this paper 👈 🐘🐘🐘
editorialbot
commented
1 month ago 🦋🦋🦋 👉 Bluesky post for this paper 👈 🦋🦋🦋
editorialbot
commented
1 month ago 🚨🚨🚨 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...
danielskatz
commented
1 month ago Congratulations to @AlexanderBarbie (Alexander Barbie) and @whasselbring on your publication!!
And thanks to @mrsonandrade and @AlexanderFabisch for reviewing! JOSS depends on volunteers and couldn't be successful without you
editorialbot
commented
1 month ago :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
```
Markdown:
[](https://doi.org/10.21105/joss.07179)
HTML:
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.07179/status.svg
:target: https://doi.org/10.21105/joss.07179
```
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: !--author-handle-->@AlexanderBarbie<!--end-author-handle-- (Alexander Barbie) Repository: https://github.com/cau-se/ARCHES-PiCar-X Branch with paper.md (empty if default branch): Version: v.1.1.1 Editor: !--editor-->@danielskatz<!--end-editor-- Reviewers: @mrsonandrade, @AlexanderFabisch Archive: 10.5281/zenodo.13937454
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
@mrsonandrade & @AlexanderFabisch, 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 @danielskatz 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 @AlexanderFabisch
📝 Checklist for @mrsonandrade