Joss-reviews: [PRE REVIEW]: Dataviz: A package of domain specific visualizations and languages for the Pharo live coding environment

[whedon]

Submitting author: @offray (Offray Vladimir Luna Cárdenas)
Repository: http://mutabit.com/repos.fossil/grafoscopio/doc/tip/Packages/Dataviz/intro.md
Version: 2.2.3
Editor: @acabunoc
Reviewers: @seandenigris

Author instructions

Thanks for submitting your paper to JOSS @offray. The JOSS editor (shown at the top of this issue) will work with you on this issue to find a reviewer for your submission before creating the main review issue.

@offray if you have any suggestions for potential reviewers then please mention them here in this thread. In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission.

Editor instructions

The JOSS submission bot @whedon is here to help you find and assign reviewers and start the main review. To find out what @whedon can do for you type:

@whedon commands

[whedon]

Hello human, I'm @whedon. I'm here to help you with some common editorial tasks for JOSS.

For a list of things I can do to help you, just type:

@whedon commands

[labarba]

@offray : I looked at the paper.md file in the webpage (BTW, the link to PDF is broken) and it's just a copy-paste from the blurb on the landing page.

We (the JOSS editors) plan to extend the author guidelines to clarify the requirements, and to be more firm with enforcing them. Paper length is an issue: we need to see a clear statement of need within the research enterprise, and expect that is not possible in under 250 words (the guide will likely give a range of 250 to 1000 words maximum).

Please take the time to write a short paper that describes the functionality of the software and how it addresses a research need.

[offray]

Lorena,

I'm away now in a Data Camp outside the country, but I will address your
recommendations after returning, on the first week of August.

Thanks,

Offray

On 22/07/17 11:50, Lorena A. Barba wrote:
>

@offray https://github.com/offray : I looked at the |paper.md| file
in the webpage (BTW, the link to PDF is broken) and it's just a
copy-paste from the blurb on the landing page.

We (the JOSS editors) plan to extend the author guidelines to clarify
the requirements, and to be more firm with enforcing them. Paper
length is an issue: we need to see a clear statement of need within
the research enterprise, and expect that is not possible in under 250
words (the guide will likely give a range of 250 to 1000 words maximum).

Please take the time to write a short paper that describes the
functionality of the software and how it addresses a research need.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openjournals/joss-reviews/issues/238#issuecomment-317195664,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFe1yjTLaYRVqIwCQVEkLFTNuVTziPXdks5sQihBgaJpZM4M-n_C.

[cMadan]

@offray - just thought I'd send a reminder

[arfon]

Friendly reminder on this @offray

[arfon]

@offray - please respond to this thread when you can. If we don't hear from you in the next two weeks we'll assume you've lost interest in this submission.

[offray]

Sorry @arfon and all about not being able of respond earlier. Lot of stuff happening in the PhD front. I will be working on the issues reported on this article this week and reporting back here.

[offray]

@labarba I have stated the research fields of data activism and civic hacking added into paper.md and how Dataviz is part of a set of pocket infrastructures that address the need for more inclusive practices in such fields contrasting critically it with the exclusionary practices of Big Data. I have also fixed the PDF link and added paper.bib.

[Kevin-Mattheus-Moerman]

@whedon generate pdf

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

PDF failed to compile for issue #238 with the following error: 

 /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/find.rb:43:in `block in find': No such file or directory (Errno::ENOENT)
    from /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/find.rb:43:in `collect!'
    from /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/find.rb:43:in `find'
    from /app/vendor/bundle/ruby/2.3.0/bundler/gems/whedon-8307502c3aee/lib/whedon/processor.rb:49:in `find_paper_paths'
    from /app/vendor/bundle/ruby/2.3.0/bundler/gems/whedon-8307502c3aee/bin/whedon:32:in `prepare'
    from /app/vendor/bundle/ruby/2.3.0/gems/thor-0.20.0/lib/thor/command.rb:27:in `run'
    from /app/vendor/bundle/ruby/2.3.0/gems/thor-0.20.0/lib/thor/invocation.rb:126:in `invoke_command'
    from /app/vendor/bundle/ruby/2.3.0/gems/thor-0.20.0/lib/thor.rb:387:in `dispatch'
    from /app/vendor/bundle/ruby/2.3.0/gems/thor-0.20.0/lib/thor/base.rb:466:in `start'
    from /app/vendor/bundle/ruby/2.3.0/bundler/gems/whedon-8307502c3aee/bin/whedon:99:in `<top (required)>'
    from /app/vendor/bundle/ruby/2.3.0/bin/whedon:22:in `load'
    from /app/vendor/bundle/ruby/2.3.0/bin/whedon:22:in `<main>'

[arfon]

@Kevin-Mattheus-Moerman - Whedon doesn't know how to handle this submission because of where the source is hosted.

[offray]

The previous accepted paper was hosted also in a Fossil repository and was processed properly, so this is possible. Let me know what can I make to help on this.

[arfon]

Yep, we can process them, I just have to do it manually.

[arfon]

@offray - could you provide links to the paper.md and paper.bib files please?

[offray]

Here they are:

• paper.bib: http://mutabit.com/repos.fossil/grafoscopio/doc/tip/Packages/Dataviz/JOSS/paper.bib
• paper.md: http://mutabit.com/repos.fossil/grafoscopio/raw/Packages/Dataviz/JOSS/paper.md?name=c9dfe60db76b62a44e997f5d2a6a4ee8fd758ad4

[arfon]

@offray @Kevin-Mattheus-Moerman - here is the compiled PDF: 10.21105.joss.00238.pdf

Also, @offray - please could you reformat your paper.md file to be exactly like this one please: https://gist.github.com/arfon/a880bdb988d5bdf9df05561122598a6c

[offray]

@arfon Done. The new paper.md at http://mutabit.com/repos.fossil/grafoscopio/raw/Packages/Dataviz/JOSS/paper.md?name=cb73e904dba8cba62d4ad652c378e6659b37e072 includes your suggestion (and some typos, writing corrections, and screenshots).

Let me know if anything else needs to be added or removed.

Thanks.

[arfon]

:wave: @acabunoc - would you be willing to edit this submission for JOSS?

[arfon]

@offray - would you be able to look at this list of reviewers and potentially suggest a couple of people who may be able to review your submission? https://bit.ly/joss-reviewers

[Kevin-Mattheus-Moerman]

Just pinging again :ping_pong: @acabunoc, could you help edit this one?

[offray]

@arfon From the list you send me, I think that Mark Galassi, coudl be a good reviewer, because is the only one that has experience with Smalltalk. Let me know anything else I can help with.

[arfon]

@offray ok thanks. Outside of the reviewer list that we have do you have any suggestions for reviewers that you know would be good for this?

[acabunoc]

Yes, I can edit this! 🏓

[acabunoc]

@whedon assign @acabunoc as editor

[whedon]

OK, the editor is @acabunoc

[offray]

@arfon I have talked with Sean DeNigris and he is willing to help.

Thanks

[arfon]

@acabunoc - looks like @offray might have been able to find us a reviewer ☝️

[offray]

@arfon @acabunoc, so which are the next steps if Sean DeNigris wants to join the process?

[arfon]

@whedon assign @seandenigris as reviewer

[whedon]

OK, the reviewer is @seandenigris

[arfon]

@whedon start review magic-word=bananas

[whedon]

OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/720. Feel free to close this issue now!

[arfon]

@seandenigris @acabunoc - please head over to #720 to carry out the main review.