-
-
Notifications
You must be signed in to change notification settings - Fork 36
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]: Effluent - A python package for modelling effluent discharge #5385
Comments
Hello human, I'm @editorialbot, a robot that can help you with some common editorial tasks. 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:
|
|
|
Wordcount for |
Hi @pnsaevik and thanks for your submission! We don't have editors available at the moment so I will add this to the waitlist. Thanks for your patience. |
In addition to the reviewers in your pool, you might want to contact the github user |
@pnsaevik Sounds great — can you take a look at the list and give 5+ specific suggestions? Just their username without the "@", please. |
Potential reviewers from the existing pool, based on their listed preferences, are:
|
@editorialbot assign me as editor |
Assigned! @kthyng is now the editor |
@pnsaevik I'll take on your submission! |
@edoddridge and @dl11g11 are you interested in reviewing this submission for JOSS? Reviews are done in a github issue and consist of a thorough software review. I would ask you to get started with your review in the next 3 weeks or so since usually the process is iterative between you and the author. You can check out the reviewer guidelines. Thank you for your consideration! |
Hi @kthyng, do you want to invite some other reviewers since @edoddridge and @dl11g11 have not responded? |
@pnsaevik It's hard being able to see what is or isn't apparently happening in your submission review huh! Yes, I will try again. |
@tomchor and @castelao Do you have the time and interest in reviewing this JOSS submission? As you know, reviews are done in a github issue and consist of a thorough software review. I would ask you to get started with your review in the next 3 weeks or so since usually the process is iterative between you and the author. You can check out the reviewer guidelines. Thank you for your consideration! |
@kthyng , I can do that. |
Sorry. This got lost in my notifications - I didn't realise I got tagged in two JOSS threads at nearly the same time and only responded to the other one. |
@castelao Awesome thanks! @edoddridge I saw you got pinged right after I pinged you. Sorry about that — we don't have a way to track review requests, only once people are actually reviewing. |
@editorialbot add @castelao as reviewer |
@castelao added to the reviewers list! |
@kthyng , JOSS used to have a rubric for review with an explicit list of checkmarks. Do you still use it? Where may I find it? Thanks, |
@castelao sorry for my delay, I have been swamped! Yes, you can see more info about that here: https://joss.readthedocs.io/en/latest/review_checklist.html#review-checklist |
@bastorer I don't suppose you're up for a JOSS review so soon after your epic review ended? If you are, we'd love to have you review this submission! You probably got a feel for in being on the other side, but here are some docs you can check out too: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html |
@kthyng Sure, I'd be happy to :-) |
Awesome thanks! I'll add you now and start the review. |
@editorialbot add @bastorer as reviewer |
@bastorer added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #5554. |
Submitting author: @pnsaevik (Pål Næverlid Sævik)
Repository: https://github.com/pnsaevik/effluent
Branch with paper.md (empty if default branch):
Version: v1.2
Editor: @kthyng
Reviewers: @castelao, @bastorer
Managing EiC: Kristen Thyng
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @pnsaevik. Currently, there isn't a JOSS editor assigned to your paper.
@pnsaevik 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 @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type:
The text was updated successfully, but these errors were encountered: