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]: Launcher: A simple tool for executing high throughput computing workloads #286

Closed
whedon opened this issue Jun 8, 2017 · 15 comments
Assignees

Comments

@whedon
Copy link

whedon commented Jun 8, 2017

Submitting author: @lwilson (Lucas Wilson)
Repository: https://github.com/TACC/launcher
Version: v3.1
Editor: @danielskatz
Reviewer: @kc9qey

Author instructions

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

@lwilson 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 Jun 8, 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

@danielskatz
Copy link

@whedon assign @danielskatz as editor

@whedon
Copy link
Author

whedon commented Jun 8, 2017

OK, the editor is @danielskatz

@danielskatz
Copy link

@kc9qey - would you be willing to review this submission for JOSS?

@kc9qey
Copy link

kc9qey commented Jun 8, 2017 via email

@danielskatz
Copy link

@whedon assign @kc9qey as reviewer

@whedon
Copy link
Author

whedon commented Jun 8, 2017

OK, the reviewer is @kc9qey

@danielskatz
Copy link

@whedon commands
tell me about how I phrase the "secret" banana again?

@whedon
Copy link
Author

whedon commented Jun 8, 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 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

🚧 Important 🚧

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

@danielskatz
Copy link

@whedon start review
but what about the banana?

@whedon
Copy link
Author

whedon commented Jun 8, 2017

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

@whedon start review magic-word=bananas

@danielskatz
Copy link

@whedon start review magic-word=bananas
I can't figure out how anyone benefits from this bananas thingee

@whedon
Copy link
Author

whedon commented Jun 8, 2017

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

@whedon start review magic-word=bananas

@danielskatz
Copy link

@whedon start review magic-word=bananas

@whedon
Copy link
Author

whedon commented Jun 8, 2017

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

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

3 participants