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
JOSS submission for whole ecosystem #5693
base: master
Are you sure you want to change the base?
Conversation
|
Ah drat, I forgot to set up a process for opting in... If you want in on this, please comment on this PR or suggest a change to the |
|
Sure please add me! Ben Postlethwaite https://github.com/bpostlethwaite is fine. |
|
Yes, good with me too! Adam Kulidjian https://github.com/kully |
|
Happy to be included as well. Miklós Tusz https://github.com/mdtusz |
|
Thanks for the inclusion! Robert Monfera https://github.com/monfera |
|
Sounds good to me |
|
Happy to be included as well! |
|
sure :) |
|
@kig |
|
|
|
Thanks, happy to be included as well! |
|
@archmoj Thanks, would be delighted! |
|
While I haven't contributed in while, I'd love to be included as well. Thanks! |
|
Thanks all! Now that I've got buy-in from everyone I actually need to write this thing so you'll have something to comment on... stay tuned :) |
I am preparing a submission to the Journal of Open Source Software (JOSS) for the whole Plotly visualization ecosystem (Javascript, Python, R, Julia). Their process is outlined here https://joss.readthedocs.io/en/latest/submitting.html and I've kicked off the conversation here openjournals/joss#928 to validate this "one big paper" approach.
Here's an example of what the final output could look like https://joss.theoj.org/papers/10.21105/joss.01057 and the corresponding artifacts in the repo that led to it https://github.com/altair-viz/altair/tree/master/paper.
This PR is currently a stub and eventually should be merged to master when everyone involved is happy with what the paper looks like, how their name/affiliation etc is represented, and then I'll make the JOSS submission as the "corresponding author" unless anyone objects. @alexcjohnson will be looking after the order of the author list.
I'll work on the body of the paper in the next little bit and ask for comments once I'm done, but I'm kicking things off here so as to notify all the potential co-authors below and start getting everyone comfortable with the process and opting in to authorship :)
Since this paper will cover the whole ecosystem for the four languages mentioned, I propose the following folks as co-authors (in no particular order, and with sincere apologies if I've left anyone out!)... everyone will have to opt IN and anyone can nominate any other major contributors: