Refactor Project Management
I would like to refactor our project management system.
Problems
Roadmap:
Sources:
ADD
WalletWasabi.Documentation/WasabikaCodex.md
+
+## Daily routine
+
+1. Start
+2. Check code review requests. [link](https://github.com/zkSNACKs/WalletWasabi/pulls) __Reviews / Awaiting review from you__
+2. Check [priority issues!](https://github.com/zkSNACKs/WalletWasabi/pulls?q=is%3Aopen+is%3Apr+label%3Apriority). Take it or set Assignees and Labels if you can.
+3. Check your own PR-s and answer if neccessary. [link](https://github.com/pulls?utf8=%E2%9C%93&q=is%3Aopen+archived%3Afalse+user%3AzkSNACKs+) __Click Created__
+ - If you need help use __@mention__.
+ - If you need review __set Reviewers__.
+4. Check assigned issues. [link](https://github.com/pulls?q=is%3Aopen+archived%3Afalse+user%3AzkSNACKs) __Click Assigned__
+5. Check mentions. [link](https://github.com/pulls?utf8=%E2%9C%93&q=is%3Aopen+archived%3Afalse+user%3AzkSNACKs) __Click Mentioned__
+6. Check new issues.
+7. Work on anything you want - manage task progress in [Kanban board](https://github.com/molnard/WalletWasabi/projects/1)
+
+## Weekly routine
+
+- Monday: Community meeting [Optional]
+- Wednesday: Developer meeting
+- Thursday: Check the bell
+- Pair programming hour.
+
+## Monthly routine
+
+- Go through all Issues and Pull requests.
+
+## Roadmap
+
+https://github.com/molnard/WalletWasabi/projects/2
+
+## Code review (CR)
+
+- Read the description of the Pull Request. If it is missing ask for it if neccessary.
+- Check Continous Integration (CI) before code review. Only continue if it is passed.
+- Do not review code longer than 60 minutes or more than 400 lines. Take a 10 minute pause at that point.
+- Check for code smells. Give constructive feedback that helps (Not hurts).
+ - Easy to read.
+ - Maintainability.
+- Checkout PR and test it if required.
+- Create Request changes if needed.
+- Approve if you are done.
+
+__Tips__: if the PR is too big ask for breakdown.
+
+__Fact__: code review is the top rated code improvement tool. It is the only one scientifically proven methology to impove code quality.
+
+## Creating Pull Request
+
+- Fill the title
+- Fill the decription.
+ - If it fixes issues [add keyword](https://help.github.com/en/articles/closing-issues-using-keywords).
+ - Add related issues and PR links
+ - Add Sub-Tasks with checkboxes
+- Implement feature
+- Always fix CI
+- Set Reviewers
+- Merge PR if there are at least 2 code maintainer Approval (nopara, lontrivero, molnard)
+- If it is UX related always ask Jumar or Dan review.

Refactor Project Management

I would like to refactor our project management system.


Problems : https://miro.com/app/board/o9J_kw6ixFo=/

Roadmap:
https://github.com/zkSNACKs/WalletWasabi/issues/2359

Sources: 
https://github.com/nopara73/ForeverAloneProgramming
https://gist.github.com/molnard/a2fa16c5a3d5931b78b79ef336cef73a