Closed whedon closed 5 months ago
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @jpsamaroo, @timholy it looks like you're currently assigned to review this paper :tada:.
: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.
:star: Important :star:
If you haven't already, you should seriously consider unsubscribing from GitHub notifications for this (https://github.com/JuliaCon/proceedings-review) repository. As a reviewer, you're probably currently watching this repository which means for GitHub's default behaviour you will receive notifications (emails) for all reviews 😿
To fix this do the following two things:
For a list of things I can do to help you, just type:
@whedon commands
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
@whedon generate pdf
PDF failed to compile for issue #127 with the following error:
Can't find any papers to compile :-(
already compiled pdf is in paper folder https://github.com/jakubMitura14/MedPipe3D.jl/blob/master/paper/test.pdf
:wave: @timholy, please update us on how your review is going (this is an automated reminder).
:wave: @jpsamaroo, please update us on how your review is going (this is an automated reminder).
:wave: @jpsamaroo, please update us on how your review is going (this is an automated reminder).
:wave: @timholy, please update us on how your review is going (this is an automated reminder).
I just tried to get started on this, but when I clicked on the invitation, it says
Sorry, we couldn't find that repository invitation. It is possible that the invitation was revoked or that you are not logged into the invited account.
I only have one GitHub account.
@whedon assign omlins as editor
@whedon generate pdf
PDF failed to compile for issue #127 with the following error:
Can't find any papers to compile :-(
@jakubMitura14 did you modify something on the paper
folder compared to the submission template?
@timholy are you able to tick the boxes on the first comment of the issue? If this is the case it will be sufficient to go through with the review
@jakubMitura14 please use the template paper
folder form https://github.com/JuliaCon/JuliaConSubmission.jl, the submission should work then
Hello thanks for a tip, as I see there are some problems I had at least for that moment withdrawn the paper, still thank You!
@jakubMitura14, in order to avoid any misunderstandings, do we understand right that you would like to withdraw this submission (in which case this issue will be closed) and potentially resubmit anew at a later time?
Yes
@whedon assign @omlins as editor
I'm sorry @omlins, I'm afraid I can't do that. That's something only editors are allowed to do.
@whedon assign @omlins as editor
@whedon commands
My name is now @editorialbot
@editorialbot commands
Hello @luraess, here are the things you can ask me to do:
# List all available commands
@editorialbot commands
# Add to this issue's reviewers list
@editorialbot add @username as reviewer
# Remove from this issue's reviewers list
@editorialbot remove @username from reviewers
# Get a list of all editors's GitHub handles
@editorialbot list editors
# Assign a user as the editor of this submission
@editorialbot assign @username as editor
# Remove the editor assigned to this submission
@editorialbot remove editor
# Remind an author, a reviewer or the editor to return to a review after a
# certain period of time (supported units days and weeks)
@editorialbot remind @reviewer in 2 weeks
# Adds a checklist for the reviewer using this command
@editorialbot generate my checklist
# Set a value for version
@editorialbot set v1.0.0 as version
# Set a value for branch
@editorialbot set juliacon-paper as branch
# Set a value for repository
@editorialbot set https://github.com/organization/repo as repository
# Set a value for the archive DOI
@editorialbot set set 10.5281/zenodo.6861996 as archive
# Mention the EiCs for the correct track
@editorialbot ping track-eic
# Reject paper
@editorialbot reject
# Withdraw paper
@editorialbot withdraw
# Invite an editor to edit a submission (sending them an email)
@editorialbot invite @(.*) as editor
# Run checks and provide information on the repository and the paper file
@editorialbot check repository
# Check the references of the paper for missing DOIs
@editorialbot check references
# Generates the pdf paper
@editorialbot generate pdf
# Recommends the submission for acceptance
@editorialbot recommend-accept
# Accept and publish the paper
@editorialbot accept
# Update data on an accepted/published paper
@editorialbot reaccept
# Generates a LaTeX preprint file
@editorialbot generate preprint
# Flag submission with questionable scope
@editorialbot query scope
# Get a link to the complete list of reviewers
@editorialbot list reviewers
# Creates a post-review checklist with editor and authors tasks
@editorialbot create post-review checklist
# Open the review issue
@editorialbot start review
Yes
I am thus finalising the withdrawal of the paper.
@editorialbot withdraw
There was a problem withdrawing the paper.
@editorialbot reject
There was a problem rejecting the paper.
Closing this now manually given there are issues with the bot.
@editorialbot reject
Paper rejected.
Submitting author: !--author-handle-->@jakubMitura14<!--end-author-handle-- (Jakub Mitura) Repository: Branch with paper.md (empty if default branch): Version: Editor: !--editor-->@omlins<!--end-editor-- Reviewers: @jpsamaroo, @timholy Archive: Pending
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
@jpsamaroo & @timholy, 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 @vchuravy 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 ✨
Review checklist for @jpsamaroo
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Paper format
paper.tex
file include a list of authors with their affiliations?Content
[ ] Context: is the scientific context motivating the work correctly presented?
[ ] Methodology: is the approach taken in the work justified, presented with enough details and reference to reproduce it?
[ ] Results: are the results presented and compared to approaches with similar goals?
Review checklist for @timholy
Conflict of interest
[ ] As the reviewer I confirm that I have read the JuliaCon conflict of interest policy and that there are no conflicts of interest for me to review this work.
Code of Conduct
General checks
Functionality
Documentation
Paper format
paper.tex
file include a list of authors with their affiliations?Content