search

openjournals / joss-reviews

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

[REVIEW]: Augmenty: A Python Library for Structured Text Augmentation #6370

Closed editorialbot closed 6 months ago

editorialbot commented 9 months ago

Submitting author: !--author-handle-->@KennethEnevoldsen<!--end-author-handle-- (Kenneth C. Enevoldsen) Repository: https://github.com/KennethEnevoldsen/augmenty Branch with paper.md (empty if default branch): Version: joss Editor: !--editor-->@arfon<!--end-editor-- Reviewers: @sap218, @wdduncan Archive: 10.5281/zenodo.11002422

Status

status

Status badge code:

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

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

@sap218 & @wdduncan, 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 @sap218

📝 Checklist for @wdduncan

crvernon commented 6 months ago

@editorialbot set joss as version

editorialbot commented 6 months ago

Done! version is now joss

crvernon commented 6 months ago

@editorialbot set 10.5281/zenodo.11002422 as archive

editorialbot commented 6 months ago

Done! archive is now 10.5281/zenodo.11002422

crvernon commented 6 months ago

:wave: @KennethEnevoldsen - one last thing before we accept...

Could you edit your metadata for the license stated in this archive https://zenodo.org/records/11002422 to match what is used by your package?

No need to do another release, you can just edit the existing record on Zenodo.

Let me know when this is done and I'll move forward with accepting the submission for publications. Thanks!

KennethEnevoldsen commented 6 months ago

@crvernon I have updated the license to match

crvernon commented 6 months ago

@editorialbot accept

editorialbot commented 6 months ago 
Doing it live! Attempting automated processing of paper acceptance...
editorialbot commented 6 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: Enevoldsen given-names: Kenneth orcid: "https://orcid.org/0000-0001-8733-0966" doi: 10.5281/zenodo.11002422 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Enevoldsen given-names: Kenneth orcid: "https://orcid.org/0000-0001-8733-0966" date-published: 2024-04-27 doi: 10.21105/joss.06370 issn: 2475-9066 issue: 96 journal: Journal of Open Source Software publisher: name: Open Journals start: 6370 title: "Augmenty: A Python Library for Structured Text Augmentation" type: article url: "https://joss.theoj.org/papers/10.21105/joss.06370" volume: 9 title: "Augmenty: A Python Library for Structured Text Augmentation" ```

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

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

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

crvernon commented 6 months ago

Congratulations on your new publication @KennethEnevoldsen! Many thanks to @arfon and to reviewers @sap218 and @wdduncan for your time, hard work, and expertise!! JOSS wouldn't be able to function nor succeed without your efforts.

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

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

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

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:

KennethEnevoldsen commented 6 months ago

Thanks @crvernon, @arfon and the reviewers @wdduncan and @sap218 - very happy about the feedback always a good experience to publish with joss