search

openjournals / joss-reviews

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

[REVIEW]: NiaARM: A minimalistic framework for Numerical Association Rule Mining #4448

Closed editorialbot closed 2 years ago

editorialbot commented 2 years ago

Submitting author: !--author-handle-->@zStupan<!--end-author-handle-- (Žiga Stupan) Repository: https://github.com/firefly-cpp/NiaARM Branch with paper.md (empty if default branch): Version: 0.2.1 Editor: !--editor-->@fabian-s<!--end-editor-- Reviewers: @diegomcarvalho, @fabian-s Archive: 10.5281/zenodo.7123879

Status

status

Status badge code:

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

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

@diegomcarvalho & @timClicks, 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 @fabian-s 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 @diegomcarvalho

📝 Checklist for @timClicks

📝 Checklist for @fabian-s

arfon commented 2 years ago

@editorialbot accept

editorialbot commented 2 years ago 
Doing it live! Attempting automated processing of paper acceptance...
editorialbot commented 2 years ago

🐦🐦🐦 👉 Tweet for this paper 👈 🐦🐦🐦

editorialbot commented 2 years 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/3570
  2. Wait a couple of minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.04448
  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...

timClicks commented 2 years ago

Well done @zStupan. Sorry again for slowing this process down.

arfon commented 2 years ago

@diegomcarvalho, @fabian-s – many thanks for your reviews here and to @fabian-s for editing this submission! JOSS relies upon the volunteer effort of people like you and we simply wouldn't be able to do this without you ✨

@zStupan – your paper is now accepted and published in JOSS :zap::rocket::boom:

editorialbot commented 2 years 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.04448/status.svg)](https://doi.org/10.21105/joss.04448)

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

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

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: