Closed editorialbot closed 1 year ago
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:
@editorialbot commands
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
@editorialbot generate pdf
Software report:
github.com/AlDanial/cloc v 1.88 T=0.14 s (719.9 files/s, 69691.0 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Java 76 809 1803 4939
YAML 3 27 19 566
XML 4 3 6 460
Markdown 9 106 0 369
Python 7 57 101 191
TeX 1 27 0 185
Maven 1 5 2 103
-------------------------------------------------------------------------------
SUM: 101 1034 1931 6813
-------------------------------------------------------------------------------
gitinspector failed to run statistical information for the repository
Wordcount for paper.md
is 886
Failed to discover a valid open source license
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1155/2017/7494313 is OK
- 10.3390/en13153920 is OK
- 10.1016/j.apenergy.2021.117267 is OK
- 10.3390/en13205350 is OK
- 10.5281/zenodo.5726738 is OK
- 10.1109/PES.2005.1489271 is OK
- 10.1145/3307772.3335321 is OK
- 10.1109/MIS.2011.3 is OK
MISSING DOIs
- None
INVALID DOIs
- doi:10.1016/j.eneco.2008.01.003 is INVALID (failed connection)
- doi:10.5771/9783845227443 is INVALID (failed connection)
- doi:10.1016/j.apenergy.2016.08.189 is INVALID (failed connection)
- doi:10.1016/j.envsoft.2017.07.009 is INVALID (failed connection)
- doi:10.1016/j.enpol.2014.03.037 is INVALID (failed connection)
- doi:10.18419/opus-11132 is INVALID (failed connection)
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@KriNiTi Please check the invalid DOIs
@KriNiTi : Please check on your license.
Dear all,
although @KriNiTi submitted the paper, I will serve as primary contact for the review.
@fraukewiese : I fixed the invalid DOIs
Regarding the license: We follow the REUSE Software licensing guide and provide a license statement for each file in the repository. All licenses used in the repository can be found in the "LICSENSES" folder. All "valuable" code is licensed under Apache2.0, other less meaningful files like ".gitignore" are licensed unter CC0-1.0.
REUSE compliance of the repository is tested during CI.
Kind regards Christoph
@editorialbot check references
@editorialbot check license
I'm sorry human, I don't understand that. You can see what commands I support by typing:
@editorialbot commands
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1155/2017/7494313 is OK
- 10.3390/en13153920 is OK
- 10.1016/j.apenergy.2021.117267 is OK
- 10.3390/en13205350 is OK
- 10.1016/j.eneco.2008.01.003 is OK
- 10.5771/9783845227443 is OK
- 10.1016/j.apenergy.2016.08.189 is OK
- 10.1016/j.envsoft.2017.07.009 is OK
- 10.1016/j.enpol.2014.03.037 is OK
- 10.5281/zenodo.5726738 is OK
- 10.18419/opus-11132 is OK
- 10.1109/PES.2005.1489271 is OK
- 10.1145/3307772.3335321 is OK
- 10.1109/MIS.2011.3 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@editorialbot commands
Hello @fraukewiese, here are the things you can ask me to do:
# List all available commands
@editorialbot commands
# Add to this issue's reviewers list
@editorialbot add @username as reviewer
# Remove from this issue's reviewers list
@editorialbot remove @username from reviewers
# Get a list of all editors's GitHub handles
@editorialbot list editors
# Assign a user as the editor of this submission
@editorialbot assign @username as editor
# Remove the editor assigned to this submission
@editorialbot remove editor
# Remind an author, a reviewer or the editor to return to a review after a
# certain period of time (supported units days and weeks)
@editorialbot remind @reviewer in 2 weeks
# Check the references of the paper for missing DOIs
@editorialbot check references
# Perform checks on the repository
@editorialbot check repository
# Adds a checklist for the reviewer using this command
@editorialbot generate my checklist
# Set a value for version
@editorialbot set v1.0.0 as version
# Set a value for archive
@editorialbot set 10.21105/zenodo.12345 as archive
# Set a value for branch
@editorialbot set joss-paper as branch
# Set a value for repository
@editorialbot set https://github.com/organization/repo as repository
# Mention the EiCs for the correct track
@editorialbot ping track-eic
# Generates the pdf paper
@editorialbot generate pdf
# Recommends the submission for acceptance
@editorialbot recommend-accept
# Generates a LaTeX preprint file
@editorialbot generate preprint
# Flag submission with questionable scope
@editorialbot query scope
# Get a link to the complete list of reviewers
@editorialbot list reviewers
# Open the review issue
@editorialbot start review
@editorialbot check repository
Software report:
github.com/AlDanial/cloc v 1.88 T=0.11 s (939.9 files/s, 90997.0 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Java 76 809 1803 4939
YAML 3 27 19 566
XML 4 3 6 460
Markdown 9 106 0 369
Python 7 57 101 191
TeX 1 27 0 185
Maven 1 5 2 103
-------------------------------------------------------------------------------
SUM: 101 1034 1931 6813
-------------------------------------------------------------------------------
gitinspector failed to run statistical information for the repository
Wordcount for paper.md
is 886
Failed to discover a valid open source license
Dear all,
although @KriNiTi submitted the paper, I will serve as primary contact for the review.
@fraukewiese : I fixed the invalid DOIs
Regarding the license: We follow the REUSE Software licensing guide and provide a license statement for each file in the repository. All licenses used in the repository can be found in the "LICSENSES" folder. All "valuable" code is licensed under Apache2.0, other less meaningful files like ".gitignore" are licensed unter CC0-1.0.
REUSE compliance of the repository is tested during CI.
Kind regards Christoph
Do you see a possibility for the license to be discovered automatically?
Dear @fraukewiese - we are in search of a solution see here and keep you updated.
@editorialbot check repository
Software report:
github.com/AlDanial/cloc v 1.88 T=0.15 s (659.3 files/s, 63827.2 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Java 76 809 1803 4939
YAML 3 27 19 566
XML 4 3 6 460
Markdown 9 106 0 369
Python 7 57 101 191
TeX 1 27 0 185
Maven 1 5 2 103
-------------------------------------------------------------------------------
SUM: 101 1034 1931 6813
-------------------------------------------------------------------------------
gitinspector failed to run statistical information for the repository
Wordcount for paper.md
is 886
Failed to discover a valid open source license
@editorialbot check repository
Software report:
github.com/AlDanial/cloc v 1.88 T=0.14 s (714.2 files/s, 69145.5 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Java 76 809 1803 4939
YAML 3 27 19 566
XML 4 3 6 460
Markdown 9 106 0 369
Python 7 57 101 191
TeX 1 27 0 185
Maven 1 5 2 103
-------------------------------------------------------------------------------
SUM: 101 1034 1931 6813
-------------------------------------------------------------------------------
gitinspector failed to run statistical information for the repository
Wordcount for paper.md
is 886
Dear @fraukewiese , we added an additional LICENSE
file to the project root - seems to work now. REUSE is not (yet) supported by many license crawlers.
May I suggest that your bot considers using a better FOSS license scanner like https://github.com/nexB/scancode-toolkit ? It would have detected everything correctly (with only some approximation for the CLA) and its works with REUSE and other conventions and never requires project to update its codebase.
@dlr-cjs re:
It would have detected everything correctly (with only some approximation for the CLA) and its works with REUSE and other conventions and never requires project to update its codebase.
I have attached the scan in JSON format for reference. Note that this may highlight a very minor inconsistency in your license documentation: In https://gitlab.com/dlr-ve/esy/amiris/amiris/-/blob/3-prepare-publication-at-joss/src/test/setup.py there are mentions of both a CC0 and an Apache license, but which one applies is not clear. This is not relevant to your paper license in any case.
@SebastianBoblest : Could you please update us on how the review is going?
@imcatta : How is the review going?
@dlr-cjs and @pombredanne : Thanks for the effort and information on the license issue.
hi,
did not yet find the time. I plan to start next week. I hoped to do it during the Christmas Holiday.
Best Sebastian
fraukewiese @.***> schrieb am Do., 2. Feb. 2023, 17:08:
@SebastianBoblest https://github.com/SebastianBoblest : Could you please update us on how the review is going?
— Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/5041#issuecomment-1413989017, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARTHLZL22MU5XNYRHFP3SSDWVPLWRANCNFSM6AAAAAATSBBZAE . You are receiving this because you were mentioned.Message ID: @.***>
@sebastianboblest : Thanks for the info :)
@imcatta : How is the review going?
I have started my review, but have not yet managed to complete it. I plan to continue it next week.
@editorialbot generate my checklist
@SebastianBoblest I can't do that because you are not a reviewer
@editorialbot commands
Hello @SebastianBoblest, here are the things you can ask me to do:
# List all available commands
@editorialbot commands
# Get a list of all editors's GitHub handles
@editorialbot list editors
# Check the references of the paper for missing DOIs
@editorialbot check references
# Perform checks on the repository
@editorialbot check repository
# Adds a checklist for the reviewer using this command
@editorialbot generate my checklist
# Set a value for branch
@editorialbot set joss-paper as branch
# Generates the pdf paper
@editorialbot generate pdf
# Generates a LaTeX preprint file
@editorialbot generate preprint
# Get a link to the complete list of reviewers
@editorialbot list reviewers
@SebastianBoblest I can't do that because you are not a reviewer
@imcatta That did not work so well. Did I do something wrong?
Here's the current list of reviewers: https://bit.ly/joss-reviewers
@SebastianBoblest I can't do that because you are not a reviewer
@imcatta That did not work so well. Did I do something wrong?
It looks fine to me. @fraukewiese can you help us, please?
@editorialbot remove @SebastianBoblest as reviewer
(trying something)
@SebastianBoblest is not in the reviewers list
@editorialbot add @SebastianBoblest as reviewer
@SebastianBoblest added to the reviewers list!
try it again now, please
Submitting author: !--author-handle-->@KriNiTi<!--end-author-handle-- (Kristina Nienhaus) Repository: https://gitlab.com/dlr-ve/esy/amiris/amiris Branch with paper.md (empty if default branch): 3-prepare-publication-at-joss Version: v1.3 Editor: !--editor-->@fraukewiese<!--end-editor-- Reviewers: @sebastianboblest, @imcatta Archive: 10.5281/zenodo.7756088
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
@sebastianboblest & @imcatta, 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 @fraukewiese 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 @imcatta
📝 Checklist for @SebastianBoblest