-
-
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]: FaaSr: R Package for Function-as-a-Service Cloud Computing #6995
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: |
👋 @spark0510 - note that your paper does not compile. Please follow the example paper and note that you can click on the error above to find out more about it. In addition, you could work on the possibly missing DOIs that editorialbot suggests, but note that some may be incorrect. Please feel free to make changes to your .bib file, then use the command |
In this case, specifically, please remove the ORCID line rather than using an invalid ORCID in the metadata |
Thank you @danielskatz - @spark0510 had been able create a GitHub Action to successfully generate a PDF of the paper, but it looks like we overlooked the ORCID and DOI issues. We'll get those addressed asap. |
@editorialbot check references |
|
@editorialbot generate pdf |
Five most similar historical JOSS papers: funsies: A minimalist, distributed and dynamic workflow engine The fqar package: R tools for analyzing floristic quality assessment data slurmR: A lightweight wrapper for HPC with Slurm Rdataretriever: R Interface to the Data Retriever containerit: Generating Dockerfiles for reproducible research with R |
@editorialbot assign me as editor |
Assigned! @danielskatz is now the editor |
👋 @spark0510 and @renatof - please suggest a few potential reviewers. You can search the list of people that have already agreed to review and may be suitable for this submission, or suggest people outside the list. If you know a potential reviewer's GitHub username, please mention it here in this thread (without tagging them with an @). |
Hi @danielskatz - my primary suggestion would be Tyson Swetnam (GitHub user tyson-swetnam) who is familiar with both the cloud/FaaS side and application side; I don't see him in the JOSS reviewer database and he may or may not have the cycles to review (but he could perhaps suggest someone in his team?) |
👋 @tyson-swetnam - would you be willing to review this submission for 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 |
👋 @gvegayon and @nuest - would one or both of you be willing to review this submission for 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 |
Yes. When is the review due date? |
Once we start the review (after we get at least 2 reviewers), we shoot for 2-4 weeks |
👋 @equitable-equations - would you be willing to review this submission for 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 |
@tyson-swetnam - I'm going to add you as a reviewer, based on your "Yes." Again, the review won't start until I find at least one more reviewer. |
@editorialbot add @tyson-swetnam as reviewer |
@tyson-swetnam added to the reviewers list! |
@danielskatz Sorry, I'm out. I'm just returning from an extended leave and I wouldn't be able to hold any deadlines. More reliable after the summer again! |
@danielskatz I'd love to but this one looks a bit too far outside my expertise. I'm sorry! |
@editorialbot add @yadudoc as reviewer Thanks for "volunteering", @yadudoc |
@yadudoc added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #7027. |
I see you already have two reviewers. LMK if you'd need a third. |
Submitting author: @spark0510 (Sungjae Park)
Repository: https://github.com/FaaSr/FaaSr-package
Branch with paper.md (empty if default branch):
Version: v1.3.0
Editor: @danielskatz
Reviewers: @tyson-swetnam, @yadudoc
Managing EiC: Daniel S. Katz
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @spark0510. Currently, there isn't a JOSS editor assigned to your paper.
@spark0510 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: