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/5994, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
dtkerns
commented
1 month ago metadata updated
On Sun, Oct 13, 2024 at 11:47 AM The Open Journals editorial robot < @.***> wrote:
👋 @openjournals/csism-eics https://github.com/orgs/openjournals/teams/csism-eics, this paper is ready to be accepted and published.
Check final proof 👉📄 Download article https://raw.githubusercontent.com/openjournals/joss-papers/joss.06825/joss.06825/10.21105.joss.06825.pdf
If the paper PDF and the deposit XML files look good in openjournals/joss-papers#5994 https://github.com/openjournals/joss-papers/pull/5994, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
— Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/6825#issuecomment-2409083603, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADVJRKH2KNZ3VKPJG4WQGXDZ3K52LAVCNFSM6AAAAABIVCPMRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBZGA4DGNRQGM . You are receiving this because you were mentioned.Message ID: @.***>
danielskatz
commented
1 month ago I see the authors as partially updated, but not the title. And the authors aren't using names (and ORCIDs if desired), but still github usernames
dtkerns
commented
1 month ago sorry I missed those. done I noticed that the Zenodo entry defaulted to a Creative Commons 4.0 but On github I specified an MIT License ... are those different things, or do they need to be consistent?
On Sun, Oct 13, 2024 at 12:44 PM Daniel S. Katz @.***> wrote:
I see the authors as partially updated, but not the title. And the authors aren't using names (and ORCIDs if desired), but still github usernames Screenshot.2024-10-13.at.14.43.33.png (view on web) https://github.com/user-attachments/assets/ecfe24ae-d168-4403-b519-fee9309d9afe
— Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/6825#issuecomment-2409100968, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADVJRKC4JK7TETYLVLKNZF3Z3LETVAVCNFSM6AAAAABIVCPMRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBZGEYDAOJWHA . You are receiving this because you were mentioned.Message ID: @.***>
danielskatz
commented
1 month ago It's good to have the license being right the material being archived - thanks
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: Kerns given-names: David T - family-names: Adegbija given-names: Tosiron doi: 10.5281/zenodo.13926674 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Kerns given-names: David T - family-names: Adegbija given-names: Tosiron date-published: 2024-10-13 doi: 10.21105/joss.06825 issn: 2475-9066 issue: 102 journal: Journal of Open Source Software publisher: name: Open Journals start: 6825 title: An Open-Source Tool for Generating Domain-Specific Accelerators for Resource-Constrained Computing type: article url: "https://joss.theoj.org/papers/10.21105/joss.06825" volume: 9 title: An Open-Source Tool for Generating Domain-Specific Accelerators for Resource-Constrained Computing ```
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 @dtkerns (David Kerns) and co-author on your publication!!
And thanks to @manuel-g-castro and @abhishektiwari for reviewing, and to @gkthiruvathukal for editing! JOSS depends on volunteers and we couldn't do this 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.06825)
HTML:
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.06825/status.svg
:target: https://doi.org/10.21105/joss.06825
```
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-->@dtkerns<!--end-author-handle-- (David Kerns) Repository: https://github.com/dtkerns/d2 Branch with paper.md (empty if default branch): Version: v1.0.0-pub Editor: !--editor-->@gkthiruvathukal<!--end-editor-- Reviewers: @manuel-g-castro, @abhishektiwari Archive: 10.5281/zenodo.13926674
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
@manuel-g-castro & @abhishektiwari, 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 @gkthiruvathukal 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 @abhishektiwari
📝 Checklist for @manuel-g-castro