-
-
Notifications
You must be signed in to change notification settings - Fork 38
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]: NetworkSedimentTransporter: A Landlab submodule for bed material transport through river networks #2199
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. 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:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
|
|
@kbarnhart, @openjournals/dev - Do you know the typical setup for reviewing a landlab module? I would like the statistics above to show the number of lines for just this submission (https://github.com/landlab/landlab/tree/master/landlab/components/network_sediment_transporter). Somehow it did find the correct paper — those move to be elsewhere when they aren't being reviewed. |
@kthyng I can provide some info. I first note that I am an author on this submission. Most Landlab component submissions to JOSS (all, I think) have three parts: component source code, tests, and example notebooks. Each live in a separate location in the Landlab repository. In the case of this specific contribution the content is located at:
Perhaps run cloc on this set of folders? re finding the right paper: yes, there is only one paper.md, the prior submissions were renamed to address this issue. The only thing that is really different about the review process for a landlab component (as compared with a typical submission in which the entire repository is the focus of review)... the reviewers need to be reminded that the scope of the review is not the entire repo. Obviously there are some whole-package things that get reviewed (install instructions, docs, contributing, etc). Let me know if there are aspects of your question that I haven't addressed. |
@kthyng will you be handling this submission as editor? |
Sorry for my delay, all. yes, I will handle this and will be able to address it in the next few days. |
OK, the editor is @kthyng |
@openjournals/dev Might it be possible in the future to run |
@kbarnhart Thanks so much for the info. |
For reference, I am going to paste in the
|
@pfeiffea I just read your personal description on github and it made me happy. Sorry for my delay, getting work done right now is slow going. Could you look at this list and give a handful of suggestions for reviewers? Please don't @ them so that they aren't specifically mentioned, just give their github handle, like kthyng for me. https://bit.ly/joss-reviewers |
Glad the description brought a smile @kthyng -- those feel extra needed right now. No worries on delay. Potential reviewers: |
@pfeiffea I should say you are welcome to suggest other reviewers too. I'll check them out tomorrow. |
Good idea. I've added this as a possible enhancement in openjournals/whedon-api#101 |
Hi @zsylvester and @ebgoldstein! Are you willing and interested in reviewing this submission to the Journal for Open Source Software? The reviews are all done openly through GitHub and given the present world circumstances, I'd hope for reviews within about 6 weeks. You can learn more about the review process here: https://joss.readthedocs.io/en/latest/review_criteria.html |
Hi @kthyng - I will need to learn a bit about the JOSS review process, but yes, I am interested. |
Hi @kthyng, I can review. |
Hi @zsylvester and @ebgoldstein: awesome! I will start the review issue and close this one — the rest of the action should take place in the review issue. Please reach out if you have questions on the process. The JOSS docs have information, and it can also help to look through old submissions to see how things work. Thanks!! |
@whedon assign @zsylvester as reviewer |
OK, @zsylvester is now a reviewer |
@whedon add @ebgoldstein as reviewer |
OK, @ebgoldstein is now a reviewer |
@whedon start review |
OK, I've started the review over in #2341. |
Submitting author: @pfeiffea (Allison Pfeiffer)
Repository: https://github.com/landlab/landlab
Version: 2.1
Editor: @kthyng
Reviewers: @zsylvester, @ebgoldstein
Managing EiC: Kristen Thyng
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 @pfeiffea. Currently, there isn't an JOSS editor assigned to your paper.
The author's suggestion for the handling editor is @kthyng.
@pfeiffea 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:
The text was updated successfully, but these errors were encountered: