We should store THE contributing guide here if we decide to remove it from repositories.

Pro:

• No inconsistency, messing with updating

Con:

• Not really nice?

We should leave the CONTRIBUTING.md file in each repo though. The contents could be a link to THE contributing guide. We want the special header when opening an issue or PR.

👍

Okay, so are we fine with a single link to the documentation?

http://docs.httplug.io/contributing for example? Or should it point to this repo and the contribution guide inside?

I was thinking about opening a development section in the documentation where we could put:

• contributing guide
• contributor code of conduct
• MIT license
• any other developer related stuff

lets have a development section in the documentation, yes. and then link to that.