openjournals / joss-reviews

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

[REVIEW]: BoboCEP: a Fault-Tolerant Complex Event Processing Engine for Edge Computing in Internet of Things #5858

Closed editorialbot closed 12 months ago

editorialbot commented 1 year ago

Submitting author: !--author-handle-->@r3w0p<!--end-author-handle-- (Alexander Power) Repository: https://github.com/r3w0p/bobocep Branch with paper.md (empty if default branch): joss Version: 1.1.1 Editor: !--editor-->@vissarion<!--end-editor-- Reviewers: @abhishektiwari, @mahsan321 Archive: 10.5281/zenodo.10160409

Status

status

Status badge code:

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

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

@abhishektiwari & @mahsan321, 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 @vissarion 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 @mahsan321

editorialbot commented 12 months ago
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1109/JIOT.2020.3015432 is OK
- 10.1016/j.eswa.2021.115578 is OK
- 10.1109/DCOSS.2017.14 is OK
- 10.1145/2187671.2187677 is OK
- 10.3390/iot3030019 is OK
- 10.1007/s00778-019-00557-w is OK
- 10.1109/BigDataService49289.2020.00024 is OK
- 10.3390/s21165464 is OK
- 10.11606/D.45.2021.tde-24032021-145027 is OK
- 10.1016/j.compeleceng.2021.107257 is OK
- 10.1007/s40815-021-01118-6 is OK

MISSING DOIs

- None

INVALID DOIs

- None
editorialbot commented 12 months 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/4795, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

r3w0p commented 12 months ago

@vissarion The final proof looks good to me. Happy to move forward if you are!

danielskatz commented 12 months ago

@r3w0p - I'm the track editor who will finish the processing of this submission. I've found a couple of small issues in the paper, as indicated in https://github.com/r3w0p/bobocep/pull/10 - please merge this, and we can proceed to publication.

danielskatz commented 12 months ago

@editorialbot recommend-accept

@r3w0p - please confirm that this is ok again

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

OK DOIs

- 10.1109/JIOT.2020.3015432 is OK
- 10.1016/j.eswa.2021.115578 is OK
- 10.1109/DCOSS.2017.14 is OK
- 10.1145/2187671.2187677 is OK
- 10.3390/iot3030019 is OK
- 10.1007/s00778-019-00557-w is OK
- 10.1109/BigDataService49289.2020.00024 is OK
- 10.3390/s21165464 is OK
- 10.11606/D.45.2021.tde-24032021-145027 is OK
- 10.1016/j.compeleceng.2021.107257 is OK
- 10.1007/s40815-021-01118-6 is OK

MISSING DOIs

- None

INVALID DOIs

- None
editorialbot commented 12 months 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/4798, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

r3w0p commented 12 months ago

@danielskatz Yes this looks okay to me 👍

danielskatz commented 12 months ago

@editorialbot accept

editorialbot commented 12 months ago
Doing it live! Attempting automated processing of paper acceptance...
editorialbot commented 12 months 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: Power given-names: Alexander orcid: "https://orcid.org/0000-0001-5348-7068" doi: 10.5281/zenodo.10160409 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Power given-names: Alexander orcid: "https://orcid.org/0000-0001-5348-7068" date-published: 2023-11-21 doi: 10.21105/joss.05858 issn: 2475-9066 issue: 91 journal: Journal of Open Source Software publisher: name: Open Journals start: 5858 title: "BoboCEP: a Fault-Tolerant Complex Event Processing Engine for Edge Computing in Internet of Things" type: article url: "https://joss.theoj.org/papers/10.21105/joss.05858" volume: 8 title: "BoboCEP: a Fault-Tolerant Complex Event Processing Engine for Edge Computing in Internet of Things" ```

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 12 months ago

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

editorialbot commented 12 months 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/4799
  2. Wait five minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.05858
  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...

r3w0p commented 12 months ago

@danielskatz @vissarion @abhishektiwari @mahsan321

Thanks for all your help in getting this work published!

danielskatz commented 12 months ago

Congratulations to @r3w0p (Alexander Power) and co-authors on your publication!!

And thanks to @abhishektiwari and @mahsan321 for reviewing, and to @vissarion for editing! JOSS depends on volunteers; we couldn't do this without you!

editorialbot commented 12 months 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.05858/status.svg)](https://doi.org/10.21105/joss.05858)

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

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

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: