Skip to content
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

Clarify publication plans #14

Open
florianm opened this issue Aug 28, 2019 · 5 comments
Open

Clarify publication plans #14

florianm opened this issue Aug 28, 2019 · 5 comments
Assignees
Labels
Milestone

Comments

@florianm
Copy link
Collaborator

florianm commented Aug 28, 2019

Feature

Clarify publication plans

Task

Source ropensci/software-review#335 @maelle

Reg "Note: I would like to submit a paper about the package in a few weeks, 
but haven't got the manuscript ready and approved for publication just yet." 
This is also a good reason to put the issue on hold since the reviewers 
would read the short JOSS paper. What do you mean by approved?
@florianm florianm self-assigned this Aug 28, 2019
@florianm
Copy link
Collaborator Author

florianm commented Aug 28, 2019

A rudimentary JOSS-style paper is actually included.
However I'd like to check scope/fit for an MEE paper first, which will both exclude prior publication to JOSS (is that right? can we have both?) and take a while longer than I'd like to hold up the ROpenSci submission. @maelle rightly mentioned that a few diagrams would help to draw the bigger picture - already working on it on paper, see also #19

The reason for not wanting to hold up ROpenSci is an ODK gathering later this year in preparation for which I'd like to prepare/solidify my end (ruODK) as far as possible. I feel that the feedback from ROpenSci reviewers will help me find my blind spots and improve ruODK efficiently.

Being a public servant, writing a paper (MEE or JOSS) involves a joyful and bureaucratic approval process to make sure I'm picking the right words and not contradicting my Department's policies/positions/strategic directions. This internal review process can further delay the publication.

So in a nutshell, ROpenSci review will help to deliver a robust, production-worthy package while the publication at MEE or JOSS will undoubtedly come but at a slightly slower pace than the ODK timeline would like.
@maelle would ROpenSci allow a submission with a slightly delayed MEE/JOSS publication?

@florianm florianm added this to the rOpenSci milestone Aug 28, 2019
@maelle
Copy link
Member

maelle commented Aug 30, 2019

Thanks for the explanation! @sckott please correct me if I'm wrong.

Indeed I think you'd need to choose between JOSS and MEE.

For MEE, the paper doesn't have to be ready but it's better if it's more or less ready. We at rOpenSci have no influence on their deeming a paper in scope/fitting.

For JOSS sorry I realize I need to ask too, will write again here (and then we can summarize in the main thread 😉).

Awesome about the diagrams! As an outsider I am looking forward to seeing them!

@sckott
Copy link

sckott commented Aug 30, 2019

I don't know about JOSS vs. MEE. I'd suggest emailing MEE and asking them. Maybe they'd consider JOSS similar enough to a pre-print, but I don't know.

@maelle
Copy link
Member

maelle commented Aug 30, 2019

Reg JOSS it'd be fine to add the short paper.md at the very end after the reviews, in which case I as editor would read it before you submit it for the expedited process at JOSS.

@florianm florianm added the ready label Sep 14, 2019
@florianm
Copy link
Collaborator Author

florianm commented Feb 11, 2020

Picking up the publication plans, currently I have about 2 months of urgent end of field season work before I can realistically dedicate time to attempt an MEE paper.

Edit June 2020: still no bandwidth. Re-visit MEE plans Aug 2020.

@florianm florianm removed the question label Feb 25, 2020
florianm pushed a commit that referenced this issue Nov 2, 2020
* Cleanup test form names and IDs
* Add all test forms to inst/extdata
* Update contrib guide
* Bump package version
florianm pushed a commit that referenced this issue Nov 2, 2020
florianm pushed a commit that referenced this issue Nov 2, 2020
* mapview 2.9.4 fixes popup, use github until CRAN is updated
* pin dep vers
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants