openjournals / joss-reviews

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

[REVIEW]: Metagenomic classification with KrakenUniq on low-memory computers #4908

Closed editorialbot closed 1 year ago

editorialbot commented 2 years ago

Submitting author: !--author-handle-->@salzberg<!--end-author-handle-- (Steven Salzberg) Repository: https://github.com/fbreitwieser/krakenuniq Branch with paper.md (empty if default branch): Version: v1.0.3 Editor: !--editor-->@lpantano<!--end-editor-- Reviewers: @Jessime, @MaximLippeveld Archive: 10.5281/zenodo.7459217

Status

status

Status badge code:

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

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

@Jessime & @MaximLippeveld, 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 @lpantano 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 @MaximLippeveld

šŸ“ Checklist for @Jessime

Kevin-Mattheus-Moerman commented 1 year ago

@alekseyzimin I am the AEiC on this track, and here to help process this work for acceptance in JOSS. I have reviewed the paper and archive and most seems in order, so we can proceed with acceptance. I do have one point below which you should fix at your earliest convenience:

I will now proceed with to acceptance in JOSS.

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

šŸ¦šŸ¦šŸ¦ šŸ‘‰ Tweet for this paper šŸ‘ˆ šŸ¦šŸ¦šŸ¦

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

@salzberg congratulations on this publication!

Thank you for editing this one @lpantano!

And a special thanks to the reviewers: @Jessime, @MaximLippeveld !!!!

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.04908/status.svg)](https://doi.org/10.21105/joss.04908)

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

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

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:

salzberg commented 1 year ago

@salzberg congratulations on this publication!

Thank you for editing this one @lpantano!

And a special thanks to the reviewers: @Jessime, @MaximLippeveld !!!!

thanks to everyone who helped with the process and especially the reviewers!

alekseyzimin commented 1 year ago

@alekseyzimin I am the AEiC on this track, and here to help process this work for acceptance in JOSS. I have reviewed the paper and archive and most seems in order, so we can proceed with acceptance. I do have one point below which you should fix at your earliest convenience:

  • [x] Please modify the license listed on your ZENODO archive. It currently refers to a creative commons license, but this should be your software license: GPL-3.0 license.

I will now proceed with to acceptance in JOSS.

Hello @Kevin-Mattheus-Moerman, I updated the license listed on Zenodo Archive.