Closed whedon closed 1 year ago
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@danielenricocahall It looks good now. Please generate the following:
Sure!
Release number: 3.4.7 Zenodo DOI: 10.5281/zenodo.7435012
@editorialbot set 3.4.7 as version
Done! version is now 3.4.7
@editorialbot set 10.5281/zenodo.7435012 as archive
Done! Archive is now 10.5281/zenodo.7435012
@danielenricocahall the title of the archive is wrong and it should read
Elephas: Distributed Deep Learning with Keras & Spark
You can edit the title and there is no need for a new DOI.
@diehlpk done!
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1145/3357223.3362707 is OK
MISSING DOIs
- None
INVALID DOIs
- None
:wave: @openjournals/dsais-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/3805, 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...
🐦🐦🐦 👉 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...
Wooo! This is exciting! Everything looks good except on the DOI it looks like it links to the old repository - is there any way to edit that? I'm not sure where that was set or if we missed something.
Also, just realized we didn't change the API documentation link to https://danielenricocahall.github.io/elephas/ instead of the old page (http://maxpumperla.com/elephas/). Is there any way we could edit that too?
Wooo! This is exciting! Everything looks good except on the DOI it looks like it links to the old repository - is there any way to edit that? I'm not sure where that was set or if we missed something.
Could you be be more specific here, i.e., what link is wrong and where?
Also, just realized we didn't change the API documentation link to https://danielenricocahall.github.io/elephas/ instead of the old page (http://maxpumperla.com/elephas/). Is there any way we could edit that too?
Yes, just update your paper and we can re-accept
Sure! Specifically, I mean on https://joss.theoj.org/papers/10.21105/joss.04073, the "Software Repository" button links to https://github.com/maxpumperla/elephas instead of https://github.com/danielenricocahall/elephas, the currently active fork. It's linked correctly in the actual paper (the "Repository" link goes to https://github.com/danielenricocahall/elephas). And sure thing, will edit now.
Ah right. We can fix that.
@editorialbot set https://github.com/danielenricocahall/elephas as repository
Done! repository is now https://github.com/danielenricocahall/elephas
@editorialbot generate pdf
:warning: An error happened when generating the pdf.
@editorialbot reaccept
Rebuilding paper!
🌈 Paper updated!
New PDF and metadata files :point_right: https://github.com/openjournals/joss-papers/pull/3818
@danielenricocahall – can you take a look and see if things are looking better for the doc now?
: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.04073/status.svg)](https://doi.org/10.21105/joss.04073)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04073">
<img src="https://joss.theoj.org/papers/10.21105/joss.04073/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04073/status.svg
:target: https://doi.org/10.21105/joss.04073
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:
@danielenricocahall – can you take a look and see if things are looking better for the doc now?
@arfon checking now. The link is correct now (thank you!). It looks like the hyperlinks are still out-of-date though. Is it because the new pdf wasn't successfully published before the reaccept?
Seems to be working now actually - thank you for everything!
Submitting author: !--author-handle-->@maxpumperla<!--end-author-handle-- (Max Pumperla) Repository: https://github.com/danielenricocahall/elephas Branch with paper.md (empty if default branch): mp_joss_paper Version: 3.4.7 Editor: !--editor-->@diehlpk<!--end-editor-- Reviewers: @sepandhaghighi, @nmoran Archive: 10.5281/zenodo.7435012
: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
@marksantcroos & @burch-cm, 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 @taless474 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 ✨