layout	title	description
default	the cloudyr project styleguide	the cloudyr project uses a standardized style package structure and programming style to streamline development, facilitate any future package maintenance, and ease contributions from new users. This document describes the essential features of a cloudyr package.

the cloudyr project uses a standardized style package structure and programming style to streamline development, facilitate any future package maintenance, and ease contributions from new users. This document describes the essential features of a cloudyr package. A template package is available, which provides a skeleton that complies with this guide.

package structure

cloudyr packages should follow the guidelines describe in Writing R Extensions and adopt a standard package structure:

+-- /data
+-- /inst
|   +-- CITATION
+-- /man
+-- /R
|   +-- *.R
+-- /tests
|   +-- /testthat
|   +-- test-all.R
+-- /vignettes
+-- .gitignore
+-- .Rbuildignore
+-- .travis.yml
+-- CONTRIBUTING.md
+-- DESCRIPTION
+-- drat.sh
+-- NAMESPACE
+-- NEWS
+-- README.md

The /man directory is generated automatically by roxygen2 (via devtools::document()). This directory will contain all function documentation plus a package-level documentation page accessible via ? packagename. R code files in the /R directory should have capital .R extensions and be written using complete roxygen2 markup (see below). A /tests directory contains relevant testthat testing code.

Optional directories include /data for embedded package data and /vignettes can be used to store knitr-enabled vignettes where appropriate.

The following sections describe some of these files in detail.

CITATION

All cloudyr packages must have a CITATION file of the following form:

citHeader("To cite package 'aws.signature' in publications use:")
     
 year <- sub(".*(2[[:digit:]]{3})-.*", "\\1", meta$Date, perl = TRUE)
 vers <- paste("R package version", meta$Version)
 
 citEntry(entry="Manual",
          title = "aws.signature: Amazon Web Services Request Signatures",
          author = personList(as.person("Thomas J. Leeper")),
          year = year,
          note = vers,
          textVersion =
          paste("Thomas J. Leeper (",
                year,
                "). aws.signature: Amazon Web Services Request Signatures. ",
                vers, ".", sep=""))

documentation

All package documentation should be generated dynamically with roxygen2 (via devtools::document()). The NAMESPACE file is generated automatically, as well. Some key features of high quality documentation include:

Packages should have a package-level documentation page (i.e., accessible via the package name, such as ? aws.s3, from the R console).
Cross-references between help files should be used generously. This includes cross-references to other packages' functions (using the \code{\link[pkgname]{function}} markup).
Related functions should be documented together by using the #' @rdname tag, where appropriate.
Documentation should use #' @details, #' @references, and #' @examples as much as needed to fully convey relevant details of code. Verbosity is virtue!
Vignettes should be used as needed, but are not required. Thematic documentation pages can also be included in addition to function-specific documentation pages (see ? regex for an example of this).

code

Code should be written cleanly, using roxygen2 inline documentation, comments where appropriate, and in a manner consistent with the Google R Style Guide and Hadley's guide. A few key points:

<- is preferred over = for assignment
Indentation is with four spaces, not two or a tab. There should be no tabs in code files.
if () {} else {} constructions should always use full curly braces even when usage seems unnecessary from a clarity perspective.
TODO statements should be opened as GitHub issues with links to specific code files and code lines, rather than written inline.

Follow Hadley's suggestion for aligning long functions with many arguments:

long_function_name <- function(a = "a long argument", 
                               b = "another argument",
                               c = "another long argument") {
  # As usual code is indented by two spaces.
}

Never use print() to send text to the console. Instead use message(), warning(), and error() as appropriate.
Use environment variables, not options(), to store global arguments that are used by many or all functions.

For packages that interact with remote websites:

Use httr for web access and implement stop_for_status() or warn_for_status() checks.
Packages requiring authenticated HTTP requests should have credentials encrypted in .travis.yml to enable Travis-CI tests.

.gitignore and .Rbuildignore

A .gitignore may be needed to mask files in a directory. A .Rbuildignore should cover all non-standard files in the top-level directory:

.travis.yml
drat.sh

continuous integration

All cloudyr packages are tested automatically on the Travis-CI Continuous Integration service. A reasonable .travis.yml file would look like the following:

language: r
sudo: required
r_packages:
- covr
- drat
after_success:
- Rscript -e 'library(covr);codecov()'
- test $TRAVIS_PULL_REQUEST == "false" && test $TRAVIS_BRANCH == "master" && bash drat.sh
env:
  global:
  - secure: jw8SjbwUlKz/zPczyqcvnm0r9jbUvNb4hplUn3bxlD2SniNkitqODk2/jmlfunrpmHJRS4GDx6X6omYTNwvNsyE51dK6XJE8nZuaeCPvGLl3xxgRL6dis2JGwy2itRm0C/P6UEAUSmuTbtR15N1JC7Y7ot0IRpfRZc0tOkuS8L0=

This indicates the use of native R support, which requires sudo permissions. r_github_packages should be used to install working versions of packages where appropriate.

Packages should have (testthat) tests and should push code coverage results to the cloudyr codecov.io page using the covr package.

The travisci package should be used, where needed, to automatically trigger builds of dependent cloudyr packages using:

after_success:
- Rscript -e "travisci::restart_last_build('cloudyr/dependentpkg')"

This requires an encrypted TRAVIS_CI_TOKEN environment variable.

drat

All packages, conditional on passing CI tests, are automatically posted to the cloudyr drat repository, so that they can be installed using install.packages() in addition to install_github() (from ghit or devtools). The drat.sh file achieves this:

#!/bin/bash
set -o errexit -o nounset
addToDrat(){
  mkdir drat; cd drat

  ## Set up Repo parameters
  git init
  git config user.name "leeper"
  git config user.email "thosjleeper@gmail.com"
  git config --global push.default simple

  ## Get drat repo
  git remote add upstream "https://$GH_TOKEN@github.com/cloudyr/cloudyr.github.io.git"
  git fetch upstream
  git checkout master

  Rscript -e "drat::insertPackage('../$PKG_TARBALL', repodir = './drat')"
  git add --all
  git commit -m "add $PKG_TARBALL (build $TRAVIS_BUILD_ID)"
  git push

}
addToDrat

For this code to execute successfully, a GH_TOKEN environment variables needs to be encrypted in the repo.

CONTRIBUTING.md

A CONTRIBUTING.md file should be written in markdown and include a reference to this page. Here's a template:

Contributions to **aws.s3** are welcome from anyone and are best sent as pull requests on [the GitHub repository](https://github.com/cloudyr/aws.s3/). This page provides some instructions to potential contributors about how to add to the package.

 1. Contributions can be submitted as [a pull request](https://help.github.com/articles/creating-a-pull-request/) on GitHub by forking or cloning the [repo](https://github.com/cloudyr/aws.s3/), making changes and submitting the pull request.
 
 2. The cloudyr project follows [a consistent style guide](http://cloudyr.github.io/styleguide/index.html) across all of its packages. Please refer to this when editing package code.
 
 3. Pull requests should involve only one commit per substantive change. This means if you change multiple files (e.g., code and documentation), these changes should be committed together. If you don't know how to do this (e.g., you are making changes in the GitHub web interface) just submit anyway and the maintainer will clean things up.
 
 4. All contributions must be submitted consistent with the package license ([GPL-2](http://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html)).
 
 5. Non-trivial contributions need to be noted in the `Authors@R` field in the [DESCRIPTION](https://github.com/cloudyr/aws.s3/blob/master/DESCRIPTION). Just follow the format of the existing entries to add your name (and, optionally, email address). Substantial contributions should also be noted in [`inst/CITATION`](https://github.com/cloudyr/aws.s3/blob/master/inst/CITATION).
 
 6. The cloudyr project use royxgen code and documentation markup, so changes should be made to roxygen comments in the source code `.R` files. If changes are made, roxygen needs to be run. The easiest way to do this is a command line call to: `Rscript -e devtools::document()`. Please resolve any roxygen errors before submitting a pull request.
 
 7. Please run `R CMD BUILD aws.s3` and `R CMD CHECK aws.s3_VERSION.tar.gz` before submitting the pull request to check for any errors.
 
Some specific types of changes that you might make are:

 1. Bug fixes. Great!
 
 2. Documentation-only changes (e.g., to Rd files, README, vignettes). This is great! All contributions are welcome.
 
 3. New functionality. This is fine, but should be discussed on [the GitHub issues page](https://github.com/cloudyr/aws.s3/issues) before submitting a pull request.
 
 3. Changes requiring a new package dependency should also be discussed on [the GitHub issues page](https://github.com/cloudyr/aws.s3/issues) before submitting a pull request.
 
 4. Message translations. These are very appreciated! The format is a pain, but if you're doing this I'm assuming you're already familiar with it.

Any questions you have can be opened as GitHub issues or directed to thosjleeper (at) gmail.com.

DESCRIPTION

There is not much to say about DESCRIPTION beyond that described in Writing R Extensions. However, a few points:

Packages should use "semantic versioning" (see Hadley's discussion) of the form major.minor.patch with values such as 1.2.3.

NEWS

A NEWS files should be present and be used to store three types of information:

Documentation changes
Bug fixes
Significant user-visible changes (such as API changes)

This does not need to be updated on every commit, but rather on significant changes. Changes that address GitHub issues should mention the issue number and other changes should attribute code authors or bug reporters where appropriate:

# CHANGES TO aws.signature v0.1.1 #

 * Fixed header encoding error. (#1, h/t Thomas Leeper)

README

A README.md file should be included to display on GitHub and CRAN. This should provide a package description, installation instructions, and brief code examples. This can be generated from a README.Rmd file using knitr::knit("README.Rmd"), but it is not required.

The README should contain the cloudyr project footer with a link to the cloudyr project page.

---
[![cloudyr project logo](http://i.imgur.com/JHS98Y7.png)](https://github.com/cloudyr)

programming style

A few rules about programming style:

Commits are cheap and should be used frequently.
Commit messages should reference issue numbers and close issues explicitly (e.g., fix headers (closes #1)) where appropriate.
Pull requests on GitHub should be merged on the command line, not using the web interface, if possible, or via the web interface without a merge commit.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

styleguide.md

styleguide.md

package structure

CITATION

documentation

code

.gitignore and .Rbuildignore

continuous integration

drat

CONTRIBUTING.md

DESCRIPTION

NEWS

README

programming style

Files

styleguide.md

Latest commit

History

styleguide.md

File metadata and controls

package structure

CITATION

documentation

code

.gitignore and .Rbuildignore

continuous integration

drat

CONTRIBUTING.md

DESCRIPTION

NEWS

README

programming style