Joss-reviews: [PRE REVIEW]: PyUnfold: A Python Package for Iterative Unfolding

Created on 16 May 2018  路  26Comments  路  Source: openjournals/joss-reviews

Submitting author: @zhampel (Zigfried Hampel-arias)
Repository: https://github.com/jrbourbeau/pyunfold
Version: v0.3
Editor: @lheagy
Reviewers: @juliohm, @benjaminrose

Author instructions

Thanks for submitting your paper to JOSS @zhampel. 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.

@zhampel 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:

@whedon commands
Makefile Python Shell pre-review

Most helpful comment

Thank you @zhampel for pinging, I would be happy to review the submission. This next week I will be in a conference in Colorado with limited free time, is there a problem if I take a look at it two weeks from now?

If you need the review to be quicker because of colleagues wanting to cite your work, please let me know. No problem at all if you'd prefer to have someone else reviewing it earlier.

All 26 comments

Hello human, I'm @whedon. I'm here to help you with some common editorial tasks. @lheagy it looks like you're currently assigned as the editor for this paper :tada:

For a list of things I can do to help you, just type:

@whedon commands
Attempting PDF compilation. Reticulating splines etc...

:wave: @lheagy - the submitting author suggested you as the handling editor.

Thanks @arfon, I am happy to take this

Thanks @arfon, I am happy to take this

Thanks!

Hi @zhampel, thanks for your submission! Do you have any recommendations for reviewers? Ideally, we find 2.

Perhaps @rowanc1 is interested in being a reviewer?

Thanks for the suggestion, cursory glance through things looks cool. :) Unfortunately, I won't be able to realistically look at this until late July. You might be able to find someone else, or I can aim for that time frame. Let me know!

Perhaps @juliohm or @benjaminrose are interested/available as reviewers?

@betatim also seems like a good potential reviewer. Are you interested/available to review?

Thank you @zhampel for pinging, I would be happy to review the submission. This next week I will be in a conference in Colorado with limited free time, is there a problem if I take a look at it two weeks from now?

If you need the review to be quicker because of colleagues wanting to cite your work, please let me know. No problem at all if you'd prefer to have someone else reviewing it earlier.

@juliohm Yeah I think that time frame seems OK. @jrbourbeau that's good for you as well yes? @lheagy, should we still search for another reviewer or is this good to get started?

The time frame laid out by @juliohm is totally fine with me. Thank you @juliohm for agreeing to be a reviewer!

Thank you @zhampel for considering me. I am also able to review this submission. I too am busy this through early next week, but I can review it on a similar time scale as @juliohm.

Thanks @juliohm and @benjaminrose for agreeing to review!

@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 assign @juliohm as reviewer

OK, the reviewer is @juliohm

@whedon add @benjaminrose as reviewer

OK, @benjaminrose is now a reviewer

@whedon start review

You didn't say the magic word! Try this:

@whedon start review magic-word=bananas

@whedon start review magic-word=bananas

OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/741. Feel free to close this issue now!

Was this page helpful?
0 / 5 - 0 ratings