-
-
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]: PYLIWC: Linguistic Inquiry and Word Count in Python #7087
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: TextDescriptives: A Python package for calculating a large variety of metrics from text TTLocVis: A Twitter Topic Location Visualization Package ConTEXT Explorer: a web-based text analysis tool for exploring and visualizing concepts across time TRUNAJOD: A text complexity library to enhance natural language processing textnets: A Python package for text analysis with networks |
@editorialbot invite @logological as editor |
Invitation to edit this submission sent! |
@editorialbot add @logological as editor |
Assigned! @logological is now the editor |
@seyyaw @HLasse @alicia-ziying-yang @dpalmasan Would you be willing and able to review this manuscript for the Journal of Open Source Software? |
Sure, I'd be happy to 👍 |
@HLasse Thanks! I'll add you as a reviewer. I'll open a separate issue for the review once I locate one or two additional reviewers. |
@editorialbot add @HLasse as reviewer |
@HLasse added to the reviewers list! |
@seyyaw I saw that you gave a thumbs-up to my comment above. Does this mean you're willing to serve as a reviewer for this paper? |
@logological I am new to this kind of review. Does the review also include Let me know and I am happy to help! |
@seyyaw Reviewing for JOSS is fairly easy -- we prepare a checklist for you that you can work through. You'll need to examine both the paper and the code (which may involve installing and running the software in order to do some basic checks). The entire review takes place via GitHub issues. Any issues you find should be reported in the review issue, or raised as separate issues in the repository of the code/paper under review. The authors then address those issues (by discussing them with you and/or making the necessary changes to the code/paper) so that you're able to proceed with the checklist. Since you say you're happy to help, I'll go ahead and add you as a reviewer and we can begin the review. This will take place in a separate GitHub issue of which you will be notified. Please let me know if you have any questions! |
@editorialbot add @seyyaw as reviewer |
@seyyaw added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #7119. |
Submitting author: @camille1 (Camille LACAN)
Repository: https://github.com/camille1/pyliwc
Branch with paper.md (empty if default branch):
Version: 0.0.1
Editor: @logological
Reviewers: @HLasse, @seyyaw
Managing EiC: Samuel Forbes
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @camille1. Currently, there isn't a JOSS editor assigned to your paper.
@camille1 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: