diff --git a/index.Rmd b/index.Rmd index 66928ae0d..3358b010e 100644 --- a/index.Rmd +++ b/index.Rmd @@ -68,19 +68,10 @@ The R Journal accepts a variety of article topics including: -- Packages: Details of contributed R packages that are available on CRAN or Bioconductor, that go beyond a package vignette. This includes providing the broader context, implementation details, applications or examples of use, with the purpose being to make the work relevant to a wider readership than only the package users. The paper might explain the novelty in implementation and use of R, introduce new data structures or general architectures that could be re-usable for other R projects. Some good advice on code style can be found in - - "R packages" chapter 7 by Hadley Wickham at https://r-pkgs.org/r.html, - - "rOpenSci Packages: Development, Maintenance, and Peer Review" at https://devguide.ropensci.org/building.html, - - "What I look for in 'Software Papers'" by Carl Boettiger at https://www.carlboettiger.info/2013/06/13/what-I-look-for-in-software-papers.html - - Using the "styler" package, - - and avoiding the features warned against by Jenny Bryan at https://www.tidyverse.org/articles/2017/12/workflow-vs-script/ - +- Packages: Details of contributed R packages that are available on CRAN or Bioconductor, that go beyond a package vignette. This includes providing the broader context, implementation details, applications or examples of use, with the purpose being to make the work relevant to a wider readership than only the package users. The paper might explain the novelty in implementation and use of R, introduce new data structures or general architectures that could be re-usable for other R projects. Note that both the paper and the code will be reviewed. - Reviews and proposals: surveying and discussing challenges and opportunities of potential importance for the broader R community, including proposals and proof-of-concept implementations. - - Comparisons and benchmarking: of implementations in base-R and contributed packages with each other, and where relevant with implementations in other software systems. - - Applications: demonstrating how new or existing techniques can be applied in an area of current interest using R, providing a fresh view of such analyses in R that is of benefit beyond the specific application. - - Special issue articles: papers associated with a conference like R Medicine, or possibly a collection of papers on a particular topic of interest. ## History diff --git a/submissions.Rmd b/submissions.Rmd index e4cf0ab0c..97150b985 100644 --- a/submissions.Rmd +++ b/submissions.Rmd @@ -90,9 +90,39 @@ You may have problems submitting if size of your submission zip file is more tha Your paper will be checked for reproducibility by running the code provided. Please ensure that the examples can be run in a timely manner, perhaps by reducing the example data size. If necessary, intermediate output files, can be provided to shorten the run time. -### Re-submission or revision - -Re-submission and revisions to accepted articles are received through the same site where new submissions are received (link below). When providing a re-submission or revision, you will need to **enter the identifier of the original submission** in the last field of the submission form. This also needs to be done if your paper has previously been rejected, and you have made appropriate corrections for it to be considered again. +# What happens after you submit a paper + +Once you have submitted a paper, the editorial board will go through the following steps. + +1. Deceide if your submission is technically in the correct format. In particular: + - are all the requested files there and of the correct format? + - does the reproducibility code run? + - is all code used open source and available via CRAN or BioConductor? + - are all the data files (if any) in an open, non-proprietary format? +2. If the technical test is passed, it is decided whether the submission is amenable for peer review: + - is the topic within scope? + - is the paper properly organized? + - is the writing style suitable for review? +3. If the submission passes the second test, it will be sent our for review. This process might take several months. + You will receive one or more reviews, possibly with notes from one of the (associate) editors, and a _verdict_. There are four possible verdicts: + - *Accepted* Congratulations. Your paper will be published in the R Journal. You will are asked to upload a final version that will be proof-read and + you will receive a print proof before publication. + - *Minor revisions* The paper can be accepted conditional on a number of smaller revisions in the manuscript and/or the code. You are expected to fix + these issies within three months, and resubmit along with a letter where you describe, point-by-point, how the comments of the reviewers have been + addressed. The paper will not be reviewed again by peer reviewers. + - *Major revisions* The manuscript and/or the code need severe updates before the manuscript can be accepted for publication. You are expected to + fix the issies within three months, and resubmit along with a letter where you describe, point-by-point how the comments of the reviewers have been + addressed. The paper will be send back to the reviewers for a second round of review, which may result in any verdict. + - *Reject* Your paper is found to be unsuited for publication in the R Journal. No resubmission is expected. + + + +Re-submission and revisions to accepted articles are received through the same +site where new submissions are received (link below). When providing a +re-submission or revision, you will need to **enter the identifier of the +original submission** in the last field of the submission form. This also needs +to be done if your paper has previously been rejected, and you have made +appropriate corrections for it to be considered again. ### Note on special issue articles