-
-
Notifications
You must be signed in to change notification settings - Fork 39
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]: DetecTree: Tree detection from aerial imagery in Python #2143
Comments
Hello human, I'm @whedon, 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:
|
|
PDF failed to compile for issue #2143 with the following error: /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-45a043c4bfc2/lib/whedon.rb:200:in |
|
@openjournals/dev can you help compile this paper? |
@whedon generate pdf |
PDF failed to compile for issue #2143 with the following error: /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-45a043c4bfc2/lib/whedon.rb:200:in |
@terrytangyuan @arokem @kthyng could one of you edit this submission? |
the affiliation is copied from my other JOSS paper source, in which I am also the sole author. I do not know what might be wrong. |
Yes, but this isn't compliant with our updated format. Please follow the example in our docs and break the |
@whedon generate pdf |
Hello @arfon I am sorry about that and I thank you for your help. I have amended the paper md source and the PDF is compiled correcly now 😄 |
Hello @Kevin-Mattheus-Moerman , should I tag more potential editors, or should we wait for the tagged ones to answer? |
Hi! I can take this one. |
OK, the editor is @kthyng |
@martibosch It looks like your documentation could be improved. I went to your readthedocs but it doesn't include the more useful documentation from your readme or from the example repo you mention. |
@martibosch Could you look through the reviewer list (https://bit.ly/joss-reviewers) and give suggestions of who might be relevant reviewers for your software? Please don't use "@" to mention them so that they do not get emailed about this, just list their github username. You can also provide information for reviewers who are not on the list if you have other suggestions. |
First of all thank you for editing my submission 😄
I understand that you mean that I should include the documentation for the technical methods described in the |
/ooo March 7, 2020 to March 15, 2020 |
some well suited potential reviewers that I could find are: rmsare scivision stsievert thomakra juliohm JeffWalton-PSC |
👋 Hey @martibosch... Letting you know, |
Dear authors and reviewers We wanted to notify you that in light of the current COVID-19 pandemic, JOSS has decided to suspend submission of new manuscripts and to handle existing manuscripts (such as this one) on a "best efforts basis". We understand that you may need to attend to more pressing issues than completing a review or updating a repository in response to a review. If this is the case, a quick note indicating that you need to put a "pause" on your involvement with a review would be appreciated but is not required. Thanks in advance for your understanding. Arfon Smith, Editor in Chief, on behalf of the JOSS editorial team. |
I mean — I am trying to learn about the package you wrote, like I have been as an editor, and I want to go somewhere to learn about it more. Normally readthedocs functions this way, but yours (previously) was strictly description of the functions. Where do you imagine a new user starting with your code? The readme seems like a good start, but also seems too short. Anyway, this will surely come up in review too, but I figured you could start working on it :) |
@JeffWalton-PSC and @thomakra Are you interested and willing to review this JOSS submission? Normally I would ask for the reviews within about 3 weeks, but many things are unusual right now, so timing is flexible too. Let me know what you think. Thanks. |
here is more information about reviewing: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html |
Kristen,
Yes, I’m interested. I will look through the documentation link you sent.
Thanks,
Jeff
From: Kristen Thyng [mailto:[email protected]]
Sent: Thursday, 19 March, 2020 15:06
To: openjournals/joss-reviews <[email protected]>
Cc: Jeff Walton <[email protected]>; Mention <[email protected]>
Subject: Re: [openjournals/joss-reviews] [PRE REVIEW]: DetecTree: Tree detection from aerial imagery in Python (#2143)
@JeffWalton-PSC<https://github.com/JeffWalton-PSC> and @thomakra<https://github.com/thomakra> Are you interested and willing to review this JOSS submission? Normally I would ask for the reviews within about 3 weeks, but many things are unusual right now, so timing is flexible too. Let me know what you think. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#2143 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AI5VWG3MHUPQKPCXUGNRYCDRIJUKBANCNFSM4LBCHJ2Q>.
|
Hi Kristen,
Unfortunately I do not have the capacity at this time, although the project
seems interesting.
…-Thomas-
On Thu, 19 Mar 2020 at 20:06, Kristen Thyng ***@***.***> wrote:
@JeffWalton-PSC <https://github.com/JeffWalton-PSC> and @thomakra
<https://github.com/thomakra> Are you interested and willing to review
this JOSS submission? Normally I would ask for the reviews within about 3
weeks, but many things are unusual right now, so timing is flexible too.
Let me know what you think. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2143 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABOAW3YCZBHV3LQRB3FWKSDRIJUKBANCNFSM4LBCHJ2Q>
.
|
Thanks @JeffWalton-PSC! I'll add you as a reviewer and continue to search for a second reviewer. |
@whedon assign @JeffWalton-PSC as reviewer |
OK, @JeffWalton-PSC is now a reviewer |
@juliohm Do you have the availability and interest to review this JOSS submission? We understand people are quite busy in these unusual times and reviews may take extra time right now, that is ok. Thanks for your consideration. |
Thank you @kthyng for pinging. I wish I could review the paper, but I am very busy at the moment with some deadlines. Hope you can find another reviewer. |
@rmsare Might you be able to review this submission to JOSS? Thanks for your consideration. |
@kthyng, thanks for the request - this submission looks really interesting. I expect I could complete a review by 3 May (unfortunately I have a late April deadline). Would this be timely enough for this review? |
@rmsare Yes, that would be great. We are grateful for any time people can dedicate to JOSS right now in these unusual times. I will add you as the second reviewer and we can move ahead to start the review. |
OK, @rmsare is now a reviewer |
@whedon start review |
OK, I've started the review over in #2172. |
@JeffWalton-PSC and @rmsare please head over to #2172 for the actual review. |
Submitting author: @martibosch (Martí Bosch)
Repository: https://github.com/martibosch/detectree
Version: v0.3.0
Editor: @kthyng
Reviewers: @JeffWalton-PSC , @rmsare
Managing EiC: Kevin M. Moerman
Author instructions
Thanks for submitting your paper to JOSS @martibosch. Currently, there isn't an JOSS editor assigned to your paper.
@martibosch 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: