Closed whedon closed 6 years ago
Hello human, I'm @whedon. I'm here to help you with some common editorial tasks.
For a list of things I can do to help you, just type:
@whedon commands
Attempting PDF compilation. Reticulating splines etc...
PDF failed to compile for issue #725 with the following error:
/app/vendor/bundle/ruby/2.3.0/bundler/gems/whedon-a31a5c2a9125/lib/whedon.rb:78:in check_fields': Paper YAML header is missing expected fields: tags (RuntimeError) from /app/vendor/bundle/ruby/2.3.0/bundler/gems/whedon-a31a5c2a9125/lib/whedon.rb:66:in
initialize'
from /app/vendor/bundle/ruby/2.3.0/bundler/gems/whedon-a31a5c2a9125/lib/whedon/processor.rb:29:in new' from /app/vendor/bundle/ruby/2.3.0/bundler/gems/whedon-a31a5c2a9125/lib/whedon/processor.rb:29:in
set_paper'
from /app/vendor/bundle/ruby/2.3.0/bundler/gems/whedon-a31a5c2a9125/bin/whedon:37:in prepare' from /app/vendor/bundle/ruby/2.3.0/gems/thor-0.20.0/lib/thor/command.rb:27:in
run'
from /app/vendor/bundle/ruby/2.3.0/gems/thor-0.20.0/lib/thor/invocation.rb:126:in invoke_command' from /app/vendor/bundle/ruby/2.3.0/gems/thor-0.20.0/lib/thor.rb:387:in
dispatch'
from /app/vendor/bundle/ruby/2.3.0/gems/thor-0.20.0/lib/thor/base.rb:466:in start' from /app/vendor/bundle/ruby/2.3.0/bundler/gems/whedon-a31a5c2a9125/bin/whedon:99:in
<top (required)>'
from /app/vendor/bundle/ruby/2.3.0/bin/whedon:22:in load' from /app/vendor/bundle/ruby/2.3.0/bin/whedon:22:in
@kdpeterson51 - please take a look at the guidelines for the paper structure http://joss.theoj.org/about#paper_structure and update yours accordingly.
In addition, this package doesn't look like it has a README, license etc. You might want to take a look at the reviewer guidelines to see what your package will be evaluated on.
Sincere apologies, Afron.
Tags have been added to YAML header, README and LICENSE files are now up-to-date.
@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 sole reviewer of this submission
@whedon assign @username as reviewer
# Add a GitHub user to the reviewers of this submission
@whedon add @username as reviewer
# Remove a GitHub user from the reviewers of this submission
@whedon remove @username as reviewer
# List of editor GitHub usernames
@whedon list editors
# List of 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
🚧 🚧 🚧 Experimental Whedon features 🚧 🚧 🚧
# Compile the paper
@whedon generate pdf
@whedon generate pdf
Attempting PDF compilation. Reticulating splines etc...
@whedon assign @leeper as editor
OK, the editor is @leeper
Hi, @kdpeterson51. Thanks for your submission. A couple of preliminary things here before we get started:
Can you clarify the license for the functions mentioned in COPYRIGHT? Do you have permission to redistribute this code from the original author? If so, under what license?
It looks like you are generating your R NAMESPACE file by hand rather than through roxygen. Can you delete and reinitialize using devtools::document()
?
Should the vignette be included in a typical /vignettes
directory in the package itself?
Do you have any suggested reviewers for the package?
Hi @leeper. Thank you very much for your assistance.
The copyright was obtained by written permission to use those cited MS Excel spreadsheets.
Original NAMESPACE file has been deleted and replaced with devtools
version.
Vignette folder is now up-to-date within /mbir
folder.
We do not have any suggested reviewers at this time.
Hi @kdpeterson51, thanks for that. Can I request that you update the COPYRIGHT file to clarify that. As you know, JOSS only publishes software that has a complete open source license and the current wording might be confusing in this respect.
Given that the software is a derivative work (rather than a redistribution of the original spreadsheets), I might suggest that you indicate that the copyright applies to the original spreadsheets, permission was granted to create a derivative work (perhaps list a date that written permission was granted), and indicate that the copyright does not apply to any of the actual code in the package.
Would that be acceptable to you?
Your suggestions are appreciated, @leeper. The COPYRIGHT file has been updated to improve the language.
@kellieotto Would you be interested in reviewing this software for JOSS?
@leeper Yes, happy to review this.
@whedon assign @kellieotto as reviewer
OK, the reviewer is @kellieotto
@whedon start review magic-word=bananas
OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/746. Feel free to close this issue now!
@kellieotto Excellent. Thank you! You can find the review issue here: https://github.com/openjournals/joss-reviews/issues/746 Please follow the instructions there, complete the review checklist, and raise any issues questions, or concerns.
Let me know (over there) if you have any questions. Thanks, again!
Submitting author: @kdpeterson51 (Kyle Peterson) Repository: https://github.com/kdpeterson51/mbir Version: 1.3 Editor: @leeper Reviewers: @kellieotto
Author instructions
Thanks for submitting your paper to JOSS @kdpeterson51. The JOSS editor (shown at the top of this issue) will work with you on this issue to find a reviewer for your submission before creating the main review issue.
@kdpeterson51 if you have any suggestions for potential reviewers then please mention them here in this thread. In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission.
Editor instructions
The JOSS submission bot @whedon is here to help you find and assign reviewers and start the main review. To find out what @whedon can do for you type: