Write contribution guide

[everzet]

No description provided.

[ciaranmcnulty]

Explain it to me Monday and I'll do this

[everzet]

awesome!

[stof]

@everzet have you explained it to @ciaranmcnulty ?

[everzet]

@stof yes, I did. To recap, core ideas:

1. Continuous delivery - everything in master is deployed via Codeship
2. Open infrastructure - Ansible playbook in the repository controls what is installed on prod
3. Issues are turned off - you report bugs by sending pull requests with *.feature files (just narratives are fine)
4. Everyone can contribute features or bug fixes by opening pull requests. As soon as they merged - behat.org is updated

[stof]

Issues are turned off - you report bugs by sending pull requests with *.feature files (just narratives are fine)

This seems a bad idea to me. It makes it hard to discuss higher level topics (like this issue for instance). We should encourage sending a PR, but we should still keep the issue tracker IMO.
Another case where the feature file is not handy is for reporting UI glitches (I don't want our Behat suite to become full of scenarios asserting that the UI looks good at all resolutions for instance)

[everzet]

@stof very good points actually.

[stof]

@ciaranmcnulty is there any progress on this ?