-
-
Notifications
You must be signed in to change notification settings - Fork 41
[REVIEW]: discourseGT: An R package to analyze discourse networks in educational contexts #5143
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
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 |
Dear @schochastics, @zoometh and @lebebr01, thank you again for accepting review this submission for JOSS. The reviewing process is checklist based, and instructions were already posted above by the editorial bot - but let me know if you need any assistance, ok? Also, you can tag @q1cui if you have specific questions about the manuscript. @q1cui, you can tag any of your co-authors GitHub accounts if you want, so they will be able to follow this issue. |
@editorialbot check references |
|
1 similar comment
|
@q1cui, please check the missing and invalid DOIs above when you can, and let me know if you need any assistance, ok? |
Review checklist for @schochasticsConflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
|
Review checklist for @zoomethConflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
|
I have added a few issues to the repository which I would like to authors to address. Especially the test part is crucial to me. Please take some time and effort to add some tests to the package. Overall this is a very nice package which just lacks a bit of good practice but that should be fixable. I am happy with the submission once my issues are addressed adequately. (cc @q1cui) |
Sorry for the delay, I will start my review at the end of the week. |
@editorialbot check references |
|
@editorialbot generate pdf |
👋 @q1cui License: Some minor errors:
|
|
@editorialbot generate pdf |
@editorialbot recommend-accept |
|
|
The paper's PDF and metadata files generation produced some warnings that could prevent the final paper from being published. Please fix them before the end of the review process.
|
ID ref-Lou_2001 already defined |
We have deleted the duplicate reference. |
@marcosvital We have fixed the image and reference issues. |
@editorialbot recommend-accept |
|
|
👋 @openjournals/sbcs-eics, this paper is ready to be accepted and published. Check final proof 👉📄 Download article If the paper PDF and the deposit XML files look good in openjournals/joss-papers#4451, then you can now move forward with accepting the submission by compiling again with the command |
@editorialbot accept |
1 similar comment
@editorialbot accept |
|
Ensure proper citation by uploading a plain text CITATION.cff file to the default branch of your repository. If using GitHub, a Cite this repository menu will appear in the About section, containing both APA and BibTeX formats. When exported to Zotero using a browser plugin, Zotero will automatically create an entry using the information contained in the .cff file. You can copy the contents for your CITATION.cff file here: CITATION.cff
If the repository is not hosted on GitHub, a .cff file can still be uploaded to set your preferred citation. Users will be able to manually copy and paste the citation. |
🐘🐘🐘 👉 Toot 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... |
Congratulations! @q1cui! Bit thanks to @marcosvital and the reviewers @schochastics, @zoometh! 🥳 |
🎉🎉🎉 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:
|
Submitting author: @q1cui (Qi Cui)
Repository: https://github.com/q1cui/discourseGT
Branch with paper.md (empty if default branch):
Version: 1.2.0
Editor: @marcosvital
Reviewers: @schochastics, @zoometh
Archive: 10.5281/zenodo.8164950
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
@schochastics & @zoometh & @lebebr01, 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 @marcosvital 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 @schochastics
📝 Checklist for @zoometh
The text was updated successfully, but these errors were encountered: