update documentation

- add initial docs/CONTRIBUTING.md
- update CODEOWNERS.md, README.md and bounties.md
- fix some issues found by codacy

docs/CONTRIBUTING.md

@@ -0,0 +1,17 @@
+## Contributing to Haveno
+
+Thanks for wishing to help! Here there are some guidelines and information about the development process. We suggest you to join the matrix room `#haveno-dev` (relayed on Freenode) and have a chat with the devs, so that we can help get you started.
+
+Issues are tracked on GitHub. We use [a label system](https://github.com/haveno-dex/haveno/issues/50) and GitHub's [project boards](https://github.com/haveno-dex/haveno/projects) to simplify development. Make sure to take a look at those and to follow the priorities suggested.
+
+### General guidelines
+
+- Be verbose. Remember this is collaborative development and we need to make life as easy as possible for future developers and for the current maintainers.
+- All formatting needs to be consistent with the current code.
+- Changes must be done 'the right way'. No hacks to make things work, if you are having issues, let the other devs know, so that we can help you out.
+
+## Development process
+
+- Pull requests should contain as many details as possible about what you are going to change and why. Avoid "title only" PRs, unless they are self-explanatory.
+- Pull requests should contain one single commit, unless it makes sense to have more. Please become familiar with git if you are not.
+- Pull requests won't be merged before 24 hours has passed. This timeframe will be extended when Haveno will have more active developers.

docs/bounties.md

@@ -1,7 +1,10 @@
 ## Bounties
 
-We use bounties to incentivize development. To receive a bounty, you agree to these conditions:
+We use bounties to incentivize development and reward contributors. All issues available for a bounty are listed [on the Kanban board](https://github.com/orgs/haveno-dex/projects/2). It's possible to list on each repository the issues with a bounty on them, by searching issues with the '💰bounty' label.
 
+To receive a bounty, you agree to these conditions:
+
+- Your changes must follow the [styling guidelines](contributing.md).
 - Bounties will be set and awarded at discretion of the Haveno core team.
 - The issues eligible for a bounty are labelled '💰bounty' and have the amount of the bounty specified in the title in this form: `[$200]` if in dollars or `[ɱ20]` if in Monero.
 - The first person who resolves an issue in its entirety will receive the entire amount of the bounty.
@@ -11,11 +14,4 @@ We use bounties to incentivize development. To receive a bounty, you agree to th
 - If a big number of bounties is claimed at the same time, the maintainers might opt for sending all the rewards on a specific day of the month instead of right after resolution.
 - If the bounty is in dollars, the contributor will receive the amount in Monero according to the value of XMR at the moment the issue was practically resolved, so in the moment the maintainers accept the last patch resolving the issue.
 
-You are also required to follow these styling guidelines:
-
-- Be verbose. Remember this is collaborative development and we need to make life as easy as possible for future developers and for the current maintainers. Pull requests should contain as many details as possible about what you are going to change and why. Avoid "title only" PRs, unless they are self-explanatory.
-- Pull requests should contain one single commit, unless it makes sense to have more. Please become familiar with git if you are not.
-- All formatting needs to be consistent with the current code.
-- Changes must be done 'the right way'. No hacks to make things work, if you are having issues, let the other devs know, so that we can help you out.
-
 We want to keep the system simple and flexible, but we will add new rules or edit existing ones if necessary.