Closed editorialbot closed 1 year ago
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1007/978-3-7643-7791-5_2 is OK
- 10.1007/978-1-4419-7719-9_6 is OK
- 10.1007/978-981-33-6781-4_6 is OK
- 10.1007/BFb0054868 is OK
- 10.1109/CADS.2010.5623536 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/4230, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@AngryMaciek here it is - please check the final proof. As said here, changing papers after the publication is very tedioius.
Looks good... but my eyes are insensitive to this document anymore...
As track editor now taking over for the final processing, I'm suggesting a bunch of changes in https://github.com/AngryMaciek/hypercomplex/pull/46
Also, I don't understand "ferd36" as a an author - should this be Patrick R. Girard, the author of the overall book?
@danielskatz : yes, I think you are right, could you please include this in your branch so that I merge everything together?
done
Done, but give me a second please, page formatting is off, I will adjust the document once again.
@danielskatz : finished on my end!
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1007/978-3-7643-7791-5_2 is OK
- 10.1007/978-1-4419-7719-9_6 is OK
- 10.1007/978-981-33-6781-4_6 is OK
- 10.1007/BFb0054868 is OK
- 10.1109/CADS.2010.5623536 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/4231, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@AngryMaciek - sorry, one more fix that shouldn't be needed, but appears to be, plus a couple of things I missed: https://github.com/AngryMaciek/hypercomplex/pull/48
@danielskatz : merged!
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1007/978-3-7643-7791-5_2 is OK
- 10.1007/978-1-4419-7719-9_6 is OK
- 10.1007/978-981-33-6781-4_6 is OK
- 10.1007/BFb0054868 is OK
- 10.1109/CADS.2010.5623536 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/4232, 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: Bak given-names: Maciek orcid: "https://orcid.org/0000-0003-1361-7301" doi: 10.5281/zenodo.7938823 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Bak given-names: Maciek orcid: "https://orcid.org/0000-0003-1361-7301" date-published: 2023-05-15 doi: 10.21105/joss.05272 issn: 2475-9066 issue: 85 journal: Journal of Open Source Software publisher: name: Open Journals start: 5272 title: "Hypercomplex: abstract & fast header-only C++ template library for lattice-based cryptosystems in high-dimensional algebras" type: article url: "https://joss.theoj.org/papers/10.21105/joss.05272" volume: 8 title: "Hypercomplex: abstract & fast header-only C++ template library for lattice-based cryptosystems in high-dimensional algebras" ```
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.
🐦🐦🐦 👉 Tweet for this paper 👈 🐦🐦🐦
🐘🐘🐘 👉 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 @AngryMaciek (Maciej Bak)!!
And thanks to @vissarion, @ludopulles for reviewing, and to @olexandr-konovalov for editing (for the first time)! We couldn't do this without your voluntary efforts
: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.05272/status.svg)](https://doi.org/10.21105/joss.05272)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.05272">
<img src="https://joss.theoj.org/papers/10.21105/joss.05272/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.05272/status.svg
:target: https://doi.org/10.21105/joss.05272
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:
Thank you @danielskatz @olexandr-konovalov @vissarion @ludopulles for your time and effort to improve this work!
I am unimaginably happy to finalise this. What started as late-evening pet project years ago now evolved into original research in cryptography with state-of-the-art software engineering mechanisms. The scope grew waaaay beyond what I initially planed but now, as I pushed through all obstacles, I am really proud of it; I think it's the most challenging piece of math I've ever done on my own :)
All the best to everyone!
Dear @olexandr-konovalov and @danielskatz,
I have presented this work to my colleagues and they have unfortunately pointed out numerous embarrassing typos in mathematical notations which we have all missed here:
I have denoted the corrections below:
I understand this is a problem and I apologise for the situation but could we please adjust the publication as mentioned in the previous post (pointing to the JOSS guidelines)?
@AngryMaciek here it is - please check the final proof. As said here, changing papers after the publication is very tedioius.
Kind Regards,
@AngryMaciek - please update the .md file, and let me know when it is fixed.
@danielskatz - I have corrected the typos and clarified formula (2): current indices reflect formula (1) better so that they are visually closer; current master
branch contains a fixed version of paper.md
and that is the only file that was changed in the PR (https://github.com/AngryMaciek/hypercomplex/pull/54)
@editorialbot reaccept
Rebuilding paper!
🌈 Paper updated!
New PDF and metadata files :point_right: https://github.com/openjournals/joss-papers/pull/4251
@AngryMaciek - this should be fixed, though it might take a little bit to update everywhere
@danielskatz - Thank you very much for your help; I think it's all good now.
Submitting author: !--author-handle-->@AngryMaciek<!--end-author-handle-- (Maciej Bak) Repository: https://github.com/AngryMaciek/hypercomplex Branch with paper.md (empty if default branch): Version: v2.0.3 Editor: !--editor-->@olexandr-konovalov<!--end-editor-- Reviewers: @vissarion, @ludopulles Archive: 10.5281/zenodo.7938823
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
@vissarion & @ludopulles, 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 @olexandr-konovalov 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 @vissarion
📝 Checklist for @ludopulles