#3 Introduce a fork+PR contribution workflow

This is done automatically if you use Gogs, Gitea, or self-hosted Gitlab and is even easier if you don't go self-hosted. ### Issues solved: * People needing to have a write access to the server to maintain their own branches publicly accessible and automergeable-when-ready. * And atk needing to use gitolite to fine-grain manually manage access rights separately for each user. (which also adds time for a new contributor to jump in) Instead people will just have their own forks and no write access to the main repo is needed. Forks are reviewed upon merge but that's it. ### Issues created *none I can tell. This is a very common practice in 2018.*