@taylori, is there a desired workflow for contributing to r4ss? For instance, in ss3sim we use branches for most changes (https://github.com/ss3sim/ss3sim/wiki/Git-Workflow). I think it's been helpful to have us all working under the same set of workflow rules.

Does something like this exist for r4ss? At what point should I create a branch vs. using master? Do you want us to automatically merge in branches or let you handle the pull requests? If I do something bigger, should I work on a forked repo?