Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

The R package development is a complex process of creating (mostly) a useful software, that will (probably) be used by other users. This means the provided tool should be resistant, immune, well tested and properly documented. Developers from many different languages have invented various approaches to improve software development, creating documentation or package testing. R users have adapted few of them and mostly we use travis for continuous integration, roxygen2 for documentation, devtools for testing and knitr / rmarkdown for writing manuals, tutorials, vignettes and package websites. This software development kit causes that the R package structure is rather broad, especially since many of us (R developers) puts source code from different languages into the package root to speed up the performance of created tools. Moreover we built our software libraries that are based on other packages, which complicates the NAMESPACE of the prepared package and forces the understanding of difference between dependent, imported and suggested packages. In this whole ecosystem of development equipment and requirements for proper package structure I’ve been asked What Every R Package Must Contain? You wouldn’t guess how easy was the answer.

# DESCRIPTION file with 7 filled fields

On my last job interview on the R developer position the recruiting manager asked me What every R package must contain? Probably it was a trigger to conversation about the best practices in the R package development process, including roxygen2 or devtools. Because I was tired of elementary questions I have responded nonstandardly – A DESCRIPTION file, and that’s it.

In fact you only need a DESCRIPTION file with 7 filled fields to have a package that passes CRAN CHECK!

I was amazed how we have developed and complicated the process of extending base R from this simple statement.

Below you can see the eRum2016 package that only have a DESCRIPTION file with such fields (URL is the extra, unneded field) passes checks on Travis platform.

By default, on Travis the R CMD check --as-cran is perfomed.

This package can be even installed from GitHub and the index of this package can be opened to present the information included in the DESCRIPTION file

This package present the key information for European R Users Meeting that will be held September in Poznań, Poland. More information about this converence can be checked on the conference website http://erum.ue.poznan.pl/.