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
[REVIEW]: mixComp: An R package for estimating complexity of a mixture #4354
Comments
Hello humans, 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 |
|
@Athene-ai, please create your checklist typing: @zhiiiyang, please create your checklist typing: |
Review checklist for @zhiiiyangConflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
|
Dear @Athene-ai and @zhiiiyang Thank you for accepting our invitation. You have just created your checklist. Please follow the instructions at the top of this page. Whenever you finish a review task, you can check the corresponding item on. You can always interact with the other reviewers, the author(s), and the editor (me). You can also create issues in the target repository but please mention this thread so we can follow up what is going on outside of the main thread. Please do not hesitate to ask me anything and ping me when you need help. Thank you! |
@jbytecode @yuliadm I have completed my review. Please see all the comments above. #4354 (comment) @yuliadm has completed some requests in the dev branch and will merge them into the main branch once all requests in yuliadm/mixComp#2 are addressed. @Athene-ai, you might want to review the dev branch for the latest commits if the merge hasn't been completed by that time. |
@zhiiiyang many thanks for the advise 😉 |
@zhiiiyang - thank you for your review. However there are still unchecked task items and it seems your review is not complete. Please do not modify the checklist entry (just click the checkboxes) and post your reviewing report as posts in this issue. |
@Athene-ai - could you please update your status and tell us how is your review going? Thank you in advance. |
@jbytecode, I see. I just check off the checklist and posted all my comments below in a separate post. Additional comments
|
@yuliadm - please follow the suggestions, apply them, and report here when all of the stuff is complete . @zhiiiyang - please review the authors' corrections (if exists) and report your final thougths. thank you in advance. |
@Athene-ai - could you please update your status? Thank you in advance! |
Hi @jbytecode ! I am finishing my review and next week I will upload it |
Review checklist for @Athene-aiConflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
|
@jbytecode I just check off the checklist and posted all my comments below in a separate post. |
@Athene-ai do you have any suggestions, comments,or improvements? |
@Athene-ai - please suggest corrections and make comments. Whenever the authors apply them check off the corresponding item. After finishing the review please provide a summary and your decision. thank you. |
@editorialbot check references |
|
@editorialbot generate pdf |
@editorialbot recommend-accept |
|
|
👋 @openjournals/joss-eics, this paper is ready to be accepted and published. Check final proof 👉 openjournals/joss-papers#3301 If the paper PDF and the deposit XML files look good in openjournals/joss-papers#3301, then you can now move forward with accepting the submission by compiling again with the command |
@yuliadm – I made some slight changes to your paper to match the current preferred format for denoting equal authorship and corresponding authorship: yuliadm/mixComp#8 |
@editorialbot recommend-accept |
|
|
👋 @openjournals/joss-eics, this paper is ready to be accepted and published. Check final proof 👉 openjournals/joss-papers#3308 If the paper PDF and the deposit XML files look good in openjournals/joss-papers#3308, then you can now move forward with accepting the submission by compiling again with the command |
Hrm, the formatting for Lilian Mueller is now a little weird with the updated formatting. @yuliadm – is there any particular need to specify/highlight that author as a 'contributor'? |
@arfon no specific reason, equal contribution would be OK! So I fixed it! |
@editorialbot recommend-accept |
|
|
👋 @openjournals/joss-eics, this paper is ready to be accepted and published. Check final proof 👉 openjournals/joss-papers#3309 If the paper PDF and the deposit XML files look good in openjournals/joss-papers#3309, then you can now move forward with accepting the submission by compiling again with the command |
@editorialbot accept |
|
🐦🐦🐦 👉 Tweet for this paper 👈 🐦🐦🐦 |
🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨 Here's what you must now do:
Any issues? Notify your editorial technical team... |
@Athene-ai, @zhiiiyang – many thanks for your reviews here and to @jbytecode for editing this submission! JOSS relies upon the volunteer effort of people like you and we simply wouldn't be able to do this without you ✨ @yuliadm – your paper is now accepted and published in JOSS ⚡🚀💥 |
🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉 If you would like to include a link to your paper from your README use the following code snippets:
This is how it will look in your documentation: We need your help! The Journal of Open Source Software is a community-run journal and relies upon volunteer effort. If you'd like to support us please consider doing either one (or both) of the the following:
|
@jbytecode , @zhiiiyang , @Athene-ai , @arfon |
Submitting author: @yuliadm (Yulia)
Repository: https://github.com/yuliadm/mixComp
Branch with paper.md (empty if default branch):
Version: v0.1.3
Editor: @jbytecode
Reviewers: @Athene-ai, @zhiiiyang
Archive: 10.5281/zenodo.6660840
Status
Status badge code:
Reviewers and authors:
Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the target repository and link to those issues (especially acceptance-blockers) by leaving comments in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)
Reviewer instructions & questions
@Athene-ai & @zhiiiyang, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review.
First of all you need to run this command in a separate comment to create the checklist:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @jbytecode know.
✨ Please start on your review when you are able, and be sure to complete your review in the next six weeks, at the very latest ✨
Checklists
📝 Checklist for @Athene-ai
📝 Checklist for @zhiiiyang
The text was updated successfully, but these errors were encountered: