-
-
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]: Generating Visualizations Conversationally using LLMs #7328
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: 🔴 Failed to discover a valid open source license |
|
Five most similar historical JOSS papers: AstronomicAL: an interactive dashboard for visualisation, integration and classification of data with Active Learning SAMBA: A Trainable Segmentation Web-App with Smart Labelling TLViz: Visualising and analysing tensor decomposition models with Python TX$^2$: Transformer eXplainability and eXploration Jury: A Comprehensive Evaluation Toolkit |
👋 @buddyroo30 - while I am finding you an editor, please reduce the word count of your paper to around 1000 words. Also, please add an open source license to your repository (see https://opensource.org/licenses). |
@editorialbot invite @logological as editor 👋 @logological are you able to take this on one as editor? Thanks! |
Invitation to edit this submission sent! |
@crvernon This submission presents a problem similar to the one we had with PYLIWC (#7119) in that it is targeted at users of a proprietary tool, CanvasXpress. (Note that CanvasXpress falsely claims to be open source; it is actually distributed under a licence that covers only uses that are "personal and educational" and places heavy-handed restrictions on redistribution.) I am concerned about our ability to find reviewers who can (legally) use CanvasXpress to test the software. Before PYLIWC was rejected (for unrelated reasons), I tried and failed to find reviewers who held a licence to the proprietary software it depended on. In any case, even if it's not strictly outside JOSS's scope, I'm not particularly comfortable editing a submission on a free/open-source tool whose only purpose is to facilitate the use of proprietary software. What are your thoughts? |
@editorialbot query scope Thank you for raising this issue @logological. I am going to place this on in review with our larger editorial board as well. So let's hold off on finding reviewers. @buddyroo30 - please feel free to provide any comment here to address the above. |
Submission flagged for editorial review. |
Hi,
Thank you for the feedback on our submission. I went ahead and added an open source license as requested and I will work to reduce the word count. As for the issue around the license for CanvasXpress itself, let me discuss that with my co-author and get back to you soon.
Best,Andrew Smith
Yahoo Mail: Search, Organize, Conquer
On Thu, Oct 24, 2024 at 4:39 PM, Chris ***@***.***> wrote:
@editorialbot query scope
Thank you for raising this issue @logological. I am going to place this on in review with our larger editorial board as well. So let's hold off on finding reviewers.
@buddyroo30 - please feel free to provide any comment here to address the above.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hi,
So I discussed the license issue around CanvasXpress itself with my collaborator and he feels its current license is reasonable and does not want to change it. First, practically, the vast majority of users of CanvasXpress are academic or not for profit users, so they would be able to freely use CanvasXpress (and the associated AI enhancements we discuss in our paper) without limitation. Second, the license for CanvasXpress itself is essentially what most of the other large visualization packages use (e.g. Plotly) so CanvasXpress's license is not anything out of the ordinary. Please let us know your thoughts and if you think you could proceed with the review of the paper.
thanks,Andrew Smith
On Friday, October 25, 2024 at 09:57:54 AM EDT, Andrew Smith ***@***.***> wrote:
Hi,
Thank you for the feedback on our submission. I went ahead and added an open source license as requested and I will work to reduce the word count. As for the issue around the license for CanvasXpress itself, let me discuss that with my co-author and get back to you soon.
Best,Andrew Smith
Yahoo Mail: Search, Organize, Conquer
On Thu, Oct 24, 2024 at 4:39 PM, Chris ***@***.***> wrote:
@editorialbot query scope
Thank you for raising this issue @logological. I am going to place this on in review with our larger editorial board as well. So let's hold off on finding reviewers.
@buddyroo30 - please feel free to provide any comment here to address the above.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@editorialbot assign me as editor @buddyroo30 - I will see if we can find you reviewers who have free access to this platform. If not, then we will have to reject. But let's give it a shot. I'll take this one on. |
Assigned! @crvernon is now the editor |
👋 @RahulSundar - 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 Note: this review requires access to CanvasXpress |
👋 @luisaforozco - 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 Note: this review requires access to CanvasXpress |
👋 @ahmadawais - 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 Note: this review requires access to CanvasXpress |
@crvernon I can try to help alongside @saqibameen our lead MLE founding engineer. |
@editorialbot add @ahmadawais as reviewer |
@ahmadawais added to the reviewers list! |
👋 @saqibameen - 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 |
@crvernon thanks for the invitation. This field is outside of my expertise and I do not have access to CanvasXpress, so I will have to pass on reviewing this one. |
Hi @crvernon ! Yes, I would like to review this work. |
@editorialbot add @RahulSundar as reviewer |
@RahulSundar added to the reviewers list! |
@editorialbot start review 👋 - Alright @buddyroo30, @ahmadawais, and @RahulSundar - 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 #7529. |
Submitting author: @buddyroo30 (Andrew Smith)
Repository: https://github.com/buddyroo30/canvasxpress_gen
Branch with paper.md (empty if default branch): JOSS-submission
Version: V1.0.1
Editor: @crvernon
Reviewers: @ahmadawais, @RahulSundar
Managing EiC: Chris Vernon
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @buddyroo30. Currently, there isn't a JOSS editor assigned to your paper.
@buddyroo30 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: