-
-
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]: 'cstag
and cstag-cli
: tools for manipulating and visualizing CS tags'
#5950
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 |
|
Five most similar historical JOSS papers: cerebra: A tool for fast and accurate summarizing of variant calling format (VCF) files BAMnostic: an OS-agnostic toolkit for genomic sequence analysis WGS2NCBI - Toolkit for preparing genomes for submission to NCBI sumo: Command-line tools for plotting and analysis of periodic ab initio calculations Chromatiblock: scalable whole-genome visualization of structural differences in prokaryotes |
@editorialbot query scope |
Submission flagged for editorial review. |
@akikuno thanks for this submission. I am the AEiC for this track, and here to help with initial steps. Note I have just triggered a scope review by our editorial board. This scope review is to help me determine if this work conforms to our substantial scholarly effort criteria, e.g. in terms of size/maturity/functionality. This scope review should take about 2 weeks to complete. |
Note to editors. This looks like this submission also includes: https://github.com/akikuno/cstag-cli, for which
|
@akikuno I have just removed the If you'd like to suggest reviewers at this point that would be helpful for us. You can do so by listing their GitHub handles, but please do leave out the @akikuno on your repository, I see you have a code-of-conduct, and the README talks about "Feedback and Support" (and posting issues), however, can you also add instructions for users on how to contribute? A detailed way of doing so would be to add a |
@editorialbot assign @jmschrei as editor |
Assigned! @jmschrei is now the editor |
@Kevin-Mattheus-Moerman @jmschrei I appreciate your feedback. I am very pleased to be able to undergo the review process with JOSS. As recommended, I have included a CONTRIBUTING.md file in the repository, which can be found here: For potential reviewers, I propose the following individuals:
Kind regards, |
Sorry for the delay, @akikuno. Let's get this going. @betteridiot, @jbloom, @KazukiNakamae, would any of you be willing to serve as reviewers for this submission, or have suggestions for others that might be able to? Thanks! |
I would happy to review this. |
Thanks! |
@editorialbot add @betteridiot as reviewer |
@betteridiot added to the reviewers list! |
If another reviewer is needed, I would also be happy to review this. Just let me know. |
Awesome, thanks! |
@editorialbot add @jbloom as reviewer |
@jbloom added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #6066. |
Submitting author: @akikuno (Akihiro Kuno)
Repository: https://github.com/akikuno/cstag
Branch with paper.md (empty if default branch): joss
Version: v1.0.4
Editor: @jmschrei
Reviewers: @betteridiot, @jbloom
Managing EiC: Kevin M. Moerman
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @akikuno. Currently, there isn't a JOSS editor assigned to your paper.
@akikuno if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.
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: