Process

Code should follow the Google style guide.

The code on the master branch should always build, pass tests (once we have them), and be a jumping off point for anyone else working on ngx_pagespeed.

All code changes need to be reviewed by someone else, ideally including someone at a different site. Work on a change in a branch labeled yourname-description (ex: jefftk-blocking-rewrite) and push often so that other people can see what you're doing. When you have something ready to merge to master create a pull request and notify ngx-pagespeed-discuss so we can all look at it. After approval someone with commit access will squash the branch into a single commit and merge it into master.