openjournals / joss-reviews

Reviews for the Journal of Open Source Software
Creative Commons Zero v1.0 Universal
725 stars 38 forks source link

[REVIEW]: OpenTera: A Framework for Telehealth Applications #5497

Closed editorialbot closed 1 year ago

editorialbot commented 1 year ago

Submitting author: !--author-handle-->@doumdi<!--end-author-handle-- (Dominic Létourneau) Repository: https://github.com/introlab/opentera Branch with paper.md (empty if default branch): main Version: v1.2.4-zenodo Editor: !--editor-->@galessiorob<!--end-editor-- Reviewers: @Rocsg, @tmickleydoyle Archive: 10.5281/zenodo.10078847

Status

status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/c77a176806a8ede2b63213f3df7f08d1"><img src="https://joss.theoj.org/papers/c77a176806a8ede2b63213f3df7f08d1/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/c77a176806a8ede2b63213f3df7f08d1/status.svg)](https://joss.theoj.org/papers/c77a176806a8ede2b63213f3df7f08d1)

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

@Rocsg & @NoujoudNader, 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:

@editorialbot generate my checklist

The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @galessiorob 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 @Rocsg

📝 Checklist for @NoujoudNader

📝 Checklist for @tmickleydoyle

doumdi commented 1 year ago

Draft of Docker installation can be found here but will be improved and incorporated in the main doc today : https://github.com/introlab/opentera/tree/main/docker/dev

doumdi commented 1 year ago

@tmickleydoyle, Any suggestion to improve the writing of the paper will be welcome. Thanks!

tmickleydoyle commented 1 year ago

@doumdi, here is my PR for some grammar suggestions.

https://github.com/introlab/opentera/pull/231

Let me know when the docker installation instructions are ready to be tested 🙇

doumdi commented 1 year ago

@tmickleydoyle Thanks for the suggestions, they are now merged into the joss-paper branch . For the docker installation, have a look at : https://introlab.github.io/opentera/deployment/DeployWithDockerCompose.html. Any suggestions / comments on the procedure is welcomed ! Thanks!

tmickleydoyle commented 1 year ago

Thank you all for the ⚡ fast update to the install process 😲 I will check out the docker install early next week 🙇

tmickleydoyle commented 1 year ago

@doumdi 🔆 Thank you for adding the instructions to install the software with Docker 🙇

@galessiorob 👋 I am 💯 to go with my checklist 🚀

tmickleydoyle commented 1 year ago

Thank you all for including me in this experience, and best of luck publishing the paper 🥇

galessiorob commented 1 year ago

Thank you all for your work to get this paper ready to be published! Since we have two full reviews we're ready to take the next steps:

@Rocsg and @tmickleydoyle thank you so, so much for your thorough and thoughtful reviews 🙏

tmickleydoyle commented 1 year ago

@galessiorob, you are the best! 🎉 ✨ 🎉

doumdi commented 1 year ago

@galessiorob You can cite all versions by using the DOI 10.5281/zenodo.10078846. This DOI represents all versions, and will always resolve to the latest one. Thank you @tmickleydoyle , @Kevin-Mattheus-Moerman , @Rocsg, @galessiorob ! BTW, the latest paper version is merged in the main branch.

galessiorob commented 1 year ago

@editorialbot set 10.5281/zenodo.10078846 as archive

editorialbot commented 1 year ago

Done! archive is now 10.5281/zenodo.10078846

galessiorob commented 1 year ago

@editorialbot set v1.2.4 as version

editorialbot commented 1 year ago

Done! version is now v1.2.4

galessiorob commented 1 year ago

@editorialbot generate pdf

editorialbot commented 1 year ago

:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:

galessiorob commented 1 year ago

@editorialbot recommend-accept

editorialbot commented 1 year ago
Attempting dry run of processing paper acceptance...
editorialbot commented 1 year ago
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1109/ICVR.2017.8007524 is OK
- 10.1109/EMBC.2017.8037404 is OK
- 10.1007/s12553-021-00636-5 is OK
- 10.1145/514183.514185 is OK

MISSING DOIs

- None

INVALID DOIs

- None
galessiorob commented 1 year ago

@doumdi an editor in chief will run the final steps to get it published. Thanks so much for working through the review, and congrats!

@Rocsg, @tmickleydoyle thank you so much for lending your time and expertise to this paper 🎉

editorialbot commented 1 year ago

:wave: @openjournals/bcm-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/4768, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

tmickleydoyle commented 1 year ago

@galessiorob 👋 Thank you for including me 😍

Kevin-Mattheus-Moerman commented 1 year ago

@editorialbot set v1.2.4-zenodo as version

editorialbot commented 1 year ago

Done! version is now v1.2.4-zenodo

Kevin-Mattheus-Moerman commented 1 year ago

Post-Review Checklist for Editor and Authors

Additional Author Tasks After Review is Complete

Editor Tasks Prior to Acceptance

Kevin-Mattheus-Moerman commented 1 year ago

@galessiorob thanks for editing here. In the future you can use the following new feature @editorialbot create post-review checklist. That will create this list :point_up: which will help keep track of the last steps needed before recommending acceptance. I'll take it from here now though. Thanks again.

Kevin-Mattheus-Moerman commented 1 year ago

@doumdi as AEiC I will now help process final steps. Please have a look at the author checklist above :point_up: which contains several points that require your attention.

doumdi commented 1 year ago

@galessiorob @Kevin-Mattheus-Moerman , I have made the required changes on Zenodo (authors, licence, title, and added summary) here: https://zenodo.org/records/10078847. I am unable to check the boxes in your previous post, but I think everything is done. Please let me know if more changes are required. Thanks!

Kevin-Mattheus-Moerman commented 1 year ago

@editorialbot set 10.5281/zenodo.10078847 as archive

editorialbot commented 1 year ago

Done! archive is now 10.5281/zenodo.10078847

Kevin-Mattheus-Moerman commented 1 year ago

@doumdi thanks, that all looks good now so we are good to proceed.

Kevin-Mattheus-Moerman commented 1 year ago

@editorialbot accept

editorialbot commented 1 year ago
Doing it live! Attempting automated processing of paper acceptance...
editorialbot commented 1 year ago

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:

CITATION.cff

``` cff-version: "1.2.0" authors: - family-names: Létourneau given-names: Dominic orcid: "https://orcid.org/0000-0001-7825-7533" - family-names: Brière given-names: Simon orcid: "https://orcid.org/0009-0000-1224-8001" - family-names: Maheux given-names: Marc-Antoine orcid: "https://orcid.org/0000-0002-3983-8754" - family-names: Godin given-names: Cédric - family-names: Warren given-names: Philippe orcid: "https://orcid.org/0009-0008-4466-0963" - family-names: Lauzier given-names: Gabriel - family-names: Joly given-names: Ian-Mathieu - family-names: Bourque given-names: Jérémie orcid: "https://orcid.org/0009-0008-5868-9724" - family-names: Arsenault given-names: Philippe orcid: "https://orcid.org/0009-0003-0772-1177" - family-names: Vilanova given-names: Cynthia - family-names: Tousignant given-names: Michel orcid: "https://orcid.org/0000-0001-7561-1170" - family-names: Michaud given-names: François orcid: "https://orcid.org/0000-0002-3639-7770" doi: 10.5281/zenodo.10078847 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Létourneau given-names: Dominic orcid: "https://orcid.org/0000-0001-7825-7533" - family-names: Brière given-names: Simon orcid: "https://orcid.org/0009-0000-1224-8001" - family-names: Maheux given-names: Marc-Antoine orcid: "https://orcid.org/0000-0002-3983-8754" - family-names: Godin given-names: Cédric - family-names: Warren given-names: Philippe orcid: "https://orcid.org/0009-0008-4466-0963" - family-names: Lauzier given-names: Gabriel - family-names: Joly given-names: Ian-Mathieu - family-names: Bourque given-names: Jérémie orcid: "https://orcid.org/0009-0008-5868-9724" - family-names: Arsenault given-names: Philippe orcid: "https://orcid.org/0009-0003-0772-1177" - family-names: Vilanova given-names: Cynthia - family-names: Tousignant given-names: Michel orcid: "https://orcid.org/0000-0001-7561-1170" - family-names: Michaud given-names: François orcid: "https://orcid.org/0000-0002-3639-7770" date-published: 2023-11-21 doi: 10.21105/joss.05497 issn: 2475-9066 issue: 91 journal: Journal of Open Source Software publisher: name: Open Journals start: 5497 title: "OpenTera: A Framework for Telehealth Applications" type: article url: "https://joss.theoj.org/papers/10.21105/joss.05497" volume: 8 title: "OpenTera: A Framework for Telehealth Applications" ```

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.

Find more information on .cff files here and here.

editorialbot commented 1 year ago

🐘🐘🐘 👉 Toot for this paper 👈 🐘🐘🐘

editorialbot commented 1 year ago

🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨

Here's what you must now do:

  1. Check final PDF and Crossref metadata that was deposited :point_right: https://github.com/openjournals/joss-papers/pull/4796
  2. Wait five minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.05497
  3. If everything looks good, then close this review issue.
  4. Party like you just published a paper! 🎉🌈🦄💃👻🤘

Any issues? Notify your editorial technical team...

Kevin-Mattheus-Moerman commented 1 year ago

Congratulations on this JOSS publication @doumdi !

Thanks for editing @galessiorob.

And a special thanks to the reviewers: @Rocsg, @tmickleydoyle

editorialbot commented 1 year 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 code snippets:

Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.05497/status.svg)](https://doi.org/10.21105/joss.05497)

HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.05497">
  <img src="https://joss.theoj.org/papers/10.21105/joss.05497/status.svg" alt="DOI badge" >
</a>

reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.05497/status.svg
   :target: https://doi.org/10.21105/joss.05497

This is how it will look in your documentation:

DOI

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: