# Collaboration Guide

Note: pyOpenSci is still building out this section of our guidebook. Many of the examples come from rOpenSci. If you have suggestions for changes, check out the GitHub repo.

## Make your repo contribution and collaboration friendly

### Code of conduct

We require that you use a code of conduct such as the Contributor Covenant in developing your package. You should document your code of conduct in a CODE_OF_CONDUCT file in the package root directory, and link to this file from the README file.

### Contributing guide

We have a template for contributing guidelines in our cookiecutter repository. Even if you're not using cookiecutter to build your project (see our packaging guide for info), you can download our CONTRIBUTING.rst as a starting point.

You can tweak it a bit depending on your workflow and package. For example, make sure contributors have instructions in your CONTRIBUTING file for running local tests if not trivial. CONTRIBUTING can also contain some details about how you acknowledge contributions (see this section) and the roadmap of your package (cf this example for R).

### Issue labelling

You can use labels such as "help wanted", "good first issue", or "beginner" to help potential collaborators, including newbies, find your repo. For more info, see this GitHub article.

## Working with collaborators

### Onboarding collaborators

There's no general pyOpenSci rule as to how you should onboard collaborators. You should increase their rights to the repo as you gain trust, and you should definitely acknowledge contributions (see this section).

You can ask a new collaborator to make PRs (see following section for assessing a PR locally, i.e. beyond CI checks) to dev/master and assess them before merging, and after a while let them push to master, although you might want to keep a system of PR reviews... even for yourself once you have team mates!

A possible model for onboarding collaborators is provided by Jim Hester in his lintr repo.

If your problem is recruiting collaborators, you can post an open call like Jim Hester's on Twitter, GitHub). As an pyOpenSci package author, you can also ask for help from pyOpenSci.

### Working with collaborators (including yourself)

You could implement the "gitflow" philosophy as explained by Amanda Dobbyn in this rOpenSci blog post.

One particular aspect of working with collaborators is reviewing pull requests. Even if not adopting gitflow it might make sense for repo collaborators to make PRs and have them reviewed, and in general PRs by external developers will need to be assessed. Sometimes you'll be fine just reading the changes and trusting Continuous integration. Sometimes you'll need to dive deeper, e.g. by downloading a copy of the branch that the PR was created from.