Closed whedon closed 7 years ago
Hello human, I'm @whedon. I'm here to help you with some common editorial tasks for JOSS. @alanlivio it looks like you're currently assigned as the reviewer for this paper :tada:.
:star: Important :star:
If you haven't already, you should seriously consider unsubscribing from GitHub notifications for this (https://github.com/openjournals/joss-reviews) repository. As as reviewer, you're probably currently watching this repository which means for GitHub's default behaviour you will receive notifications (emails) for all JOSS reviews 😿
To fix this do the following two things:
For a list of things I can do to help you, just type:
@whedon commands
version updated to v0.6.6
Hello @acabunoc. I finish the review. But I found a problem in the form. I believe that the item " Version: Does the release version given match the GitHub release (v0.5.2)?" should be changed to v0.6.6, right?
@whedon commands
Here are some things you can ask me to do:
# List all of Whedon's capabilities
@whedon commands
# Assign a GitHub user as the reviewer of this submission
@whedon assign @username as reviewer
# List the GitHub usernames of the JOSS editors
@whedon list editors
# List of JOSS reviewers together with programming language preferences and domain expertise
@whedon list reviewers
# Change editorial assignment
@whedon assign @username as editor
# Set the software archive DOI at the top of the issue e.g.
@whedon set 10.0000/zenodo.00000 as archive
# Open the review issue
@whedon start review
:construction: Important :construction:
This is all quite new. Please make sure you check the top of the issue after running a @whedon command (you might also need to refresh the page to see the issue update).
@whedon set 10.5281/zenodo.256850 as archive
I'm sorry @edusantana, I'm afraid I can't do that. That's something only JOSS editors are allowed to do.
Hello @acabunoc. I finish the review. I only see the version problem. How proceed to conclude the review.
Hi @acabunoc Do you need any thing else? An other reviewer?
Thanks for the quick review @alanlivio!
The form is updated. I like how you have an Open Canvas in your docs 😄 .
Once I set the archive we should be good to go! Flagging @arfon 🎏
@whedon set 10.5281/zenodo.256850 as archive
OK. 10.5281/zenodo.256850 is the archive.
Also, @arfon, I manually updated the version number. Not sure if this breaks something behind the scenes.
@acabunoc about the open canvas, I enjoy doing it. Thank you for that. I discovered it looking at your repositories. But this tip was also good, for creating an animated gif.
Thanks for the review here @alanlivio and for editing this submission @acabunoc ✨
@edusantana - your paper is now accepted into JOSS and your DOI is http://dx.doi.org/10.21105/joss.00169 ⚡️ 🚀 💥
Submitting author: @edusantana (Eduardo Alexandre) Repository: https://github.com/abntex/limarka Version: v0.6.6 Editor: @acabunoc Reviewer: @alanlivio Archive: 10.5281/zenodo.256850
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) 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 questions
Conflict of interest
General checks
Functionality
Documentation
Software paper
paper.md
file include a list of authors with their affiliations?