search

openjournals / joss-reviews

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

[REVIEW]: PowerAPI: A toolkit for estimating power consumption of software #6670

Closed editorialbot closed 3 months ago

editorialbot commented 5 months ago

Submitting author: !--author-handle-->@roda82<!--end-author-handle-- (Daniel Romero Acero) Repository: https://github.com/powerapi-ng/powerapi Branch with paper.md (empty if default branch): joss-paper Version: v2.7.0 Editor: !--editor-->@danielskatz<!--end-editor-- Reviewers: @varshaprasad96, @EpicStep Archive: 10.5281/zenodo.11453194

Status

status

Status badge code:

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

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

@varshaprasad96 & @EpicStep, 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 @danielskatz 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 @EpicStep

šŸ“ Checklist for @varshaprasad96

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

danielskatz commented 3 months ago

Congratulations to @roda82 (Daniel Romero Acero) and co-authors on your publication!!

And thanks to @varshaprasad96 and @EpicStep for reviewing! JOSS depends on volunteers and we couldn't do this without you.

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

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

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

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: