Closed editorialbot closed 1 year ago
:wave: @openjournals/sbcs-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/4218, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@editorialbot accept
Doing it live! Attempting automated processing of paper acceptance...
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:
``` cff-version: "1.2.0" authors: - family-names: Leeuw given-names: Joshua R. name-particle: de orcid: "https://orcid.org/0000-0003-4815-2364" - family-names: Gilbert given-names: Rebecca A. orcid: "https://orcid.org/0000-0003-4574-7792" - family-names: Luchterhandt given-names: BjΓΆrn orcid: "https://orcid.org/0000-0002-9225-2787" contact: - family-names: Leeuw given-names: Joshua R. name-particle: de orcid: "https://orcid.org/0000-0003-4815-2364" doi: 10.5281/zenodo.7702307 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Leeuw given-names: Joshua R. name-particle: de orcid: "https://orcid.org/0000-0003-4815-2364" - family-names: Gilbert given-names: Rebecca A. orcid: "https://orcid.org/0000-0003-4574-7792" - family-names: Luchterhandt given-names: BjΓΆrn orcid: "https://orcid.org/0000-0002-9225-2787" date-published: 2023-05-11 doi: 10.21105/joss.05351 issn: 2475-9066 issue: 85 journal: Journal of Open Source Software publisher: name: Open Journals start: 5351 title: "jsPsych: Enabling an Open-Source Collaborative Ecosystem of Behavioral Experiments" type: article url: "https://joss.theoj.org/papers/10.21105/joss.05351" volume: 8 title: "jsPsych: Enabling an Open-Source Collaborative Ecosystem of Behavioral Experiments" ```
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.
π¦π¦π¦ π Tweet for this paper π π¦π¦π¦
πππ π Toot for this paper π πππ
π¨π¨π¨ THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! π¨π¨π¨
Here's what you must now do:
Any issues? Notify your editorial technical team...
Congrats! @jodeleeuw
Sorry for going AWOL, I had a super ad migraine.
Big thank you to the reviewers @pmcharrison, @xinyiguan, @chartgerink! And congratulations @jodeleeuw! π₯³
: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.05351/status.svg)](https://doi.org/10.21105/joss.05351)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.05351">
<img src="https://joss.theoj.org/papers/10.21105/joss.05351/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.05351/status.svg
:target: https://doi.org/10.21105/joss.05351
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:
Submitting author: !--author-handle-->@jodeleeuw<!--end-author-handle-- (Joshua de Leeuw) Repository: https://github.com/jspsych/jspsych Branch with paper.md (empty if default branch): joss-paper Version: v7.3.2 Editor: !--editor-->@oliviaguest<!--end-editor-- Reviewers: @pmcharrison, @xinyiguan, @chartgerink Archive: 10.5281/zenodo.7702307
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
@pmcharrison & @xinyiguan & @chartgerink, 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:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @oliviaguest 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 @xinyiguan
π Checklist for @chartgerink
π Checklist for @pmcharrison