-
-
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]: ReadmeReady: Free and Customizable Code Documentation with LLMs - A Fine-Tuning Approach #7479
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:
|
Software report:
Commit count by author:
|
Paper file info: 📄 Wordcount for ✅ The paper includes a |
License info: ✅ License found: |
|
Five most similar historical JOSS papers: DeBEIR: A Python Package for Dense Bi-Encoder Information Retrieval Jury: A Comprehensive Evaluation Toolkit TextDescriptives: A Python package for calculating a large variety of metrics from text DeepSynth: Scaling Neural Program Synthesis with Distribution-based Search TRUNAJOD: A text complexity library to enhance natural language processing |
👋 @souradipp76 - thank you for your submission. While I am seeking out an editor for you, please reduce the word count of your paper to around 1000 words. Most non-essential items can be placed in your documentation. Thank you. |
@crvernon, the paper has been modified to have a word count of around 1500. Thank you. |
Hi @crvernon , @souradipp76, I would like to review this paper. Can I go ahead? Brief about me: |
@editorialbot assign me as editor I am going to take this on myself as editor. |
Assigned! @crvernon is now the editor |
@Manvi-Agrawal - may I ask how you heard about this review? Thanks! |
@crvernon I was browsing for open access journals on Wikipedia and came across JOSS. I found it interesting and went through JOSS website which directed me here. |
@editorialbot add @Manvi-Agrawal as reviewer I'll add you @Manvi-Agrawal thanks! |
@Manvi-Agrawal added to the reviewers list! |
👋 @camilochs - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html |
@editorialbot generate my checklist |
Checklists can only be created once the review has started in the review issue |
@Manvi-Agrawal - I will start the actual review thread after I secure one more review. You will be able to generate your checklist from that thread. |
Thanks @crvernon for your quick reply. I was about to comment here regarding the same when I saw your reply xD |
Hello, @crvernon. Of course. I will review it during tomorrow. |
@editorialbot add @camilochs as reviewer Thanks @camilochs! |
@camilochs added to the reviewers list! |
@editorialbot start review 👋 - Alright @souradipp76, @Manvi-Agrawal, and @camilochs - I am going to close this Pre-Review and kick off the full review which you should receive a notification for. Thanks! |
OK, I've started the review over in #7489. |
Submitting author: @souradipp76 (Souradip Pal)
Repository: https://github.com/souradipp76/ReadMeReady
Branch with paper.md (empty if default branch): main
Version: v1.1.0
Editor: @crvernon
Reviewers: @Manvi-Agrawal, @camilochs
Managing EiC: Chris Vernon
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @souradipp76. Currently, there isn't a JOSS editor assigned to your paper.
@souradipp76 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: