Automated JOSS submission

[hadley]

It would be neat to have some tools that automated the submission of a package to JOSS

• Develop some convention about where paper.md should live, and provide a basic check that it's the correct structure. Create a template and add to usethis.

• R script to generate paper.json

• Automate submission of a package to zenodo/figshare

• Automate generation of inst/CITATION and badge for README

[noamross]

submitr could have submit_joss() and submit_ropensci(joss=TRUE)

[cboettig]

👍

For the R script to generate the json metadata (parsed by zenodo, and working with figshare to do so), we've started a script (one-fn package) here: https://github.com/codemeta/codemetar . Currently just creates a codemeta.json for a software package based on data from DESCRIPTION, but would be great to support more interactive input & generate paper.json (as both use the codemeta json-ld context @arfon & co have helped develop).

[karthik]

I love this idea!
This would also be motivation for me to finish the rzenodo package which I will do before unconf.

@noamross Maybe we could work on this at unconf and try to fold into onboarding as well?

cc / @arfon

[karthik]

@noamross Is there separate discussion for submitr elsewhere? I shared a whole bunch of ideas about it on onboarding (or some other channel before that came to be) for both the package and the the GitHub based services (similar to JOSS' Whedon).

[arfon]

⚡️ love the sounds of this. Let me know if there's anything I can do to help.

[noamross]

@karthik No, I just made that up

[MilesMcBain]

Just the opportunity to be there when we submit the JOSS submission package to JOSS using the JOSS submission package has me pretty keen to help out with this.

Will it be enough to call forth a mighty FOSS demagorgon? We can only hope.

[karthik]

@MilesMcBain open source all the way down. 🐢🐢🐢🐢🐢🐢