Closed whedon closed 3 years ago
I had a quick look, seems OK.
@whedon accept deposit=true
Doing it live! Attempting automated processing of paper acceptance...
🐦🐦🐦 👉 Tweet for this paper 👈 🐦🐦🐦
🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨
Here's what you must now do:
Party like you just published a paper! 🎉🌈🦄💃👻🤘
Any issues? Notify your editorial technical team...
Congrats @berenger-eu on your article's publication in JOSS!
Many thanks to @pitsianis, @Himscipy, and @sarats for reviewing this, and @poulson for editing.
: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.02444/status.svg)](https://doi.org/10.21105/joss.02444)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.02444">
<img src="https://joss.theoj.org/papers/10.21105/joss.02444/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.02444/status.svg
:target: https://doi.org/10.21105/joss.02444
This is how it will look in your documentation:
We need your help!
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:
Submitting author: @berenger-eu (Bérenger Bramas) Repository: https://gitlab.inria.fr/bramas/tbfmm Version: v1.0 Editor: @poulson Reviewer: @pitsianis, @Himscipy, @sarats Archive: 10.5281/zenodo.4302384
:warning: JOSS reduced service mode :warning:
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
Status
Status badge code:
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
@pitsianis & @Himscipy & @sarats, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @poulson know.
✨ Please try and complete your review in the next six weeks ✨
Review checklist for @pitsianis
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @Himscipy
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @sarats
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper