Closed whedon closed 3 years ago
Attempting PDF compilation from custom branch joss-paper. Reticulating splines etc...
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@sbozzolo, one more request: could you change the Zenodo archive title to match this submission title (see https://joss.readthedocs.io/en/latest/editing.html#after-reviewers-recommend-acceptance)? The author list should also match the submission's author list. (But thanks for the credit! :) )
How do I do it? Everything was generated automatically by Zenodo
EDIT: I found out: I have to add a zenodo.json
to my repo. I'll regenerate the archive.
Okay, I think I got it (even if I had to regenerate the archive 3 times)!
The new DOI is 10.5281/zenodo.4681119
@whedon set 10.5281/zenodo.4681119 as archive
OK. 10.5281/zenodo.4681119 is the archive.
@whedon generate pdf from branch joss-paper
Attempting PDF compilation from custom branch joss-paper. Reticulating splines etc...
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@whedon accept
Attempting dry run of processing paper acceptance...
PDF failed to compile for issue #3099 with the following error:
Can't find any papers to compile :-(
@whedon accept from branch joss-paper
Attempting dry run of processing paper acceptance...
:wave: @openjournals/joss-eics, this paper is ready to be accepted and published.
Check final proof :point_right: https://github.com/openjournals/joss-papers/pull/2222
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/2222, then you can now move forward with accepting the submission by compiling again with the flag deposit=true
e.g.
@whedon accept deposit=true from branch joss-paper
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.5281/zenodo.3866075 is OK
- 10.1007/3-540-36569-9_13 is OK
- doi:10.1088/0264-9381/29/11/115001 is OK
- 10.1103/PhysRevD.72.024028 is OK
- 10.1088/1361-6382/aa9cad is OK
- 10.1145/3311790.3396656 is OK
MISSING DOIs
- None
INVALID DOIs
- None
Thanks @Sbozzolo for the nice package, and thanks @Yurlungur for an exceptionally thorough review! I appreciate your collaboration.
My pleasure. I'm very excited to see Kuibit enter the Einstein Toolkit ecosystem!
Hi @Sbozzolo, I am the AEIC on duty this week doing some final checks before accepting.
I noticed that the Guercilena citation might have the incorrect title or URL, can you double check that one? I think it should be rugutils.
Thank you very much, @eloisabentivegna and @Yurlungur !
@kyleniemeyer, yes, thanks, I just pushed a new version. I also took the chance to add the Cactus citation inline when I mention Cactus.
@whedon generate pdf
PDF failed to compile for issue #3099 with the following error:
Can't find any papers to compile :-(
@whedon generate pdf from branch joss-paper
Attempting PDF compilation from custom branch joss-paper. Reticulating splines etc...
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@whedon accept from branch joss-paper
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.5281/zenodo.3866075 is OK
- 10.1007/3-540-36569-9_13 is OK
- doi:10.1088/0264-9381/29/11/115001 is OK
- 10.1103/PhysRevD.72.024028 is OK
- 10.1088/1361-6382/aa9cad is OK
- 10.1145/3311790.3396656 is OK
MISSING DOIs
- None
INVALID DOIs
- None
:wave: @openjournals/joss-eics, this paper is ready to be accepted and published.
Check final proof :point_right: https://github.com/openjournals/joss-papers/pull/2224
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/2224, then you can now move forward with accepting the submission by compiling again with the flag deposit=true
e.g.
@whedon accept deposit=true from branch joss-paper
@whedon accept deposit=true from branch joss-paper
Doing it live! Attempting automated processing of paper acceptance...
π¦π¦π¦ π Tweet for this paper π π¦π¦π¦
π¨π¨π¨ THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! π¨π¨π¨
Here's what you must now do:
Party like you just published a paper! πππ¦ππ»π€
Any issues? Notify your editorial technical team...
Congratulations @Sbozzolo on your article's publication in JOSS!
Many thanks to @Yurlungur for reviewing this, and @eloisabentivegna for editing (and reviewing).
: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.03099/status.svg)](https://doi.org/10.21105/joss.03099)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.03099">
<img src="https://joss.theoj.org/papers/10.21105/joss.03099/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.03099/status.svg
:target: https://doi.org/10.21105/joss.03099
This is how it will look in your documentation:
We need your help!
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: @sbozzolo (Gabriele Bozzola) Repository: https://github.com/Sbozzolo/kuibit/ Version: 1.0.0 Editor: @eloisabentivegna Reviewer: @yurlungur, @eloisabentivegna Archive: 10.5281/zenodo.4681119
:warning: JOSS reduced service mode :warning:
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
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
@yurlungur & @eloisabentivegna, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @eloisabentivegna 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 β¨
Review checklist for @yurlungur
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @eloisabentivegna
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper