-
-
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]: Sequana: a set of flexible genomic pipelines for processing and reporting NGS analysis #334
Comments
@pjotrp - the submitting author suggested you as a potential editor. |
@whedon commands |
Here are some things you can ask me to do:
🚧 Important 🚧 This is all quite new. Please make sure you check the top of the issue after running a @whedon command (you might also need to refresh the page to see the issue update). |
OK, the editor is @pjotrp |
@cokelaer thank you for your submission! I'll be looking for a reviewer soon. In the mean time can you help out with a few things? I can't find the paper.md and paper.bib files. Can you point them to me? Also can you make the LICENSE file standard - if it is it will show up on github with the right license icon. Thanks! |
@ pjotrp |
Best is to check one of the existing publication. See https://github.com/genenetwork/genenetwork2/tree/master/doc/joss/2016 |
Do the paper.bib and paper.md must be in the repository of the software or can they be put elsewhere ? Sequana is an organisation and we put the software in sequana/sequana but for papers, we'd like to keep it separate for instance in ./sequana/resources . Would it be fine with your policy ? |
I think this is going to break some of our submission tooling (i.e. it's expected that the paper be in the software repository being reviewed). Let me check and get back to you. For reference, some authors have made a folder in |
As the final paper gets generated from the source tree it is tied to the commit of that release. You can remove the paper from the source tree once it is published. It will be in that particular source release and git history. So it is not intrusive. Makes sense to tie it to the project, right? |
okay, that's fine, I will add a ./joss directory in the ./doc |
FYI we have added a paper.bib paper.md in https://github.com/sequana/sequana/tree/master/doc/joss |
That looks great. @bow since since this is a snakemake application would you care to review this JOSS submission? |
No problem. Thanks @bow. |
OK, the reviewer is @bow |
@whedon start review magic-word=bananas |
OK, I've started the review over in #352. Feel free to close this issue now! |
Submitting author: @cokelaer (Thomas Cokelaer)
Repository: https://github.com/sequana/sequana/
Version: 0.4.1
Editor: @pjotrp
Reviewer: @bow
Author instructions
Thanks for submitting your paper to JOSS @cokelaer. The JOSS editor (shown at the top of this issue) will work with you on this issue to find a reviewer for your submission before creating the main review issue.
@cokelaer if you have any suggestions for potential reviewers then please mention them here in this thread. In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission.
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: