Closed editorialbot closed 1 year ago
@ronyronen, you could just change the title in the zenodo archive you provided. Let me know once done.
@ronyronen, you could just change the title in the zenodo archive you provided. Let me know once done.
Done.
@editorialbot set 10.5281/zenodo.8060399 as archive
Done! archive is now 10.5281/zenodo.8060399
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@nachootal, looks like your comments are addressed. Please confirm your decision so that I can proceed with the submission. Thanks so much!!
Hi @prashjha, looks good to me.
Thanks and keep up the good work @ronyronen :) , Nacho
@nachootal, noted and thanks for the prompt response :)
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1109/ACCESS.2019.2927931 is OK
- 10.5028/jatm.v11.1081 is OK
MISSING DOIs
- None
INVALID DOIs
- None
Hi, @ronyronen, see if these suggestions make sense for your draft:
Initialization
and Operation
by considering bold font weight.Let me know when you are finished editing the draft.
Hello, @prashjha. Than's for your time to review the work. I have made the necessary adjustments based on your feedback.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
perfect, @ronyronen
@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/ACCESS.2019.2927931 is OK
- 10.5028/jatm.v11.1081 is OK
MISSING DOIs
- None
INVALID DOIs
- None
:wave: @openjournals/pe-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/4337, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
Hello @ronyr, a few final things to fix before publishing:
@kyleniemeyer Thank you for the feedback. I've fixed that.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@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: Ronen given-names: Rony orcid: "https://orcid.org/0000-0002-1300-5236" - family-names: Britvin given-names: Michael orcid: "https://orcid.org/0009-0003-5492-4014" - family-names: Moshe given-names: Boaz Ben orcid: "https://orcid.org/0000-0002-1580-5421" doi: 10.5281/zenodo.8060399 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Ronen given-names: Rony orcid: "https://orcid.org/0000-0002-1300-5236" - family-names: Britvin given-names: Michael orcid: "https://orcid.org/0009-0003-5492-4014" - family-names: Moshe given-names: Boaz Ben orcid: "https://orcid.org/0000-0002-1580-5421" date-published: 2023-06-24 doi: 10.21105/joss.05147 issn: 2475-9066 issue: 86 journal: Journal of Open Source Software publisher: name: Open Journals start: 5147 title: "SATLLA0: A Flight Software Platform for Aerospace and STEM Education" type: article url: "https://joss.theoj.org/papers/10.21105/joss.05147" volume: 8 title: "SATLLA0: A Flight Software Platform for Aerospace and STEM Education" ```
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...
@prashjha @kyleniemeyer @federeghe @nachootal Thank you all for your invaluable review of this paper.
Congratulations @ronyr on your article's publication in JOSS! Please consider signing up as a future reviewer, if you haven't already.
Many thanks to @nachootal and @federeghe for reviewing, and @prashjha for editing.
: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.05147/status.svg)](https://doi.org/10.21105/joss.05147)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.05147">
<img src="https://joss.theoj.org/papers/10.21105/joss.05147/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.05147/status.svg
:target: https://doi.org/10.21105/joss.05147
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-->@ronyr<!--end-author-handle-- (Rony Ronen) Repository: https://github.com/kcglab/satllazero Branch with paper.md (empty if default branch): Version: 4.0.13 Editor: !--editor-->@prashjha<!--end-editor-- Reviewers: @nachootal, @federeghe Archive: 10.5281/zenodo.8060399
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
@nachootal & @federeghe, 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 @prashjha 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 @federeghe
📝 Checklist for @nachootal