Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PRE REVIEW]: PFEIFER: Preprocessing Framework of Electrograms Intermittently Fiducialized from Experimental Recordings #446

Closed
whedon opened this issue Nov 1, 2017 · 29 comments
Assignees

Comments

@whedon
Copy link

whedon commented Nov 1, 2017

Submitting author: @bzenger (Brian Zenger)
Repository: https://github.com/SCIInstitute/PFEIFER
Version: v1.0.0
Editor: @Kevin-Mattheus-Moerman
Reviewer: @CristianaCorsi

Author instructions

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

@bzenger 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
@whedon
Copy link
Author

whedon commented Nov 1, 2017

Hello human, I'm @whedon. I'm here to help you with some common editorial tasks for JOSS.

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

@whedon commands

@bzenger
Copy link

bzenger commented Nov 3, 2017

Hi, we would like to suggest the following reviewers for our JOSS submission.

Thanks.

@Kevin-Mattheus-Moerman, @cMadan, @nirum

@bzenger
Copy link

bzenger commented Nov 17, 2017

Hi @arfon,

Is there anything else we need to do to get an editor assigned?

Thanks

@arfon
Copy link
Member

arfon commented Nov 17, 2017

Is there anything else we need to do to get an editor assigned?

Not right now. We need one of the JOSS editors to volunteer to edit this submission (which they've not yet done so).

Sorry for the delay.

@nirum
Copy link

nirum commented Nov 17, 2017 via email

@arfon
Copy link
Member

arfon commented Nov 18, 2017

@whedon commands

@whedon
Copy link
Author

whedon commented Nov 18, 2017

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 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

@bzenger
Copy link

bzenger commented Nov 18, 2017

@arfon thanks for the info and the response. Let us know if anything comes up.

@arfon
Copy link
Member

arfon commented Nov 20, 2017

@Kevin-Mattheus-Moerman @cMadan - would either of you be willing to edit this submission for JOSS? I realize it's a little out of any of our expertise areas but we could look at getting an additional reviewer to help here.

@Kevin-Mattheus-Moerman
Copy link
Member

I can help sure I'll take this one

@Kevin-Mattheus-Moerman
Copy link
Member

@whedon assign @Kevin-Mattheus-Moerman as editot

@Kevin-Mattheus-Moerman
Copy link
Member

@whedon assign @Kevin-Mattheus-Moerman as editor

1 similar comment
@arfon
Copy link
Member

arfon commented Nov 20, 2017

@whedon assign @Kevin-Mattheus-Moerman as editor

@whedon
Copy link
Author

whedon commented Nov 20, 2017

OK, the editor is @Kevin-Mattheus-Moerman

@bzenger
Copy link

bzenger commented Nov 20, 2017

@arfon @Kevin-Mattheus-Moerman Thank you so much for your work on this. Please let us know if we can help by recommending possible external reviewers.

@Kevin-Mattheus-Moerman
Copy link
Member

@bzenger please feel free to recommend reviewers. Recommend them by tagging them in a post with their github handles. Thanks

@bzenger
Copy link

bzenger commented Nov 22, 2017

@Kevin-Mattheus-Moerman thanks we have a possible reviewer @CristianaCorsi​. Let us know if there is anything else we need to do.

@Kevin-Mattheus-Moerman
Copy link
Member

Thanks. @CristianaCorsi you have been suggested as potential reviewer. If you are interested in reviewing can you please share​ your full name and perhaps a link to a professional (e.g. institutional) page? I ask this for verification and to learn about your affiliation/status/experience since your GitHub profile seems brand new and is currently empty.

@CristianaCorsi
Copy link

CristianaCorsi commented Nov 23, 2017 via email

@Kevin-Mattheus-Moerman
Copy link
Member

Great thanks. @CristianaCorsi

@Kevin-Mattheus-Moerman
Copy link
Member

@whedon assign @CristianaCorsi as reviewer

@Kevin-Mattheus-Moerman
Copy link
Member

@whedon start review

@whedon
Copy link
Author

whedon commented Nov 26, 2017

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

@whedon start review magic-word=bananas

@Kevin-Mattheus-Moerman
Copy link
Member

@whedon start review magic-word=bananas

@Kevin-Mattheus-Moerman
Copy link
Member

@whedon assign @CristianaCorsi as reviewer

@whedon
Copy link
Author

whedon commented Nov 27, 2017

OK, the reviewer is @CristianaCorsi

@Kevin-Mattheus-Moerman
Copy link
Member

@whedon start review magic-word=bananas

@whedon
Copy link
Author

whedon commented Nov 27, 2017

OK, I've started the review over in #472. Feel free to close this issue now!

@Kevin-Mattheus-Moerman
Copy link
Member

@bzenger @CristianaCorsi I've started the review issue see #472.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants