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]: WhaleMap: a tool to collate and display whale survey results in near real-time #3047

Closed
whedon opened this issue Feb 20, 2021 · 32 comments

Comments

@whedon
Copy link

whedon commented Feb 20, 2021

Submitting author: @hansenjohnson (Hansen Johnson)
Repository: https://github.com/hansenjohnson/WhaleMap
Version: v1.0.0
Editor: @KristinaRiemer
Reviewers: @pjbouchet, @mcsiple
Managing EiC: Kevin M. Moerman

⚠️ JOSS reduced service mode ⚠️

Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.

Author instructions

Thanks for submitting your paper to JOSS @hansenjohnson. Currently, there isn't an JOSS editor assigned to your paper.

@hansenjohnson if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission (please start at the bottom of the list).

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 Feb 20, 2021

Hello human, I'm @whedon, a robot that can help you with some common editorial tasks.

⚠️ JOSS reduced service mode ⚠️

Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.

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

@whedon commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@whedon generate pdf

@whedon
Copy link
Author

whedon commented Feb 20, 2021

Failed to discover a Statement of need section in paper

@whedon
Copy link
Author

whedon commented Feb 20, 2021

Software report (experimental):

github.com/AlDanial/cloc v 1.88  T=0.29 s (401.5 files/s, 49296.9 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
R                               99           3379           3328           5961
make                             1             97            105            446
Bourne Shell                    12             84             93            240
Markdown                         3             76              0            229
Rmd                              1             71             89            144
TeX                              1              1              0             22
-------------------------------------------------------------------------------
SUM:                           117           3708           3615           7042
-------------------------------------------------------------------------------


Statistical information for the repository '6ef6b0d3ad106134a17acf8a' was
gathered on 2021/02/20.
No commited files with the specified extensions were found.

@whedon
Copy link
Author

whedon commented Feb 20, 2021

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1121/10.0001811 is OK
- 10.1111/csp2.267 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@whedon
Copy link
Author

whedon commented Feb 20, 2021

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

@Kevin-Mattheus-Moerman
Copy link
Member

@hansenjohnson thanks for this submission. Our system detected the paper currently lacks a Statement of need section which is required. Can you add such a section to you paper? It should illustrate the research purpose of the software.

@Kevin-Mattheus-Moerman
Copy link
Member

Notes for handling editor, this work seems to relate to these papers:
#1825
#2097
#2172

@Kevin-Mattheus-Moerman
Copy link
Member

@KristinaRiemer @karthik @marcosvital @jni could one of you handle this submission? Note there are some related papers ☝️ which might help to find reviewers too.

@hansenjohnson
Copy link

Thank you @Kevin-Mattheus-Moerman! I made some very slight changes to explicitly include a Statement of need section. Sorry for omitting that in the first place!

@hansenjohnson
Copy link

@whedon commands

@whedon
Copy link
Author

whedon commented Feb 22, 2021

Here are some things you can ask me to do:

# List Whedon's capabilities
@whedon commands

# List of editor GitHub usernames
@whedon list editors

# List of reviewers together with programming language preferences and domain expertise
@whedon list reviewers

EDITORIAL TASKS

# Compile the paper
@whedon generate pdf

# Compile the paper from alternative branch
@whedon generate pdf from branch custom-branch-name

# Ask Whedon to check the references for missing DOIs
@whedon check references

# Ask Whedon to check repository statistics for the submitted software
@whedon check repository

@hansenjohnson
Copy link

@whedon generate pdf

@whedon
Copy link
Author

whedon commented Feb 22, 2021

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

@Kevin-Mattheus-Moerman
Copy link
Member

@KristinaRiemer @karthik @marcosvital @jni @kthyng could one of you handle this submission? Note these are some related papers which might help to find reviewers too:
#1825
#2097
#2172

@kthyng
Copy link

kthyng commented Feb 25, 2021

Hi @hansenjohnson and thanks for your submission. It looks like a really interesting project! I am going to ping the editorial board to make sure that it is in scope before we move forward. This isn't a statement on how awesome your project is, but just to check for fit. This will take 1-2 weeks and someone will get back to you. Thanks for your patience.

@kthyng
Copy link

kthyng commented Feb 25, 2021

@whedon query scope

@whedon whedon added the query-scope Submissions of uncertain scope for JOSS label Feb 25, 2021
@whedon
Copy link
Author

whedon commented Feb 25, 2021

Submission flagged for editorial review.

@hansenjohnson
Copy link

Thank you @kthyng! I recognize this is a bit of an odd submission and think a scope query is a great place to start. I look forward to hearing from the team. Much appreciated!

@danielskatz
Copy link

This submission has been determined to be in-scope

@danielskatz danielskatz removed the query-scope Submissions of uncertain scope for JOSS label Mar 2, 2021
@danielskatz
Copy link

👋 @KristinaRiemer - you were suggested as the editor for this submission. Are you able to take it on?

@danielskatz
Copy link

@whedon invite @KristinaRiemer as editor

@whedon
Copy link
Author

whedon commented Mar 2, 2021

@KristinaRiemer has been invited to edit this submission.

@KristinaRiemer
Copy link

Hi, yes, I'm able to take care of this submission. (I had accidentally turned off GitHub notifications for this repo 🤦‍♀️)

@KristinaRiemer
Copy link

@whedon assign me as editor

@whedon
Copy link
Author

whedon commented Mar 3, 2021

OK, the editor is @KristinaRiemer

@KristinaRiemer
Copy link

@whedon assign @pjbouchet as reviewer

@whedon
Copy link
Author

whedon commented Mar 9, 2021

OK, @pjbouchet is now a reviewer

@KristinaRiemer
Copy link

@whedon add @mcsiple as reviewer

@whedon
Copy link
Author

whedon commented Mar 9, 2021

OK, @mcsiple is now a reviewer

@KristinaRiemer
Copy link

@whedon start review

@whedon
Copy link
Author

whedon commented Mar 9, 2021

OK, I've started the review over in #3094.

@whedon whedon closed this as completed Mar 9, 2021
@KristinaRiemer
Copy link

Thanks to @pjbouchet and @mcsiple for agreeing to review this submission! The review will happen in the GitHub issue linked to above. Feel free to ask me questions there! Use the checklist as a guide for your review, and file issues in the submission repo to suggest improvements.

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