Document process for testing coala-ci on a GitHub project using Travis and reporting findings

[jayvdb]

Document process for testing coala-ci on a GitHub project using Travis and reporting findings.

This will be used as a GCI medium difficulty task, but is also used for other engagement activities where many participants are exploring coala's capabilities.

The important part is what they do with the Travis results, so that the reported findings are pushed back into the coala dev and further engagement processes.

e.g. if all tests pass, and the project doesnt have CI linting yet, then it is easy to create a pull request to the project and see if they want to adopt coala.

However if they already have some CI linting, we dont want to be aggressively proposing they replace their existing infrastructure with coala. Especially not asking school children to be our pushers ;-)

So results need to be pushed into the coala project, and then new tasks created by coala mentors.

[jayvdb]

Writing it up at https://github.com/coala/coala/wiki/Google-Code-In-Task-Use-coala

[jayvdb]

Note there should be two tasks:

1. report findings of coala-ci with only auto-fixes, and no PR (mostly written up)
2. explore the errors and fix them if there are a small number, or remove the problematic bears, so that the changes can be a PR to the selected repo (not done)

[jayvdb]

Note this task is much easier if coala/coala-quickstart#39 is completed

[jayvdb]

This was done as that CI1-3 series of GCI tasks, e.g. https://github.com/coala/projects/blob/master/_projects/use_coala.md