[REVIEW]: Trash AI: A Web GUI for Serverless Computer Vision Analysis of Images of Trash

[editorialbot]

Submitting author: !--author-handle-->@wincowgerDEV<!--end-author-handle-- (Win Cowger) Repository: https://github.com/code4sac/trash-ai Branch with paper.md (empty if default branch): Version: 1.0 Editor: !--editor-->@arfon<!--end-editor-- Reviewers: @domna, @luxaritas Archive: 10.5281/zenodo.8384126

Status

Status badge code:

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

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

@domna & @luxaritas, 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 @arfon 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 @domna

📝 Checklist for @luxaritas

[editorialbot]

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

[arfon]

@wincowgerDEV – can you please merge this PR? https://github.com/code4sac/trash-ai/pull/192

[arfon]

@editorialbot recommend-accept

[editorialbot]

Attempting dry run of processing paper acceptance...

[editorialbot]

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.5281/zenodo.4154370 is OK
- 10.1186/s43591-022-00035-1 is OK
- 10.1029/2019EA000960 is OK
- 10.1186/s40965-018-0050-y is OK
- 10.1016/j.wasman.2021.12.001 is OK
- 10.48550/ARXIV.2003.06975 is OK

MISSING DOIs

- None

INVALID DOIs

- None

[editorialbot]

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

[arfon]

@editorialbot accept

[editorialbot]

Doing it live! Attempting automated processing of paper acceptance...

[editorialbot]

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: Cowger given-names: Win orcid: "https://orcid.org/0000-0001-9226-3104" - family-names: Hollingsworth given-names: Steven - family-names: Fey given-names: Day - family-names: Norris given-names: Mary C - family-names: Yu given-names: Walter - family-names: Kerge given-names: Kristiina - family-names: Haamer given-names: Kris - family-names: Durante given-names: Gina - family-names: Hernandez given-names: Brianda contact: - family-names: Hollingsworth given-names: Steven doi: 10.5281/zenodo.8384126 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Cowger given-names: Win orcid: "https://orcid.org/0000-0001-9226-3104" - family-names: Hollingsworth given-names: Steven - family-names: Fey given-names: Day - family-names: Norris given-names: Mary C - family-names: Yu given-names: Walter - family-names: Kerge given-names: Kristiina - family-names: Haamer given-names: Kris - family-names: Durante given-names: Gina - family-names: Hernandez given-names: Brianda date-published: 2023-09-29 doi: 10.21105/joss.05136 issn: 2475-9066 issue: 89 journal: Journal of Open Source Software publisher: name: Open Journals start: 5136 title: "Trash AI: A Web GUI for Serverless Computer Vision Analysis of Images of Trash" type: article url: "https://joss.theoj.org/papers/10.21105/joss.05136" volume: 8 title: "Trash AI: A Web GUI for Serverless Computer Vision Analysis of Images of Trash" ```

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]

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

[editorialbot]

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

Here's what you must now do:

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

Any issues? Notify your editorial technical team...

[arfon]

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

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

[editorialbot]

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

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

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

This is how it will look in your documentation:

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:

• Volunteering to review for us sometime in the future. You can add your name to the reviewer list here: https://reviewers.joss.theoj.org/join
• Making a small donation to support our running costs here: https://numfocus.org/donate-to-joss

[wincowgerDEV]

Wonderful! Thank you so much @arfon, @luxaritas, and @domna for all your hard work helping us bring this project to life.

[domna]

Congrats 🎉 I was happy to review this nice project! Good luck with your software in the future. I hope the publication gives you some additional reach for your research!