Closed whedon closed 4 years ago
π¦π¦π¦ π 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...
@ResidentMario, @martinfleis - many thanks for your reviews here and to @leouieda for editing this submission β¨
@slumnitz - your paper is now accepted into JOSS :zap::rocket::boom:
: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.01882/status.svg)](https://doi.org/10.21105/joss.01882)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.01882">
<img src="https://joss.theoj.org/papers/10.21105/joss.01882/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.01882/status.svg
:target: https://doi.org/10.21105/joss.01882
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:
Thank you for your help and support @leouieda, @martinfleis, @ResidentMario and @arfon.
@slumnitz congratulations on the publication! Huge thanks to @martinfleis and @ResidentMario for the reviews and @arfon for picking up where I left off (apologies for the disappearance).
Submitting author: @slumnitz (Stefanie Lumnitz) Repository: https://github.com/pysal/splot Version: v1.1.1 Editor: @leouieda Reviewer: @ResidentMario, @martinfleis Archive: 10.5281/zenodo.3724199
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
@ResidentMario & @martinfleis, 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 @leouieda know.
β¨ Please try and complete your review in the next two weeks β¨
Review checklist for @ResidentMario
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @martinfleis
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper