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]: ggalluvial: Layered Grammar for Alluvial Plots #1937
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @akeshavan it looks like you're currently assigned as the editor for this paper 🎉 For a list of things I can do to help you, just type:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
What happens now? This submission is currently in a You can help the editor by looking at this list of potential reviewers to identify individuals who might be able to review your submission (please start at the bottom of the list). Also, feel free to suggest individuals who are not on this list by mentioning their GitHub handles here. |
|
|
Failed to discover a valid open source license. |
|
👋 @akeshavan - sorry, I assigned this to you while starting the process without checking with you first. Are you willing to edit this submission? |
👋 @corybrunson - this submission needs a license - please add a plain text LICENSE file with the OSI-approved license that you are using for the software (which I think is GPL-3). |
Also, please check to see if the missing DOI whedon suggests is correct, and if so, add it to the .bib file. (Whedon suggestions are just suggestions, and sometimes they are wrong.) |
@danielskatz thank you! I've added the missing DOI. To be sure, is it good practice to simply put the standard GPLv3 license text (file name |
@whedon generate pdf |
|
Yes, and if there are any deviations, you have changed the license to a non-OSI-approved one, which would mean that JOSS would not consider the submission. |
Right, thank you for pointing that out. In a moment i'll push the Markdown GPLv3 obtained from here, renamed |
not LICENSE.md but LICENSE |
Thank you, this has been changed (using the plain text version of GPLv3). |
From the list of potential reviewers, @kellieotto, @njtierney, and @clauswilke seem to have very relevant expertise and interests. |
Happy to provide a review, when would you like it completed? The end of the year is looming and I'm not sure if I could get it completed before December 20, but can try. |
👋 @akeshavan - sorry, I assigned this to you while starting the process without checking with you first. Are you willing to edit this submission? (we already have one potential reviewer who has agreed...) |
hi @danielskatz , sorry I only just saw this! happy to review. @njtierney no worries, I know everyone is busy during the holidays! Can we plan for sometime in January? |
👋 @kellieotto and @clauswilke -- I know you are busy with holidays now, but would you be interested in reviewing this submission in January? |
I can do a review. Please send a reminder in early Jan. if I haven't done it by then. |
Hello! Sorry I haven't managed this yet, I am aiming for the end of Jan, if that is alright? |
Thank you all! @akeshavan is there anything i need to do before the review begins? (I have made some slight edits to the paper.) @whedon generate pdf |
@whedon generate pdf |
|
Hi @corybrunson - whedon commands have to be the start of a comment, like the following |
ah, you also figured this out - never mind... |
@whedon assign @clauswilke as reviewer |
OK, @clauswilke is now a reviewer |
@whedon add @njtierney as reviewer |
OK, @njtierney is now a reviewer |
hi @corybrunson , @njtierney and @clauswilke -- now that holidays are over, I'm moving this to the review stage. Thanks for your patience! |
@whedon start review |
OK, I've started the review over in #2017. Feel free to close this issue now! |
Submitting author: @corybrunson (Jason Cory Brunson)
Repository: https://github.com/corybrunson/ggalluvial
Version: v0.11.1
Editor: @akeshavan
Reviewers: @clauswilke, @njtierney
Author instructions
Thanks for submitting your paper to JOSS @corybrunson. The JOSS editor @akeshavan, will work with you on this issue to find a reviewer for your submission before creating the main review issue.
@corybrunson 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:
The text was updated successfully, but these errors were encountered: