openjournals / joss-reviews

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

[REVIEW]: MOLE: Mimetic Operators Library Enhanced #6288

Closed editorialbot closed 3 months ago

editorialbot commented 9 months ago

Submitting author: !--author-handle-->@jcorbino<!--end-author-handle-- (Johnny Corbino) Repository: https://github.com/jcorbino/mole Branch with paper.md (empty if default branch): Version: v1.0 Editor: !--editor-->@jedbrown<!--end-editor-- Reviewers: @jakelangham, @victorapm Archive: 10.5281/zenodo.12752946

Status

status

Status badge code:

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

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

@jakelangham & @victorapm, 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 @jedbrown 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 @jakelangham

📝 Checklist for @victorapm

editorialbot commented 3 months ago
Doing it live! Attempting automated processing of paper acceptance...
editorialbot commented 3 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: Corbino given-names: Johnny orcid: "https://orcid.org/0000-0002-2638-9216" - family-names: Dumett given-names: Miguel A. - family-names: Castillo given-names: Jose E. contact: - family-names: Corbino given-names: Johnny orcid: "https://orcid.org/0000-0002-2638-9216" doi: 10.5281/zenodo.12752946 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Corbino given-names: Johnny orcid: "https://orcid.org/0000-0002-2638-9216" - family-names: Dumett given-names: Miguel A. - family-names: Castillo given-names: Jose E. date-published: 2024-07-17 doi: 10.21105/joss.06288 issn: 2475-9066 issue: 99 journal: Journal of Open Source Software publisher: name: Open Journals start: 6288 title: "MOLE: Mimetic Operators Library Enhanced" type: article url: "https://joss.theoj.org/papers/10.21105/joss.06288" volume: 9 title: "MOLE: Mimetic Operators Library Enhanced" ```

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

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

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/5644
  2. Wait five minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.06288
  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 @jcorbino (Johnny Corbino) and co-authors on your publication!!

And thanks to @jakelangham and @victorapm for reviewing, and to @jedbrown for editing! JOSS depends on volunteers and wouldn't be successful 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.06288/status.svg)](https://doi.org/10.21105/joss.06288)

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

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

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:

jcorbino commented 3 months ago

Thank you @danielskatz , @jedbrown , @victorapm , @jakelangham for all the good discussions and suggestions. We appreciate it! We will follow the instructions from the editorialbot and "Party like we just published a paper" 👍🏻

victorapm commented 3 months ago

Sure! Congrats, Johnny!